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:
man pcs shows 'stickiness' option in the example of usage for 'pcs resource meta':
meta <resource id | group id | clone id> <meta options> [--wait[=n]]
Add specified options to the specified resource, group or clone. Meta options should be in the format of name=value, options may be removed by setting an option without a
value. If --wait is specified, pcs will wait up to 'n' seconds for the changes to take effect and then return 0 if the changes have been processed or 1 otherwise. If 'n'
is not specified it defaults to 60 minutes.
Example: pcs resource meta TestResource failure-timeout=50 stickiness=
Expected result:
To achieve the correct functionality, 'resource-stickiness' meta option needs to be specified instead
Additional info:
This is also applicable for pcs help
DevTestResults:
[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.13-1.el8.x86_64
[root@r8-node-01 ~]# pcs resource meta |& sed -n "/Example/,$ p"
Example:
pcs resource meta TestResource failure-timeout=50 resource-stickiness=
[root@r8-node-01 ~]# MANWIDTH=80 man pcs | grep "meta <resource" -A 10
meta <resource id | group id | clone id> <meta options> [--wait[=n]]
Add specified options to the specified resource, group or clone.
Meta options should be in the format of name=value, options may
be removed by setting an option without a value. If --wait is
specified, pcs will wait up to 'n' seconds for the changes to
take effect and then return 0 if the changes have been processed
or 1 otherwise. If 'n' is not specified it defaults to 60 min‐
utes.
Example: pcs resource meta TestResource failure-timeout=50
resource-stickiness=
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 (Moderate: pcs security, 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/RHSA-2022:7447
Description of problem: man pcs shows 'stickiness' option in the example of usage for 'pcs resource meta': meta <resource id | group id | clone id> <meta options> [--wait[=n]] Add specified options to the specified resource, group or clone. Meta options should be in the format of name=value, options may be removed by setting an option without a value. If --wait is specified, pcs will wait up to 'n' seconds for the changes to take effect and then return 0 if the changes have been processed or 1 otherwise. If 'n' is not specified it defaults to 60 minutes. Example: pcs resource meta TestResource failure-timeout=50 stickiness= Expected result: To achieve the correct functionality, 'resource-stickiness' meta option needs to be specified instead Additional info: This is also applicable for pcs help