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:
crm_resource has undocumented -c option.

Version-Release number of selected component (if applicable):
pacemaker-1.1.12-4.el6.x86_64

How reproducible:


Steps to Reproduce:
1. crm_resource --help
2. man crm_resource
3.

Actual results:
no info about -c option

Expected results:
-c option documented in both steps (--help and man)

Additional info:

Right, we don't want to advertise this to users.
This option is intended only fir use by CTS.

It is used in init scripts.

Hiding options also does not sound like a good idea to me. I'd prefer documenting it even with a note that it's for internal use, with possible warning if it can have destructive consequences (like we are used to with --force and similar options elsewhere).

I really can't see this happening. Too much other stuff going on.