Bug 857918

Summary: "subscription-manager service-level --set "" " unsets service-level
Product: Red Hat Enterprise Linux 6 Reporter: Shwetha Kallesh <skallesh>
Component: subscription-managerAssignee: Bryan Kearney <bkearney>
Status: CLOSED WONTFIX QA Contact: Entitlement Bugs <entitlement-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4CC: bkearney, jsefler, wpoteat
Target Milestone: rcKeywords: Reopened
Target Release: 6.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-09 21:36:13 UTC Type: Bug
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: 771481    

Description Shwetha 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:

Comment 1 Bryan Kearney 2012-09-17 13:41:00 UTC
"" is in effect the same as unsetting.

Comment 2 John Sefler 2012-09-17 14:13:46 UTC
(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.

Comment 3 Bryan Kearney 2012-09-19 15:32:21 UTC
After string freeze, omving to rhel 6.4

Comment 5 Bryan Kearney 2012-10-05 20:38:00 UTC
Fixing the strings in candlepin server. Keeping the case that --set="" does an unset.

Comment 6 Bryan Kearney 2012-10-08 15:28:55 UTC
Fixed in candlepin master at 3e4521cbf0760bb9cd4e55aa0fdd9494719c7fe3. You will need 0.7.13 or later to verify the fix.

Comment 9 Shwetha Kallesh 2012-11-07 09:04:37 UTC
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

Comment 10 William Poteat 2012-11-09 21:39:08 UTC
Agreement from jsefler on resolution.