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.

Bug 1977720

Summary: Make messaging in service-level module compliant with rest of the system purpose attributes
Product: Red Hat Enterprise Linux 9 Reporter: Rehana <redakkan>
Component: subscription-managerAssignee: Jiri Hnidek <jhnidek>
Status: CLOSED ERRATA QA Contact: Red Hat subscription-manager QE Team <rhsm-qe>
Severity: low Docs Contact:
Priority: medium    
Version: 9.0CC: cdonnell, jhnidek, ptoscano
Target Milestone: betaKeywords: Triaged
Target Release: 9.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: subscription-manager-1.29.21-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 15:58:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rehana 2021-06-30 10:54:29 UTC 
Description of problem:
Observed the service-level module is showing a slightly different message compared to rest of the system purpose modules

Version-Release number of selected component (if applicable):
# subscription-manager version
server type: This system is currently not registered.
subscription management server: 3.2.18-1
subscription management rules: 5.41
subscription-manager: 1.29.15-1.git.14.dcbf3e7.el9

How reproducible:

Steps to Reproduce:
1.For ex : 
# subscription-manager syspurpose addons --list --username=bad-username --password=password
Unable to get the list of valid values for the system purpose "addons".

# subscription-manager addons --list --username=bad-username --password=password
Unable to get the list of valid values for the system purpose "addons".

# subscription-manager service-level --list --username=bad-username --password=password
HTTP error (401 - Unauthorized): Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html

# subscription-manager syspurpose service-level --list --username=bad-username --password=password
HTTP error (401 - Unauthorized): Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html

Actual results:
Notice the messaging is not consistent.

Expected results:
This bug expects all messaging in service-level module to be compliant with other system purpose modules 

Additional info:
Comment 1 Pino Toscano 2021-07-01 07:38:51 UTC 
This happens because the implementation of the 'service-level' syspurpose command differs from the implementation used by other syspurpose commands.
A better idea would be to eventually switch 'service-level' to the same implementation of the others, if possible. This should make its behaviour and diagnostic coherent with the others.
Comment 5 Rehana 2021-11-15 09:54:53 UTC 
Reproducing the failure : 

subscription management server: 3.2.21-1
subscription management rules: 5.41
subscription-manager: 1.29.18-2.el9

# subscription-manager syspurpose addons --list --username=bad-username --password=password
Unable to get the list of valid values for the system purpose "addons".

# subscription-manager addons --list --username=bad-username --password=password
Unable to get the list of valid values for the system purpose "addons".

# subscription-manager service-level --list --username=bad-username --password=password
HTTP error (401 - Unauthorized): Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html

# subscription-manager syspurpose service-level --list --username=bad-username --password=password
HTTP error (401 - Unauthorized): Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html

Pre-testing on : 

# subscription-manager version
server type: This system is currently not registered.
subscription management server: 3.2.21-1
subscription management rules: 5.41
subscription-manager: 1.29.21-1.git.0.d3fb25b.el9

# subscription-manager syspurpose addons --list --username=bad-username --password=password
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP error code 401: Unauthorized)

# subscription-manager addons --list --username=bad-username --password=password
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP error code 401: Unauthorized)

# subscription-manager service-level --list --username=bad-username --password=password
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP error code 401: Unauthorized)

# subscription-manager syspurpose service-level --list --username=bad-username --password=password
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP error code 401: Unauthorized)

Observed that the following message " Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP error code 401: Unauthorized)" is displayed consistently across all the syspurpose modules.

Marking Verified:tested.
Comment 9 Rehana 2021-12-01 12:30:58 UTC 
Verifying on :
-------------

# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 3.2.21-1
subscription management rules: 5.41
subscription-manager: 1.29.21-1.el9

# subscription-manager syspurpose addons --list --username=bad-username --password=password
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP error code 401: Unauthorized)

# subscription-manager addons --list --username=bad-username --password=password
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP error code 401: Unauthorized)

# subscription-manager service-level --list --username=bad-username --password=password
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP error code 401: Unauthorized)

# subscription-manager syspurpose service-level --list --username=bad-username --password=password
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP error code 401: Unauthorized)

# subscription-manager role --list --username=bad-username --password=password
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP error code 401: Unauthorized)

# subscription-manager syspurpose role --list --username=bad-username --password=password
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP error code 401: Unauthorized)

# subscription-manager usage --list --username=bad-username --password=password
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP error code 401: Unauthorized)

# subscription-manager syspurpose usage --list --username=bad-username --password=password
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP error code 401: Unauthorized)

All the test scenarios passed. Moving the bug to Verified!!
Comment 11 errata-xmlrpc 2022-05-17 15:58:13 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 (new packages: subscription-manager), 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://access.redhat.com/errata/RHBA-2022:3984