Hide Forgot
Description of problem: Luci sets a wrong value into 'secure' parameter, inside <fencedevice> section. The correct value to be set is "secure=1" and Luci set "secure=On" instead. If you change this value within a text editor, the fence works without problems into iDrac6. This parameter has to be set to use the iDrac6 with SSH. Version-Release number of selected component (if applicable): luci-0.22.2-14.el6_0.1.x86_64 How reproducible: Install luci and config your fence_device to use the iDrac6 through the web interface. Steps to Reproduce: 1. Install luci-0.22.2-14.el6_0.1.x86_64 2. Access the Luci web address 3. Configure the fence_device within iDrac6. Actual results: The parameter 'secure' into <fencedevice> has the value 'On'. secure=On Expected results: The parameter 'secure' into <fencedevice> has the value '1'. secure=1 Additional info: If the fence script is executed, it works without problem: fence_drac5 -c admin1 -a 192.168.0.13 -l user -m 1 -p pAssWOrd1 -x but if the fence_node command is issued, then the error occurs: fence_node -vv node1 fence node1 dev 0.0 agent fence_drac5 result: error from agent agent args: nodename=node1 agent=fence_drac5 cmd_prompt=admin1 ipaddr=192.168.0.13 login=user module_name=1 passwd=pAssWOrd1 secure=on fence node1 failed System Information Red Hat Enterprise Linux Server release 6.0 (Santiago) kernel-2.6.32-71.14.1.el6.x86_64 #1 SMP Manufacturer: Dell Inc. Product Name: PowerEdge R710
Created attachment 481446 [details] Fence-agents fix This can also be fixed or worked around in the fence-agents package, as demonstrated by this patch. I have tested this patch on my WTI VMR (with its telnet access shut off). Without this patch, it fails if you supply "secure=on" or "secure=true".
verified in fence-agents-3.0.12-23.el6 fence_node -vv <nodename> with secure="on" or secure="true" in cluster.conf executes successfully. luci writes cluster.conf to contain secure="on" as a parameter to <fencedevice/>
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