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.

Bug 797294

Summary: subscription-manager-migration is throwing a SyntaxError
Product: Red Hat Enterprise Linux 6 Reporter: John Sefler <jsefler>
Component: subscription-managerAssignee: Bryan Kearney <bkearney>
Status: CLOSED ERRATA QA Contact: Entitlement Bugs <entitlement-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3CC: skallesh, spandey
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 13:06:09 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: 738066    

Description John Sefler 2012-02-24 20:17:18 UTC
Description of problem:

[root@jsefler-r63-server ~]# rhn-migrate-classic-to-rhsm --help
  File "/usr/sbin/rhn-migrate-classic-to-rhsm", line 80
    (options, args) = parser.parse_args()
                    ^
SyntaxError: invalid syntax


Version-Release number of selected component (if applicable):
[root@jsefler-r63-server ~]# rpm -q subscription-manager-migration
subscription-manager-migration-0.99.8-1.git.17.2604172.el6.x86_64

Comment 1 Bryan Kearney 2012-02-24 21:34:14 UTC
fixed  in e98707cb42e9051f9ba2cae031eb401a434adbcd

Comment 3 Shwetha Kallesh 2012-02-27 06:33:14 UTC
Moving the bug to verified.

RPM used:

[root@dhcp201-166 ~]# rpm -qa | grep subscription-manager
subscription-manager-gnome-0.99.8-1.el6.x86_64
subscription-manager-0.99.8-1.el6.x86_64
subscription-manager-migration-0.99.8-1.el6.x86_64
subscription-manager-migration-data-1.12-1.el6.noarch
subscription-manager-debuginfo-0.99.8-1.el6.x86_64



[root@dhcp201-166 ~]# rhn-migrate-classic-to-rhsm --help
Usage: /usr/sbin/rhn-migrate-classic-to-rhsm [--force|--cli-only|--help|--no-auto]

Options:
  -f, --force     Ignore channels not available on RHSM
  -c, --cli-only  Don't launch the GUI tool to subscribe the system, just use
                  the CLI tool which will do it automatically
  -n, --no-auto   Don't execute the autosubscribe option while registering
                  with subscription manager.
  -h, --help      show this help message and exit

Comment 5 errata-xmlrpc 2012-06-20 13:06:09 UTC
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-0804.html