Description of problem: We handle unset service levels a little differently than unset release versions. service-level --show returns "Current service level:", whereas release --show returns "Release not set". I think saying it isn't set is clearer than showing an empty string. Could we update service-level to show "Service level preference not set" for cases where it isn't set? Version-Release number of selected component (if applicable): subscription-manager-1.0.2-1.git.2.2b23e6e
commit 614fbddbd53c74ea580ad0c980b2a98bda587988 Author: Alex Wood <awood> Date: Mon Jun 4 11:21:10 2012 -0400 825286: Handle unset service levels in a manner similar to unset release versions.
Verified using following rpm subscription-manager-1.0.3-1.git.69.b87abd7.el5 subscription-manager-firstboot-1.0.3-1.git.69.b87abd7.el5 subscription-manager-migration-data-1.11.1.1-1.git.2.c7fbafe.el5 subscription-manager-migration-1.0.3-1.git.69.b87abd7.el5 subscription-manager-gui-1.0.3-1.git.69.b87abd7.el5 [root@dhcp193-122 ~]# subscription-manager service-level --show Service level preference not set tested with unset [root@dhcp193-122 ~]# subscription-manager service-level --unset Service level preference has been unset [root@dhcp193-122 ~]# subscription-manager service-level --show Service level preference not set Working fine resolving defect as verified
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-2013-0033.html