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 1020361 - man page entry for status option needs to be edited
Summary: man page entry for status option needs to be edited
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Bryan Kearney
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel70
TreeView+ depends on / blocked
 
Reported: 2013-10-17 14:09 UTC by Sharath Dwaral
Modified: 2015-03-23 01:14 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:00:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Sharath Dwaral 2013-10-17 14:09:18 UTC 
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.
Comment 1 Bryan Kearney 2014-01-29 19:19:16 UTC 
https://github.com/candlepin/subscription-manager/pull/878
Comment 2 Bryan Kearney 2014-01-30 17:33:17 UTC 
commit c047fba9da624d7d6c5351db97f55ec4ed893ed5
Author: Bryan Kearney <bkearney>
Date:   Wed Jan 29 13:06:42 2014 -0500

    1039914: Update the rhsm-debug man page
Comment 3 Bryan Kearney 2014-01-30 17:33:39 UTC 
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
Comment 5 Rehana 2014-02-06 07:35:42 UTC 
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"
Comment 6 Rehana 2014-02-06 07:39:51 UTC 
man -P cat subscription-manager | tail -1
version 2.8  January 29, 2014  subscription-manager(8)
Comment 7 Ludek Smid 2014-06-13 12:00:35 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.