Red Hat Bugzilla – Bug 1336924
[RFE]hypervisors that do NOT have a subscription attached should NOT be green under content hosts
Last modified: 2018-07-18 08:38:29 EDT
Description of problem: When walking through virt-who steps, and then hypervisors populate into the satellite webui, they are always green. This is confusing since they should be red in our customers eyes since they don't have a subscription yet. So often times we'll have to have a remote session in order to explain to them "yes they are green, but you still have to attach a subscription to them" Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. set up virt-who then start it 2. check under content hosts 3. all hypervisors show up and they are all green. Actual results: Even before adding a subscription, the status is green. On a regular content host they are red/yellow if they need a subscription. The hypervisors should be yellow, since they are in the webui, but need a subscription still. Expected results: status of yellow hypervisors, until you place a subscription on them. Additional info:
Created redmine issue http://projects.theforeman.org/issues/20577 from this bug
*** Bug 1396145 has been marked as a duplicate of this bug. ***
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17147 has been resolved.
Verified in Satellite 6.3 Snap 22. Hypervisors that don't have a valid subscription attached now show up in the UI as an "Unsubscribed Hypervisor", which gets the yellow warn icon. See attached images for verification.
Created attachment 1347090 [details] verification screenshot 1
Created attachment 1347091 [details] verification screenshot 2
qe_test_coverage PR: https://github.com/SatelliteQE/robottelo/pull/5585
*** Bug 1544016 has been marked as a duplicate of this bug. ***
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/RHSA-2018:0336
*** Bug 1310698 has been marked as a duplicate of this bug. ***