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.
Created attachment 1200992 [details] screenshot screenshot
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.)
created redmine issue for this: http://projects.theforeman.org/issues/16748
Upstream bug component is WebUI
Upstream bug component is Content Management
*** This bug has been marked as a duplicate of bug 1368254 ***