Description of problem: luci web app does not enforce selection of fence port - if the user omits the fence port, this error is raised when an attempt is made to fence the node: Jan 31 08:45:01 tng3-3 fence_node[6530]: agent "fence_apc" reports: failed: no plug number Jan 31 08:45:01 tng3-3 fence_node[6530]: Fence of "tng3-1.lab.msp.redhat.com" was unsuccessful Version-Release number of selected component (if applicable): luci-0.8-30.el5 How reproducible: 100% Steps to Reproduce: 1. Create a fence definition w/o the port # for the cluster node - see the screenshot attachment. 2. Attempt to fence the node Actual results: The error listed above is written to /var/log/messages Expected results: The luci GUI should require the user to specify the fence port #. Additional info:
Created attachment 147026 [details] Screenshot
This is already fixed in HEAD (and for RHEL 4.5).
Fixing Product Name. Cluster Suite was merged into Enterprise Linux for version 5.0.
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 the 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/RHSA-2007-0640.html