Created attachment 713306 [details] disconnected system erroneously shows a green compliance Description of problem: Now that the compliance calculations of a system have been moved from the system to the candlepin server, it is unclear what the compliance color of a disconnected system should be. Previously, when a system with installed products is NOT registered to RHN and has no RHSM entitlements, the overall system compliance was red ("My Installed Products" tab was red). In today's build, this case is showing green (see attachment) which is not correct. However, it is unclear what should be correct. Should it be red to indicate non-compliance? yellow to indicate unknown compliance? or something gray? Also note that when a system with installed products is registered to RHN, but not RHSM, then the overall system compliance previously turned green and stayed green as long as there was a connection to RHN. Should this compatibility compliance behavior continue? Version-Release number of selected component (if applicable): [root@jsefler-7 ~]# rpm -q subscription-manager-gui subscription-manager-gui-1.8.4-1.git.31.00b0b78.el7.x86_64 How reproducible: Steps to Reproduce: [root@jsefler-7 ~]# yum repolist Loaded plugins: langpacks, product-id, rhnplugin, security, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. This system is not registered with RHN Classic or RHN Satellite. You can use rhn_register to register. RHN Satellite or RHN Classic support will be disabled. repolist: 0 [root@jsefler-7 ~]# subscription-manager-gui & Actual results: see attachment Expected results: unclear: red? yellow? gray?
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Fixed as of subscription-manager 1.8.8 Disconnected and unregistered systems appear gray/unknown status
Created attachment 757376 [details] confusing but yet correct Version: # rpm -qa | egrep "subscription-manager|python-rhsm" python-rhsm-1.8.12-1.git.0.d747a65.el5 subscription-manager-migration-data-1.11.3.1-1.git.1.78afd75.el5 subscription-manager-gui-1.8.10-1.git.1.b44c4b1.el5 subscription-manager-migration-1.8.10-1.git.1.b44c4b1.el5 subscription-manager-firstboot-1.8.10-1.git.1.b44c4b1.el5 subscription-manager-1.8.10-1.git.1.b44c4b1.el5 Verification # subscription-manager identity This system is not yet registered. Try 'subscription-manager register --help' for more information. # rhnreg_ks --serverUrl=https://xmlrpc.rhn.code.stage.redhat.com/XMLRPC --username=qa --password=redhatqa [root@dhcp129-119 ~]# subscription-manager identity server type: RHN Classic # yum repolist Loaded plugins: product-id, rhnplugin, security, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. This system is receiving updates from RHN Classic or RHN Satellite. repo id repo name status rhel-x86_64-server-5 Red Hat Enterprise Linux (v. 5 for 64-bit x86_64) 9,355 repolist: 9,355 Actual Result Green icon on the tab states it compliant Grey icons for installed products indicate unknown status VERIFIED
Please refer attachment in the above comment for verified result
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-2013-1332.html