Bug 706889
Summary: | “-1” displayed on console while unsubscribe invalid serial | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | spandey |
Component: | subscription-manager | Assignee: | Devan Goodwin <dgoodwin> |
Status: | CLOSED ERRATA | QA Contact: | John Sefler <jsefler> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2 | CC: | dgoodwin, jmolet, jsefler, kbanerje, skallesh, spandey |
Target Milestone: | rc | ||
Target Release: | 6.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 17:14:28 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 682238 |
Description
spandey
2011-05-23 11:32:09 UTC
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 |