Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:
Our current service level of None can be confusing and is slated to be updated (Does None mean I don't have a service level preference, is there no value there and I'm basically getting a null response?, what does not having a service level on this subscription mean for me as a customer?, etc).

One of the terminology updates for RHEL 7.0 is to update 'None' to be 'No Support' for service levels.

This would give us service levels on our subscriptions of:
No Support (currently None)
Self-Support
Standard
Premium

and possible service level preferences of:
Not Set
No Support (currently None)
Self-Support
Standard
Premium


Additional info:
This will impact subscription-manager service-level --set=none, as we'll now have to include no support in quotes or escape the space to get it to parse properly.
#subscription-manager service-level --set 'no support'
#subscription-manager service-level --set "No Support"
#subscription-manager service-level --set No\ Support