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:
With help from cduryee, I am putting together some automated tests for subscription-manager redeem that will run against an onpremises candlepin server with a testing patch that simulates the code from aedwards to replace the candlepin DefaultSubscriptionServiceAdapter.java.
When all is good, it appears that aedwards' SubscriptionServiceAdapter.java will thrown a new AcceptedRequestException with a message "Your subscription activation is being processed and should be available soon."
This is good because in the subscription-manager-gui, an information dialog will be presented to the user.
On the command line, an exit code of 255 is being returned. This is bad. As such, my automated tests believe that there is an error. We are expecting an exit code of 0 for a successful call to redeem.
Version-Release number of selected component (if applicable):
[root@jsefler-onprem-62server ~]# rpm -q subscription-manager
subscription-manager-0.96.4-1.git.80.a26379e.el6.x86_64
How reproducible:
Steps to Reproduce:
[root@jsefler-onprem-62server ~]# subscription-manager redeem --email=jsefler
Your subscription activation is being processed and should be available soon. You will be notified via email once it is available. If you have any questions, additional information can be found here: https://access.redhat.com/kb/docs/DOC-53864.
[root@jsefler-onprem-62server ~]# echo $?
255
^^^ Expected an exit code of 0
Verifying Version...
[root@jsefler-onprem-62server ~]# rpm -q subscription-manager
subscription-manager-0.96.6-1.git.8.6e109e4.el6.x86_64
[root@jsefler-onprem-62server ~]# subscription-manager redeem --email=tester
Your subscription activation is being processed and should be available soon. You will be notified via email once it is available. If you have any questions, additional information can be found here: https://access.redhat.com/kb/docs/DOC-53864.
[root@jsefler-onprem-62server ~]# echo $?
0
^^^ VERIFIED The AcceptedRequestException thrown by SubscriptionServiceAdapter.java is results in an exitCode of 0 by subscription-manager.
Also verifying error case when the candlepin server does NOT support subscription redemption and throws a ServiceUnavailableException...
[root@jsefler-onprem-62server ~]# subscription-manager redeem --email=tester
Standalone candlepin does not support redeeming a subscription.
[root@jsefler-onprem-62server ~]# echo $?
255
^^^ VERIFIED The error case results in a 255 exit code by subscription-manager.
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