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.
DescriptionJan Pokorný [poki]
2010-08-11 18:23:37 UTC
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
fence-agents-3.0.12-7.el6.x86_64
How reproducible:
Always.
Steps to Reproduce (this is only an example how to demonstrate it; there can be more similar cases):
1. # man fence_sanbox2
(...)
-o, --action=<action>
Fencing Action (Default Value: disable)
(...)
ACTIONS
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.
monitor
Check if fencing device is running. List available plugs/virtual machines or get status of machine (if it does not support more).
metadata
The operational behavior of this is not known.
(...)
2. # fence_sanbox2 -o on
Failed: Unrecognised action 'on'
Please use '-h' for usage
Actual results:
Bad information about possible actions provided by man page.
Expected results:
The information is correct.
Additional info:
Note that -h flag informs correctly:
(...)
-o, --action=<action> Action: status, enable or disable
(...)
Comment 2RHEL Program Management
2010-08-11 18:58:40 UTC
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.)
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.
http://rhn.redhat.com/errata/RHBA-2011-0745.html
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 fence-agents-3.0.12-7.el6.x86_64 How reproducible: Always. Steps to Reproduce (this is only an example how to demonstrate it; there can be more similar cases): 1. # man fence_sanbox2 (...) -o, --action=<action> Fencing Action (Default Value: disable) (...) ACTIONS 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. monitor Check if fencing device is running. List available plugs/virtual machines or get status of machine (if it does not support more). metadata The operational behavior of this is not known. (...) 2. # fence_sanbox2 -o on Failed: Unrecognised action 'on' Please use '-h' for usage Actual results: Bad information about possible actions provided by man page. Expected results: The information is correct. Additional info: Note that -h flag informs correctly: (...) -o, --action=<action> Action: status, enable or disable (...)