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.

Description of problem:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Deployment_Guide/mng-service-levels.html

In section 4.8. Managing Service Levels on Systems, the doc currently says "Two attributes are displayed, per subscription: its support level and its support type".   Then the screenshot shows "Support Level" and Support Type" circled in red.

We learned from mkhusid that we should use the word "Service" rather than "Support".  In the attached screenshot you will see that the application currently uses "Service" for both of these terms.  Hence the screenshot in the doc is currently wrong.

Section 4.8.3. Viewing Service Level Settings

To view available service levels for the syste, use the --list option.
                                         ^^^^^
                                         TYPO system

Section 4.8.3. Viewing Service Level Settings

Preferences for default service levels can be specified for an organization and for a local system, and those two settings do not have to be the same.

^^^ THIS SENTENCE IS TRUE

The current setting for the entire organization is shown with the --org option: 

^^^ THIS SENTENCE IS NOT TRUE, WHICH MAKES THE FOLLOWING EXAMPLE WRONG..

[root#server ~]# subscription-manager service-level --org admin
Current service level: Standard


The --org option for subscription-manager service-level is used in conjunction with the --username and --password to provide credentials for --list to see the available service levels before your system is actually registered.

There is NOT currently a way to see or set the default service level for an org using subscription-manager cli or gui.  I believe this functionality is part of SAM and rhsm-web.

Removed --org reference:
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/viewing-slas-subscr.html