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.

Bug 2064818

Summary:	man pcs suggests using 'stickiness' instead of 'resource-stickiness' in 'pcs resource meta'
Product:	Red Hat Enterprise Linux 9	Reporter:	Tomas Jelinek <tojeline>
Component:	pcs	Assignee:	Tomas Jelinek <tojeline>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	low	Docs Contact:
Priority:	low
Version:	9.0	CC:	cluster-maint, cluster-qe, idevat, kmalyjur, mlisik, mmazoure, mpospisi, nhostako, omular, tojeline
Target Milestone:	rc	Keywords:	EasyFix, Triaged
Target Release:	9.1	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pcs-0.11.2-1.el9	Doc Type:	No Doc Update
Doc Text:	This is a self-explanatory minor documentation update	Story Points:	---
Clone Of:	2064805	Environment:
Last Closed:	2022-11-15 09:49:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomas Jelinek 2022-03-16 15:59:33 UTC

+++ This bug was initially created as a clone of Bug #2064805 +++

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

Comment 1 Tomas Jelinek 2022-03-22 07:56:43 UTC

Upstream patch: https://github.com/ClusterLabs/pcs/commit/d881674b35d646b3ffffcb047f7f81258bb4ce8c

Comment 3 Miroslav Lisik 2022-05-19 17:41:02 UTC

DevTestResults:

[root@r91-1 ~]# rpm -q pcs
pcs-0.11.2-1.el9.x86_64

[root@r91-1 ~]# pcs resource meta |& sed -n "/Example/,$ p"
        Example:
        pcs resource meta test_resource failure-timeout=50 resource-stickiness=

[root@r91-1 ~]# MANWIDTH=80 man pcs | grep "meta <stonith" -A 10
       meta <stonith id> <meta options> [1m--wait22m[=n]]
              Add  specified options to the specified stonith device. Meta op‐
              tions should be in the format of name=value, options may be  re‐
              moved  by setting an option without a value. If 1m--wait 22mis speci‐
              fied, 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 stonith meta  test_stonith  failure-timeout=50  re‐
              source-stickiness=
[root@r91-1 ~]# MANWIDTH=80 man pcs | grep "meta <resource" -A 10
       meta <resource id | group id | clone id> <meta options> [1m--wait22m[=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  1m--wait  22mis

              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  re‐
              source-stickiness=

Comment 9 errata-xmlrpc 2022-11-15 09:49:09 UTC

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:7935