I did totally remove that value. It still fails.

No just a single host. I didn't see any documentation that said you need two or more hosts. You could be right. I did some further testing by installing ipmitool on my laptop. [root@lt ~]# ipmitool -v -I lanplus -H 172.30.50.2 -U ADMIN session info all Password: session handle : 0 slot count : 16 active sessions : 1 user id : 2 privilege level : ADMINISTRATOR session type : IPMIv2/RMCP+ channel number : 0x01 Maybe a one of the DEVs could chime in and confirm if this is expected behavior?

I believe without the inclusion of a developer on this thread it makes sense not to work with a single host because if you're trying to test fencing (via the power management setup) then how the host will fence itself and validate it. This of course when testing with a single host. I believe the option is labeled incorrectly on ovirt because it should not be called power management if you're performing fencing with it. there should be a an explicit button or setup option for fencing and another one for power management things. this leads to confusing terms and this is one of the features that sometimes keep people from testing systems like ovirt and sticking with hyper-v or VMware where options are clearly described. once again it makes no sense to me to test fencing with a single host on my environment. that's why I believe developers failed to document the fact that you need at least two host to test fencing. I could be totally wrong but as I learn ovirt here I have never ever been able to test fencing with a single host, always with two or more hosts previously configured. On Sun, Oct 20, 2019, 3:26 PM <jeremy_tourville(a)hotmail.com&gt; wrote:

LOL, yes That's just about right. I'd say I agree with you. The language used in the error output wasn't real clear to me either. I'll have to add something in the docs that say: ***WARNING/*** Fencing will not work on a single host. You must have at least 2 hosts in the cluster for fencing to work properly.