Red Hat Bugzilla – Bug 623266
Metadata (man pages) generation does not take different sorts of action into account
Last modified: 2016-04-26 11:06:52 EDT
Description of problem:
Specifically, metadata function in fencing.py (agents/lib/fence.py.py) outputs a static block of actions without being aware of current fence.
Version-Release number of selected component (if applicable):
Tested both on current git version and updated RHEL 6.0 beta:
# rpm -q fence-agents
Steps to Reproduce (this is only an example how to demonstrate it; there can be more similar cases):
1. # man fence_sanbox2
Fencing Action (Default Value: disable)
on Power on machine.
off Power off machine.
reboot Reboot machine.
status This returns the status of the plug/virtual machine.
list List available plugs with aliases/virtual machines if there is support for more then one device. Returns N/A otherwise.
Check if fencing device is running. List available plugs/virtual machines or get status of machine (if it does not support more).
The operational behavior of this is not known.
2. # fence_sanbox2 -o on
Failed: Unrecognised action 'on'
Please use '-h' for usage
Bad information about possible actions provided by man page.
The information is correct.
Note that -h flag informs correctly:
-o, --action=<action> Action: status, enable or disable
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
We should standardize action values, I suggest on/off, and make all agents, docs, man pages, rng use and refer to on/off.
(Any agents that currently accept enable/disable need to continue accepting those values in addition to on/off.)
Fixed in upstream:
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.