Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMarcelo Moreira de Mello
2016-09-14 23:01:31 UTC
Description of problem:
When a system is fully updated based on its content view and correctly registered and consuming an entitlement, the system's properties page still shows an error status if there are some "Security errata applicable" since it considered all the applicable errata (not yet present on its content view).
We need to enhance and provide a better description to avoid misunderstanding on this particular situation. Ideally, we should address differently the error status when:
1 module Katello
2 class ErrataStatus < HostStatus::Status
3 NEEDED_SECURITY_ERRATA = 3
4 NEEDED_ERRATA = 2
[.. snip ..]
15 N_("Security errata applicable")
16 when NEEDED_ERRATA
17 N_("Non-security errata applicable")
"Security errata applicable" or "Non-security errata applicable" should not be considered as an error.
Version-Release number of selected component (if applicable):
Red Hat Satellite 6.2
How reproducible:
100%
Steps to Reproduce:
1. Install a RHEL6u7 system;
2. Create a content view including packages up to RHEL6u6
3. Register the RHEL6u7 system to the RHEL6u6 content view
4. yum list updates should return 0
5. Access https://satellite/hosts/RHEL6u7 system
Actual results:
Status: Error
Errata: Security errata applicable
Subscription: Fully entitled
Expected results:
It is correct that are some security errata applicable but this should not trigger the status to be displayed as an error. Maybe we can change to warning or a different message.
Comment 2Marcelo Moreira de Mello
2016-09-14 23:09:12 UTC
I have been hearing this complaint from a few customers that we should not consider this situation an Error. Ideally we could address this in 6.2.z or 6.3
It should be noted that not only is this status confusing, but does NOT seem to properly update in the WebUI once this is no longer the actual case for that host. Marcelo was also able to reproduce this by ensuring a host was totally up to date, and notably the host would still show the error. (We could flip this switch in the DB to get it sorted manually.)
Description of problem: When a system is fully updated based on its content view and correctly registered and consuming an entitlement, the system's properties page still shows an error status if there are some "Security errata applicable" since it considered all the applicable errata (not yet present on its content view). We need to enhance and provide a better description to avoid misunderstanding on this particular situation. Ideally, we should address differently the error status when: 1 module Katello 2 class ErrataStatus < HostStatus::Status 3 NEEDED_SECURITY_ERRATA = 3 4 NEEDED_ERRATA = 2 [.. snip ..] 15 N_("Security errata applicable") 16 when NEEDED_ERRATA 17 N_("Non-security errata applicable") "Security errata applicable" or "Non-security errata applicable" should not be considered as an error. Version-Release number of selected component (if applicable): Red Hat Satellite 6.2 How reproducible: 100% Steps to Reproduce: 1. Install a RHEL6u7 system; 2. Create a content view including packages up to RHEL6u6 3. Register the RHEL6u7 system to the RHEL6u6 content view 4. yum list updates should return 0 5. Access https://satellite/hosts/RHEL6u7 system Actual results: Status: Error Errata: Security errata applicable Subscription: Fully entitled Expected results: It is correct that are some security errata applicable but this should not trigger the status to be displayed as an error. Maybe we can change to warning or a different message.