Red Hat Bugzilla – Bug 454239
fence_ilo can not reboot HP server with RIBCL v2.22 (ILO2)
Last modified: 2013-07-28 20:44:41 EDT
Description of problem:
After update the servers' bios( iLO2 with RIBCL v2.22 ), fence_ilo will met
following messages when trying to reboot hp server.
# fence_ilo -a 192.168.100.1 -l Administrator -p password -o reboot
Can't use an undefined value as a HASH reference at
/usr/lib64/perl/vendor_perl/5.8.8/x86_64-linux-thread-multi/Net/SSL.pm line 128,
<> line 4.
We find a way can work around this issue:
Adding sleep(3) into line 633 and line 635 before taking action power_on &
620 elsif (/reboot/)
622 fail "power_status: unexpected error\n" if power_status;
624 if (! /^off$/i)
626 fail "power_off: unexpected error\n" if power_off;
627 fail "power_status: unexpected error\n" if power_status;
628 fail "failed to turn off\n" unless (/^off$/i);
631 if (/^off$/i)
633 sleep(3); <<<<<<= add a sleep here
634 fail "power_on: unexpected error\n" if power_on;
635 sleep(3); <<<<<<= add a sleep here
636 fail "power_status: unexpected error\n" if power_status;
637 fail "failed to turn on\n" unless (/^on$/i);
641 fail "unexpected power state: '$_'\n";
Version-Release number of selected component (if applicable):
[root@localhost ~]# rpm -q cman
Steps to Reproduce:
1. Update HP server's bios to latest version. make sure it has iLO2 with RIBCL
v2.22. setting up ip/login/password for ilo2.
2. On a client server, try to reboot it use fence_ilo
met error when using reboot action with fence_ilo.
fence_ilo can work well before updating server's bios.
Created attachment 311131 [details]
Is this version 1.50 of the firmware?
Fix available, raising exception to include in rc compose as this generates lots of customer calls.
This bug is already fixed in new fence agent (shipped in 5.3). New fence agent was tested also on these configurations:
iLO / firmware 1.91 / RIBCL 2.22
iLO2 / firmware 1.22 / RIBCL 2.22
iLO2 / firmware 1.50 / RIBCL 2.22
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.