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.
DescriptionShwetha Kallesh
2012-09-17 13:38:11 UTC
Description of problem:
"subscription-manager service-level --set "" " unsets service-level
Version-Release number of selected component (if applicable):
[root@dhcp201-110 pki]# rpm -qa | grep subscription-manager
subscription-manager-1.0.17-1.el5
subscription-manager-gui-1.0.17-1.el5
subscription-manager-firstboot-1.0.17-1.el5
How reproducible:
Steps to Reproduce:
1.subscription-manager service-level --set ""
service level preference has been unset
2.
3.
Actual results:
Expected results:
Error:Cannot set service level to ""
Additional info:
(In reply to comment #1)
> "" is in effect the same as unsetting.
Agreed. This was the functional behavior implemented before the --unset option was invented. It was the only way for the user to effectively remove their service level preference.
However, now that the --unset option exists, using --set="" is strange. Shwetha is suggesting that it should now be considered an error; or it could just throw the not available service level result.
# subscription-manager service-level --set=" is not "
Service level is not is not available to consumers of organization admin.
^^^^^^
THIS REALLY SHOULD BE SURROUNDED BY SINGLE QUOTES
Moving back to ASSIGNED for further consideration.
Moving back to new
[root@rhel-64-server ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.7.18-1
subscription-manager: 1.1.5-1.el6
python-rhsm: 1.1.4-1.el6
[root@rhel-64-server ~]# subscription-manager service-level --set ""
Service level preference has been unset
Description of problem: "subscription-manager service-level --set "" " unsets service-level Version-Release number of selected component (if applicable): [root@dhcp201-110 pki]# rpm -qa | grep subscription-manager subscription-manager-1.0.17-1.el5 subscription-manager-gui-1.0.17-1.el5 subscription-manager-firstboot-1.0.17-1.el5 How reproducible: Steps to Reproduce: 1.subscription-manager service-level --set "" service level preference has been unset 2. 3. Actual results: Expected results: Error:Cannot set service level to "" Additional info: