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 1192094 - man page for subscription-manager references "servicelevel" command when it should say "service-level"
Summary: man page for subscription-manager references "servicelevel" command when it s...
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: Chris "Ceiu" Rog
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel68
TreeView+ depends on / blocked
 
Reported: 2015-02-12 15:42 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:16 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-02-12 15:42:39 UTC 
Description of problem:
There are some typos in the subscription-manager man page that reference the "servicelevel" command module when in reality it is the "service-level" command module.

Warning: Do not confuse the "service-level" module with the "--servicelevel" option.



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


How reproducible:


Steps to Reproduce:
[root@jsefler-os7 ~]# man subscription-manager | egrep "[^-]servicelevel"
              7. servicelevel
   servicelevel OPTIONS
       The  servicelevel command displays the current configured service level preference for prod‐
              The servicelevel command does not set the service level for the system; it only shows


Actual results:
  servicelevel

Expected results:
  service-level


Additional info:
Do NOT change these occurrences of "--servicelevel".  They are correct....
[root@jsefler-os7 ~]# man subscription-manager | egrep -- "--servicelevel"
       --servicelevel=LEVEL
       --servicelevel=LEVEL
       scriptions, the --servicelevel option. In this case, the --servicelevel option sets a  pref‐
              --auto-attach --servicelevel=premium
       scriptions, the --servicelevel option. In this case, the --servicelevel option sets a  pref‐
              subscription-manager attach --auto --servicelevel=premium
              /usr/sbin/subscription-manager register --username admin --password secret --org 'east colo' --auto-attach --servicelevel=premium --force
Comment 2 John Sefler 2015-02-24 16:30:50 UTC 
Deferring for resolution during RHEL6.7 development cycle
Comment 3 Chris "Ceiu" Rog 2015-06-04 15:00:24 UTC 
commit 961aa8d43ef6e18ef9cde2e740be8462101bb4c6
Author: Chris Rog <crog>
Date:   Thu Apr 9 10:16:49 2015 -0400

    1192094: Fixed erroneous usage of "servicelevel" for the subman command
    
    - Updated the subscription-manager man page to no longer refer to the
      "service-level" command as "servicelevel."
Comment 6 Shwetha Kallesh 2015-12-09 09:57:46 UTC 
Instances of servicelevel has been changed to service-level , whereever it refers to service-level as a module and not as an option

[root@pogo-cn1100-01 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.9.51.11-1
subscription management rules: 5.15
subscription-manager: 1.16.6-1.el6
python-rhsm: 1.16.4-1.el6


[root@pogo-cn1100-01 ~]#  man subscription-manager | egrep "[^-]servicelevel"
[root@pogo-cn1100-01 ~]#  man subscription-manager | egrep "service-level"
              7. service-level
       service-level  preference is standard, then a subscription with a stan-
       --show Shows the system’s current service-level preference. If  a  ser-
              Removes any previously set service-level preference.

-------------------------------------------------------------------------------

--servicelevel instances are unchanged

[root@pogo-cn1100-01 ~]# man subscription-manager | grep  "servicelevel" 
       --servicelevel=LEVEL
       --servicelevel=LEVEL
               scriptions, the --servicelevel option. In this case, the --servicelevel option sets a  pref‐
              --auto-attach --servicelevel=premium
              subscription-manager attach --servicelevel=premium
              /usr/sbin/subscription-manager register --username admin --password secret --org ’east colo’ --auto-attach --servicelevel=premium --force
Comment 8 errata-xmlrpc 2016-05-10 20:36:16 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.