Bug 2064805

Summary: man pcs suggests using 'stickiness' instead of 'resource-stickiness' in 'pcs resource meta'
Product: Red Hat Enterprise Linux 8 Reporter: Nina Hostakova <nhostako>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: low Docs Contact:
Priority: low    
Version: 8.6CC: cluster-maint, idevat, kmalyjur, mlisik, mpospisi, omular, tojeline
Target Milestone: rcKeywords: EasyFix, Triaged
Target Release: 8.7Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.10.13-1.el8 Doc Type: No Doc Update
Doc Text:
This is a self-explanatory minor documentation update
Story Points: ---
Clone Of:
: 2064818 (view as bug list) Environment:
Last Closed: 2022-11-08 09:14:00 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 Nina Hostakova 2022-03-16 15:28:39 UTC
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 4 Miroslav Lisik 2022-05-26 08:52:14 UTC
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=

Comment 14 errata-xmlrpc 2022-11-08 09:14:00 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:7447