Red Hat Bugzilla – Bug 860130
check power status at the end of each power command
Last modified: 2018-02-05 19:41:31 EST
Most fence commands support checking the power status of the system. As an extra sanity check, we could update the power scripts to do this after issuing a power command and bail out if the state is not what we are expecting.
+++ This bug was initially created as a clone of Bug #859400 +++
Description of problem:
The reboot command in beaker-provision has no delay between the off and on operation which causes some systems to hang. Worse yet, it is not very nice to hardware and could damage it.
--- Additional comment from firstname.lastname@example.org on 2012-09-24 18:22:33 EST ---
Can i suggest run status command after power command just to be sure that everything is working as expected.
It turns out waiting for the reported power status to change is already built in to the fence scripts (see /usr/share/fence/fencing.py), so it will only make sense to do this for the ipmitool and virsh power scripts.
This is similar to the "don't issue the command if we're already in the correct state" checks, which are implicit in all fence scripts, but need to be handled explicitly for virsh and ipmitool.
I ended up just modifying ipmitool for now.
This has now been released