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:


Version-Release number of selected component (if applicable):


How reproducible:
5/5

Prerequisites :
Client : Rhel5.7 with following subscription manager client 
subscription-manager-firstboot-0.95.5.18-1.git.4.364aa10.el5

subscription-manager-0.95.5.18-1.git.4.364aa10.el5

subscription-manager-gnome-0.95.5.18-1.git.4.364aa10.el5

Steps to Reproduce : 

Execute following command on console 
[root@dhcp201-172 ~]# subscription-manager unsubscribe --serial lkjskshs

Expected Result : 
Proper Message should display on console for invalid serial number 

Actual Result : 
 
[root@dhcp201-172 ~]# subscription-manager unsubscribe --serial lkjskshs --proxy 10.65.193.99:3128

'lkjskshs' is not a valid serial number

-1

Moving to 6.2 since that's the next tracker and the bug needs to be fixed in the master branch, but this bug will only manifest on el5 (just fyi for developers).

Fix in subscription-manager.git master branch: cfbd5a361a8fd4210e8fb27fc9b317e8f547ee25

handle_exception method now checks if we're looking at a SystemExit exception, and if so skips all the processing / printing of the exception message. (as this is a pretty clear indication we already did some error handling and called sys.exit)

Moving the bug to verified as it result is as expected

RPM used :

subscription-manager-0.96.4-1.git.62.75efb0a.el6.x86_64
subscription-manager-firstboot-0.96.4-1.git.62.75efb0a.el6.x86_64
subscription-manager-gnome-0.96.4-1.git.62.75efb0a.el6.x86_64

Steps to reproduce :

subscription-manager unsubscribe --serial lkjskshs

Output:

'lkjskshs' is not a valid serial number

Unable to change the status...Pls change the status to verified

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