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.
Description of problem:
The stderr/exitCode thrown by "rhn-migrate-classic-to-rhsm --activation-key=foo" without specifying --org is not consistent with the rest of subscription-manager.
[root@ibm-z10-08 ~]# rhn-migrate-classic-to-rhsm --activation-key=foo
The --activation-key option requires that a --org be given.
[root@ibm-z10-08 ~]# echo $?
1
Example of a command that throws a better exitCode
[root@ibm-z10-08 ~]# subscription-manager list --no-overlap
Error: --no-overlap is only applicable with --available
[root@ibm-z10-08 ~]# echo $?
64
Version-Release number of selected component (if applicable):
[root@ibm-z10-08 ~]# rpm -q subscription-manager-migration
subscription-manager-migration-1.14.5-1.el6.s390x
How reproducible:
Steps to Reproduce:
[root@ibm-z10-08 ~]# rhn-migrate-classic-to-rhsm --activation-key=foo
The --activation-key option requires that a --org be given.
[root@ibm-z10-08 ~]# echo $?
1
Actual results:
exitCode 1
Expected results:
exitCode 64 from python EX_USAGE
commit 270f2a3e5f7d55b69a6f98c160d38362961b3059
Author: Chris Rog <crog>
Date: Mon May 4 11:44:10 2015 -0400
Specified error codes on system_exit in rhn-migrate-classic-to-rhsm
- Many calls to system_exit now specify an error code on exit instead
of using a common non-zero value
Exit code is now changed to 64 from 1
[root@cisco-c210-01 ~]# rpm -qa | grep subscription-manager
subscription-manager-migration-1.14.7-1.el6.x86_64
subscription-manager-1.14.7-1.el6.x86_64
[root@cisco-c210-01 ~]# rhn-migrate-classic-to-rhsm --activation-key=foo
The --activation-key option requires that a --org be given.
[root@cisco-c210-01 ~]# echo $?
64
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.
https://rhn.redhat.com/errata/RHBA-2015-1345.html