Description of problem:



Customer does not like the fact that instance ha automatically starts nova-compute after the compute node comes back up from fencing.  The reasoning is most of the failures they see are around memory going bad, so if memory goes bad and the compute comes back up without that dimm , therefore less ram the compute still isn't ready for usage. If vms start getting scheduled there again after fencing they still have to manually disable compute service and migrate vms off to fix the hardware.  We are wondering if there is a way to have the admin confirm the compute is good before allowing scheduling to continue to that node?  We tried to play with disabling compute unfence trigger since the docs say that is what unfences the node when it comes back up; that didn't work. Manually disabling the compute service doesn't seem like a good option either since the admin may not know exactly when fencing happens.