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:
This is a bug request to improve the feedback message and consistency when trying to list available usage|role|addons|service-level as suggested by the help...
[root@kvm-02-guest10 ~]# subscription-manager usage --help | grep -- --list
--list list all usage available
[root@kvm-02-guest10 ~]# subscription-manager role --help | grep -- --list
--list list all role available
[root@kvm-02-guest10 ~]# subscription-manager addons --help | grep -- --list
--list list all addons available
[root@kvm-02-guest10 ~]# subscription-manager service-level --help | grep -- --list
--list list all service_level_agreement available
Notice above that the help information for --list is rather consistent and describes that it's function is to list available values - not "provide" values.
Version-Release number of selected component (if applicable):
[root@kvm-02-guest10 ~]# rpm -q subscription-manager
subscription-manager-1.28.5-1.el8.x86_64
How reproducible:
When using a new account that has no subscriptions available....
Steps to Reproduce:
[root@kvm-02-guest10 ~]# subscription-manager usage --list --username=stage_newuser --password=REDACTED --org=13056508
No valid values provided for "usage"
[root@kvm-02-guest10 ~]# subscription-manager role --list --username=stage_newuser --password=REDACTED --org=13056508
No valid values provided for "role"
[root@kvm-02-guest10 ~]# subscription-manager addons --list --username=stage_newuser --password=REDACTED --org=13056508
No valid values provided for "addons"
[root@kvm-02-guest10 ~]# subscription-manager service-level --list --username=stage_newuser --password=REDACTED --org=13056508
This org does not have any subscriptions with service levels.
Notice above that the feedback when listing available values is not consistent and uses the word "provided" which is confusing from the perspective of the user who is trying to list "available" values.
Actual results:
No valid values provided for "usage"
No valid values provided for "role"
No valid values provided for "addons"
This org does not have any subscriptions with service levels.
Proposed results:
This org does not have any subscriptions with an available "usage".
This org does not have any subscriptions with an available "role".
This org does not have any subscriptions with an available "addons".
This org does not have any subscriptions with an available "service-level".
Additional info:
This bug FailedQA in comment 1 because the fix did not yet land in subscription-manager-1.28 from comment 2. However, I would still argue that this bug will still failQA because the actual results will be missing a trailing period to complete the sentence.
Nevertheless, I suggest resolving new Bug 1959048 which manipulates the same strings and then using this bugzilla to backport/cherry-pick the fix back to subscription-manager-1.28 for the benefit of RHEL-8.5.
# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 3.2.19-1
subscription management rules: 5.41
subscription-manager: 1.28.19-1.el8
# rpm -q subscription-manager --changelog | grep 1897767
- 1897767: improve wording for invalid syspurpose values (ptoscano)
- 1897767: improve wording for missing or empty syspurpose values
- 1897767: what does 'No valid values provided for usage' mean to the user for
# subscription-manager usage --list --username=***** --password=****
There are no available values for the system purpose "usage" from the available subscriptions in this organization.
# subscription-manager role --list --username=***** --password=****
There are no available values for the system purpose "role" from the available subscriptions in this organization.
# subscription-manager service-level --list --username=***** --password=****
There are no available values for the system purpose "service_level" from the available subscriptions in this organization.
# subscription-manager addons --list --username=***** --password=****
There are no available values for the system purpose "addons" from the available subscriptions in this organization.
Based on the above observation , moving the bug to Verified!!
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 (subscription-manager bug fix and enhancement update), 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-2021:4390
Description of problem: This is a bug request to improve the feedback message and consistency when trying to list available usage|role|addons|service-level as suggested by the help... [root@kvm-02-guest10 ~]# subscription-manager usage --help | grep -- --list --list list all usage available [root@kvm-02-guest10 ~]# subscription-manager role --help | grep -- --list --list list all role available [root@kvm-02-guest10 ~]# subscription-manager addons --help | grep -- --list --list list all addons available [root@kvm-02-guest10 ~]# subscription-manager service-level --help | grep -- --list --list list all service_level_agreement available Notice above that the help information for --list is rather consistent and describes that it's function is to list available values - not "provide" values. Version-Release number of selected component (if applicable): [root@kvm-02-guest10 ~]# rpm -q subscription-manager subscription-manager-1.28.5-1.el8.x86_64 How reproducible: When using a new account that has no subscriptions available.... Steps to Reproduce: [root@kvm-02-guest10 ~]# subscription-manager usage --list --username=stage_newuser --password=REDACTED --org=13056508 No valid values provided for "usage" [root@kvm-02-guest10 ~]# subscription-manager role --list --username=stage_newuser --password=REDACTED --org=13056508 No valid values provided for "role" [root@kvm-02-guest10 ~]# subscription-manager addons --list --username=stage_newuser --password=REDACTED --org=13056508 No valid values provided for "addons" [root@kvm-02-guest10 ~]# subscription-manager service-level --list --username=stage_newuser --password=REDACTED --org=13056508 This org does not have any subscriptions with service levels. Notice above that the feedback when listing available values is not consistent and uses the word "provided" which is confusing from the perspective of the user who is trying to list "available" values. Actual results: No valid values provided for "usage" No valid values provided for "role" No valid values provided for "addons" This org does not have any subscriptions with service levels. Proposed results: This org does not have any subscriptions with an available "usage". This org does not have any subscriptions with an available "role". This org does not have any subscriptions with an available "addons". This org does not have any subscriptions with an available "service-level". Additional info: