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.
Description of problem:
I provisioned an atomic 7.2 content host from satellite 6.2. Host was provisioned successfully. Later, I registered the host with satellite server and webUI shows subscription status as 'warning' and in green color.
Version-Release number of selected component (if applicable):
Satellite 6.2 beta snap7.1
How reproducible:
Steps to Reproduce:
1. provision and register atomic host with satellite 7.2
2.
3.
Actual results:
go to content-host -> select host -> provisioning details -> subscription status shown as 'warning and that too in 'Green color.
under content host -> details -> subscription status set as 'Fully entitled'
under content-host -> subscriptions -> subscriptions details_. status shown as red dot.
Expected results:
- Status should be green at all places
- instead of 'warning' under provisioning details, it should be reflected as ok
Additional info:
Hi Sachin, Although this bug was created for an atomic host, it appears to be the same general issue raised by bug 1321041. Would you object to closing this one as a duplicate with a comment to the other bug to verify for both atomic and non-atomic hosts?