Bug 1537108 - Errata and CVE iconography inconsistent with other products
Summary: Errata and CVE iconography inconsistent with other products
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI
Version: 580
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jiří Dostál
QA Contact: Radovan Drazny
URL:
Whiteboard:
Depends On:
Blocks: sat58-errata
TreeView+ depends on / blocked
 
Reported: 2018-01-22 12:56 UTC by Jiří Dostál
Modified: 2018-05-15 21:47 UTC (History)
5 users (show)

Fixed In Version: spacewalk-java-2.5.14-120-sat satellite-branding-5.8.0.9-1-sat
Doc Type: Release Note
Doc Text:
If this bug requires documentation, please select an appropriate Doc Type value.
Clone Of:
Environment:
Last Closed: 2018-05-15 21:46:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Errata icons pre-update (satellite-branding-5.8.0.8-1) (469.69 KB, image/png)
2018-04-04 12:02 UTC, Radovan Drazny
no flags Details
Missing errata icons post-update (satellite-branding-5.8.0.9-1) (462.18 KB, image/png)
2018-04-04 12:15 UTC, Radovan Drazny
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:1565 0 None None None 2018-05-15 21:47:03 UTC

Comment 1 Jiří Dostál 2018-01-22 14:19:51 UTC
spacewalk 1c236c59cc87e9dcc7f6251dbf19926a83fad033

Comment 2 Jiří Dostál 2018-01-25 08:53:57 UTC
Colored icons for errata-lists
370c2169bd33cb5c4bf27f1eda7fb2e998064834

Comment 6 Radovan Drazny 2018-04-04 12:02:34 UTC
Created attachment 1417245 [details]
Errata icons pre-update (satellite-branding-5.8.0.8-1)

Comment 7 Radovan Drazny 2018-04-04 12:15:31 UTC
Created attachment 1417247 [details]
Missing errata icons post-update (satellite-branding-5.8.0.9-1)

Updated to spacewalk-java-2.5.14-116 and satellite-branding-5.8.0.9-1. Looking at https://<satellite-host>/rhn/errata/RelevantErrata.do with a not updated RHEL 7.4 system registered, it seems the new icons are not present in the left column "Errata legend" field, nor at errata items themselves. 

FAILEDQA

Comment 8 Radovan Drazny 2018-04-04 12:34:16 UTC
Ok, it seems that my Firefox was misbehaving a bit, and was not refreshing cache correctly. Manual web cache clean-up helped, and icons are present as expected. Sorry for the noise.

Comment 9 Radovan Drazny 2018-04-06 12:46:09 UTC
Well, maybe I was too hasty, after all. Relevant and All errata pages are ok, there are new icons, and they are color coded depending on RHSA severity. But when I do search for errata using the Advanced Search errata page, there are new icons, but the color codes are missing - all icons are black, no matter the severity. Is this an expected behavior?

Comment 10 Jiří Dostál 2018-04-09 09:41:35 UTC
Silly me, I forgot to enclose one commit in this BZ. This commit resolves colored icons for search. Following commits also resolve ISE caused by wrong cherry-picking and one improvement.


spacewalk 046c37a03da1bf3963523636cc664106eac77822
spacewalk d4a852b8d8e79f28a843ca2bc1b62ad0f8744272

Comment 12 Jiří Dostál 2018-04-12 07:08:15 UTC
One more page has been found - upgradable packages. 
Spacewalk 25794d2305c9f2fc407b8cc5a40419e346796a25

Comment 15 Jiří Dostál 2018-04-17 15:44:44 UTC
Updating relevant errata SQL query to select severities...
d14f71e1be12f84f9926c42afce7032a1ccd18a6

Comment 17 Radovan Drazny 2018-04-18 10:05:44 UTC
Verified on spacewalk-java-2.5.14-120. I didn't find any pages with the new iconography and severity color coding missing. There could be some confirmation pages with severity color coding missing, but these are not critical. 

VERIFIED

Comment 20 errata-xmlrpc 2018-05-15 21:46:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:1565


Note You need to log in before you can comment on or make changes to this bug.