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.
Bug 1223907 - subscription-manager man page is out of date for the servicelevel module
Summary: subscription-manager man page is out of date for the servicelevel module
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: William Poteat
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel68
TreeView+ depends on / blocked
 
Reported: 2015-05-21 16:43 UTC by John Sefler
Modified: 2016-05-10 20:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 20:36:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0797 0 normal SHIPPED_LIVE python-rhsm and subscription-manager bug fix and enhancement update 2017-01-06 16:31:50 UTC

Description John Sefler 2015-05-21 16:43:02 UTC
Description of problem:
The man page for subcription-manager currently reports the following for the servicelevel module...

   servicelevel OPTIONS
       The servicelevel command displays the current configured
       service level preference for products installed  on  the
       system.  For example, if the service-level preference is
       standard, then a subscription with  a  standard  service
       level  is  selected when auto-attaching subscriptions to
       the system.

              The servicelevel command does not set the service
              level  for  the system; it only shows its current
              setting or available settings. The  service-level
              preference  must  be set in the Subscription Man-
              ager GUI.

       --list Lists the available service levels.

       --show Shows the system’s current service-level  prefer-
              ence.  If  a service level is not set, then there
              is a message saying it is not set.

       --unset
              Removes any previously set service-level  prefer-
              ence.




The sentence "The service-level preference must be set in the Subscription Manager GUI." should be removed.  This is no longer true.

The following command line options are missing from the man page description...
  --set=SERVICE_LEVEL   service level to apply to this system
  --insecure            do not check the server SSL certificate against
                        available certificate authorities
  --serverurl=SERVER_URL
                        server URL in the form of https://hostname:port/prefix


Version-Release number of selected component (if applicable):
[root@jsefler-os6 ~]# rpm -q subscription-manager
subscription-manager-1.14.7-1.el6.x86_64

Comment 1 William Poteat 2015-11-13 15:15:08 UTC
master commit 87a47470398ab260164dd28a37b7f079e0163fff

Comment 2 Mike McCune 2016-03-28 23:45:25 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 4 Shwetha Kallesh 2016-04-19 06:29:22 UTC
Marking verified!!


[root@dhcp35-125 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 2.0.10-1
subscription management rules: 5.20
subscription-manager: 1.16.8-8.el6
python-rhsm: 1.16.6-1.el6


--set , --insecure , --serverurl options have been added
SERVICE-LEVEL OPTIONS
       The service-level command displays the current configured service level preference for products installed on the system.  For  example,  if  the
       service-level  preference  is  standard,  then a subscription with a standard service level is selected when auto-attaching subscriptions to the
       system.

       --serverurl=SERVER_URL
              Server URL in the form of https://hostname:port/prefix

       --insecure
              Do not check the server SSL certificate against available certificate authorities

       --show Shows the system’s current service-level preference. If a service level is not set, then there is a message saying it is not set.

       --list Lists the available service levels.

       --set=SERVICE_LEVEL
              Service level to apply to this system

       --unset
              Removes any previously set service-level preference.

Comment 6 errata-xmlrpc 2016-05-10 20:36:54 UTC
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.

https://rhn.redhat.com/errata/RHBA-2016-0797.html


Note You need to log in before you can comment on or make changes to this bug.