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 985152 - /usr/libexec/rhsmd --help description for --force-signal improvement
Summary: /usr/libexec/rhsmd --help description for --force-signal improvement
Keywords:
Status: CLOSED WONTFIX
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
: 7.0
Assignee: candlepin-bugs
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel70
TreeView+ depends on / blocked
 
Reported: 2013-07-16 23:50 UTC by John Sefler
Modified: 2013-10-11 15:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-11 15:35:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description John Sefler 2013-07-16 23:50:50 UTC 
Description of problem:

[root@jsefler-5 ~]# /usr/libexec/rhsmd --help
Usage: rhsmd [OPTIONS]

options:
  -h, --help            show this help message and exit
  -d, --debug           Display debug messages
  -k, --keep-alive      Stay running (don't shut down after the first dbus
                        call)
  -s, --syslog          Run standalone and log result to syslog
  -f FORCE_SIGNAL, --force-signal=FORCE_SIGNAL
                        Force firing of a signal (valid, expired, warning,
                        partial, classic or registration_required)
  -i, --immediate       Fire forced signal immediately (requires --force-
                        signal)


The description for force-signal needs improvement.  How about this:
Force firing of a signal (valid, expired, warning, partial) (requires RHN Classic or Subscription Management registration)

Version-Release number of selected component (if applicable):
[root@jsefler-5 ~]# rpm -q subscription-manager
subscription-manager-1.8.13-1.el5
Comment 1 RHEL Program Management 2013-07-17 00:19:52 UTC 
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.
Comment 2 Matt Reid 2013-07-18 17:42:53 UTC 
I'm not familiar with rhsmd as I don't think its autocomplete-able (and doesn't have a description string in that --help), but I'm not sure your revision accurately captures what force-signal does. The way I read the current string is that you can use force-signal to throw one of {valid, expired, warning, partial, already-registered-with-classic, unregistered} signals/messages. Not that you need to be registered with RHN Classic or RHSM before you can force one of {valid, expired, warning, partial}, but maybe the string really is that misleading :)

If we're expecting users might interact with rhsmd, we may want to make it tab-complete-able, have a description string, and tweak the strings to match the cli consistency stuff we went through earlier (capitalize Options:, start option descriptions with a lowercase letter).
Comment 3 Bryan Kearney 2013-07-18 20:26:20 UTC 
string change.. pushing.
Comment 5 Bryan Kearney 2013-10-11 15:35:00 UTC 
This is really not meant to be user facing. I tend to agree with Matt that the text is a bit misleading. I am going to close this now. If you have another text, go ahead and re-open.
Note You need to log in before you can comment on or make changes to this bug.