Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1336924 - [RFE]hypervisors that do NOT have a subscription attached should NOT be green under content hosts
[RFE]hypervisors that do NOT have a subscription attached should NOT be green...
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Subscription Management (Show other bugs)
6.1.8
Unspecified Unspecified
high Severity high (vote)
: Beta
: Unused
Assigned To: Christine Fouant
jcallaha
: FutureFeature, PrioBumpGSS, PrioBumpPM, Triaged, UserExperience
: 1310698 1396145 1544016 (view as bug list)
Depends On:
Blocks: CEE_Sat6_Top_BZs/GSS_Sat6_Top_Bugs 260381
  Show dependency treegraph
 
Reported: 2016-05-17 15:54 EDT by Kathryn Dixon
Modified: 2018-07-18 08:38 EDT (History)
21 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-02-21 07:35:17 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
verification screenshot 1 (133.21 KB, image/png)
2017-11-02 14:15 EDT, jcallaha
no flags Details
verification screenshot 2 (112.56 KB, image/png)
2017-11-02 14:15 EDT, jcallaha
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 17147 None None None 2017-08-29 17:07 EDT
Red Hat Knowledge Base (Solution) 2874721 None None None 2017-05-23 18:23 EDT
Red Hat Product Errata RHSA-2018:0336 normal SHIPPED_LIVE Important: Satellite 6.3 security, bug fix, and enhancement update 2018-02-21 17:43:42 EST

  None (edit)
Description Kathryn Dixon 2016-05-17 15:54:54 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:
Comment 8 Brad Buckingham 2017-08-14 08:22:27 EDT
Created redmine issue http://projects.theforeman.org/issues/20577 from this bug
Comment 9 Christine Fouant 2017-08-29 15:20:07 EDT
*** Bug 1396145 has been marked as a duplicate of this bug. ***
Comment 10 pm-sat@redhat.com 2017-09-27 14:02:51 EDT
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17147 has been resolved.
Comment 11 jcallaha 2017-11-02 14:14:41 EDT
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.
Comment 12 jcallaha 2017-11-02 14:15 EDT
Created attachment 1347090 [details]
verification screenshot 1
Comment 13 jcallaha 2017-11-02 14:15 EDT
Created attachment 1347091 [details]
verification screenshot 2
Comment 14 Djebran Lezzoum 2017-11-22 11:32:09 EST
qe_test_coverage PR: https://github.com/SatelliteQE/robottelo/pull/5585
Comment 15 Christian Marineau 2018-02-09 16:21:52 EST
*** Bug 1544016 has been marked as a duplicate of this bug. ***
Comment 18 errata-xmlrpc 2018-02-21 07:35:17 EST
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
Comment 19 Rich Jerrido 2018-07-18 08:38:29 EDT
*** Bug 1310698 has been marked as a duplicate of this bug. ***

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