Description of problem: The following commit was too agressive.... Commit 6241cd1495b9feac2ed123f60405061b03815721 by Bryan Kearney 749332: Normalize the error messages for not being registered Version-Release number of selected component (if applicable): [root@jsefler-onprem-5server ~]# rpm -q subscription-manager subscription-manager-0.98.3-1.git.12.130b7ce.el5_7 How reproducible: Steps to Reproduce: [root@jsefler-onprem-5server ~]# subscription-manager unregister Error: You need to register this system by running `register` command. Try register --help. [root@jsefler-onprem-5server ~]# echo $? 255 Expected results: [root@jsefler-onprem-62server ~]# subscription-manager unregister This system is currently not registered. [root@jsefler-onprem-62server ~]# echo $? 1 ^^^ THESE HAVE BEEN THE EXPECTED RESULTS SINCE RHEL61 Additional info:
I suggest undoing commit 6241cd1495b9feac2ed123f60405061b03815721 and then revisiting a different solution for bug 749332.
This bug report previously had all acks and release flags approved. However since at least one of its acks has been changed, the release flags have been reset to ? by the bugbot (pm-rhel). The ack needs to become approved before the release flags can become approved again.
This bugzilla has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being [proposed|marked] as a blocker for this release. Please resolve ASAP.
Commit 7d7dd1e3f04bf2c5764b3d92668e427e0ed057dd in master
Moving the bug to verified.. RPM used: [root@tiger entitlement]# rpm -qa | grep subscription-manager subscription-manager-gnome-0.98.3-1.git.16.14460bc.el5_7 subscription-manager-firstboot-0.98.3-1.git.16.14460bc.el5_7 subscription-manager-migration-0.98.3-1.git.16.14460bc.el5_7 subscription-manager-0.98.3-1.git.16.14460bc.el5_7 [root@tiger entitlement]# subscription-manager unregister This system is currently not registered.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description necessary
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-2012-0154.html