Customer is going to retry using different APC firmware versions. At least v3.3.3 and v2.7.4 will be attempted.
Customer reports that downgrading the firmware to 2.7.4 makes the bug disappear. They accepted this as a workaround. I'll lower the priority to medium. For the record, they tested firmware 3.3.3 first and confirmed that the bug occurs there. They also tried to modify /sbin/fence_apc to accept "Outlet Management" instead of "Outlet Control" but didn't succeed. The customer also reports that their APC switch was manufactured in January 2007 and it was bought just a few weeks ago. This apparently means that if you buy an APC switch off the shelf today, you will encounter this bug.
Created attachment 156486 [details] Patches fence_apc 2.0.64 to support APC firmware 3.3.3 Apply with: cd /sbin patch -p0 < fence_apc.patch Note this patch does not change the version number and has not been tested with previous APC firmware releases.
Comment on attachment 156486 [details] Patches fence_apc 2.0.64 to support APC firmware 3.3.3 Confirmed in Firmware 3.3.3 and later (released January 5th 2007) on an APC7960 Switched Rack PDU by running: /sbin/fence_apc -a IPADDRESS -l LOGINNAME -p PASSWORD -o off -n 1:1 Which returns: failed: unrecognised menu response We fixed it by creating the attached patch (patch -p0 < patchfile), which also permits renaming outlets on the APC (which otherwise would break fence_apc). After applying the patch, the above command should return: success: outlet 1 off
This issue is of PARAMOUNT importance. My committed fix has been tested on old firmware versions as well as the latest from APCC. An incomplete fix for this issue made it into the beta - the currently committed fix is the real deal and I have complete confidence in it.
Created attachment 158961 [details] latest tested fix BTW, thx for the patch, but that patch fixes the old perl version of the agent. The latest version is in python, and includes support for alias'd names, outlet grouping, big switches, etc. Please try this attached agent - it uses the same CLI and xml attr's as the perl agent of course
Checked in. Thx for the acks, all.
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/RHBA-2007-0575.html