Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
It seems that bug 667991 was only partially fixed. When you are registered to rhn classic your Certificate status icon in the upper left corner of subscription-manager-gui is still RED, and the system fact 'system.entitlements_valid' is False.
According to bug 667991 subscription manager should think it is fully compliant whenever it is registered to rhn classic.
Version-Release number of selected component (if applicable):
subscription-manager-0.96.11-1.git.14.21c378d.el6.x86_64
subscription-manager-gnome-0.96.11-1.git.14.21c378d.el6.x86_64
python-rhsm-0.96.12-1.git.0.4862863.el6.noarch
subscription-manager-firstboot-0.96.11-1.git.14.21c378d.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. register to rhn classic (or touch /etc/sysconfig/rhn/systemid )
2. Start subscription-manager-gui
3. Look at the system facts
Actual results:
- The certificate status icon is RED.
- fact system.entitlements_valid is False
Expected results:
- The certificate status icon is GREEN. (and the message next to it references rhn_classic)
- fact system.entitlements_valid is True
Additional info:
Created attachment 525856[details]
Despite the red installed product certs, the overall Certificate Status is GREEN when registered to RHN Classic.
Verifying version...
[root@jsefler-onprem-62server ~]# rpm -q subscription-manager
subscription-manager-0.96.11-1.git.21.0fdd5b9.el6.x86_64
[root@jsefler-onprem-62server ~]# touch /etc/sysconfig/rhn/systemid
[root@jsefler-onprem-62server ~]# subscription-manager list --installed | grep Status
Installed Product Status
Status: Not Subscribed
Status: Not Subscribed
Status: Not Subscribed
Status: Not Subscribed
Status: Not Subscribed
Status: Not Subscribed
Status: Not Subscribed
Status: Not Subscribed
Status: Not Subscribed
Status: Not Subscribed
Status: Not Subscribed
Status: Not Subscribed
Status: Not Subscribed
Status: Not Subscribed
[root@jsefler-onprem-62server ~]# subscription-manager facts --list | grep valid
system.entitlements_valid: True
VERIFIED...
- despite all my non-subscribed products installed, my system.entitlements_valid fact is True
- the attached screenshot shows the overall Certificate Status is GREEN despite the RED installed products.
- the Certificate Status message in the gui is "This system is registered to RHN Classic"
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.
http://rhn.redhat.com/errata/RHBA-2011-1695.html