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:
Version-Release number of selected component (if applicable):
How reproducible:
3/3
Prerequisites.
Rhel6.3 with following rpm.
subscription-manager-migration-0.99.15-1.el6.x86_64
subscription-manager-gnome-0.99.15-1.el6.x86_64
subscription-manager-migration-data-1.12.1.5-1.el6.noarch
subscription-manager-0.99.15-1.el6.x86_64
subscription-manager-debuginfo-0.99.15-1.el6.x86_64
subscription-manager-firstboot-0.99.15-1.el6.x86_64
Steps to verify :
Registered client to older candlepin i used (10.65.201.177).
execute following command on client console.
subscription-manager release –list
Expected Result :
Following message should display on console.
ERROR: The 'release' command is not supported by the server.
Actual Result :
[root@sachbeta1 ~]# subscription-manager release --list
[root@sachbeta1 ~]# echo $?
0
Working fine with release , and release –set
[root@sachbeta1 ~]# subscription-manager release
ERROR: The 'release' command is not supported by the server.
[root@sachbeta1 ~]# subscription-manager release --set=2303030303003
ERROR: The 'release' command is not supported by the server.
Output of --list is independent of candlepin version. Instead it is
dependent on the content available on the cdn (aka, baseurl from the config). (and to a lesser degree, on what products and entitlements the system has).
Ie, if a system isn't subscribe to a product (and in particular, a "rhel" product) "release --list" will be empty. It will also be empty if there is no rhel content on the cdn (or it 404's, etc).
What is baseurl pointed at in this case?
Discussed this with spandey a bit. His concern is that not showing an error message about release being unsupported in this case is misleading, since you get into a case where you would be able to "release --list" and see some output, but not actually able to set your release to those (because of an older candlepin). If you tried, then you would receive the error about release being unsupported.
While not optimal, I think this case is ok. But probably something we should revisit for the next release.