Red Hat Bugzilla – Bug 1121791
Provide documentation of batch-limit and other pacemaker properties in man page or pcs help
Last modified: 2015-11-19 04:32:30 EST
Description of problem: When onsite without access to the official Red Hat docs, there is no way to determine what the pacemaker properties are for. We should have them documented in the pcs man page, help text or pcs property output.
One note, this information is in the pengine man page. So it might make sense to just put a note to that effect in the pcs man page/usage text.
Created attachment 1022169 [details] proposed fix test: "Run 'man pengine' and 'man crmd' to get a description of the properties." in pcs help and man page.
Before Fix: [root@rh71-node1 ~]# rpm -q pcs pcs-0.9.137-13.el7_1.2.x86_64 [root@rh71-node1:~]# man pcs | grep pengine [root@rh71-node1:~]# pcs property help | grep pengine After Fix: [root@rh71-node1:~]# rpm -q pcs pcs-0.9.140-1.el6.x86_64 [root@rh71-node1:~]# man pcs | grep pengine pengine' and 'man crmd' to get a description of the properties. set on the specified node. Run 'man pengine' and 'man crmd' to get a description of the properties. Remove property from configuration (or remove attribute from specified node if --node is used). Run 'man pengine' and 'man crmd' to get a description of the properties. [root@rh71-node1:~]# pcs property help | grep pengine Run 'man pengine' and 'man crmd' to get a description of the properties. Run 'man pengine' and 'man crmd' to get a description of the properties. Run 'man pengine' and 'man crmd' to get a description of the properties.
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, 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://rhn.redhat.com/errata/RHSA-2015-2290.html