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:
An example in subscription-manager man page needs to be edited for status option. It shows a "status -> valid" this term is no longer used and replaced by term "current" to be in sync with SAM
Version-Release number of selected component (if applicable):
# subscription-manager version
server type: This system is currently not registered.
subscription management server: 0.8.29-1
subscription-manager: 1.9.11-1.el6
python-rhsm: 1.9.6-1.el6
How reproducible:
Always
Steps to Reproduce:
1. man subscription-manager
2. Look into "status" option
Actual results:
STATUS OPTIONS
The status command shows the current status of the products and attached subscriptions for the system. If some products are not fully covered or subscriptions have expired, then the
status command shows why subscriptions are not current.
[root@server ~]# subscription-manager status
+-------------------------------------------+
System Status Details
+-------------------------------------------+
Overall Status: Valid <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
--ondate=DATE
Shows the system status for a specific date in the future. The format of the date is YYYY-MM-DD.
[root@server ~]# subscription-manager status --ondate=2014-01-01
+-------------------------------------------+
System Status Details
+-------------------------------------------+
Overall Status: Insufficient
Expected results:
The term "valid" should be replaced by "Current"
>> Personal Note to dlackey: I'm not sure when it's decided to change version and date of a man-page but, it would be helpful if they were updated when the man page was edited.
commit 2c861a2a2dd108252c7fbc74231de38a559c6c88
Author: Bryan Kearney <bkearney>
Date: Wed Jan 29 14:18:43 2014 -0500
1020361: Replace the use of the term Valid with Current in the status command
Retested on ,
subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.9.2-1
subscription-manager: 1.10.13-1.el7
python-rhsm: 1.10.12-1.el7
Observed that now the term "Current" is displayed in the man page of subscription-manger status option section
STATUS OPTIONS
The status command shows the current status of the products and attached subscriptions for the system. If some products are not fully cov‐
ered or subscriptions have expired, then the status command shows why subscriptions are not current.
[root@server ~]# subscription-manager status
+-------------------------------------------+
System Status Details
+-------------------------------------------+
Overall Status: Current <<--- updated
--ondate=DATE
Shows the system status for a specific date in the future. The format of the date is YYYY-MM-DD.
[root@server ~]# subscription-manager status --ondate=2014-01-01
+-------------------------------------------+
System Status Details
+-------------------------------------------+
Overall Status: Insufficient
Hence, moving the bug to "Verified"
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Description of problem: An example in subscription-manager man page needs to be edited for status option. It shows a "status -> valid" this term is no longer used and replaced by term "current" to be in sync with SAM Version-Release number of selected component (if applicable): # subscription-manager version server type: This system is currently not registered. subscription management server: 0.8.29-1 subscription-manager: 1.9.11-1.el6 python-rhsm: 1.9.6-1.el6 How reproducible: Always Steps to Reproduce: 1. man subscription-manager 2. Look into "status" option Actual results: STATUS OPTIONS The status command shows the current status of the products and attached subscriptions for the system. If some products are not fully covered or subscriptions have expired, then the status command shows why subscriptions are not current. [root@server ~]# subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Valid <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< --ondate=DATE Shows the system status for a specific date in the future. The format of the date is YYYY-MM-DD. [root@server ~]# subscription-manager status --ondate=2014-01-01 +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Insufficient Expected results: The term "valid" should be replaced by "Current" >> Personal Note to dlackey: I'm not sure when it's decided to change version and date of a man-page but, it would be helpful if they were updated when the man page was edited.