Nova compute containers stays unhealthy after the compute node gets fenced
Issue
-
The
nova containeris waiting forfenceflag to setdown.Waiting for fence-down flag to be cleared Waiting for fence-down flag to be cleared Waiting for fence-down flag to be cleared Waiting for fence-down flag to be cleared -
The
compute-unfence-triggerresources stay inFAILEDstate.compute-unfence-trigger (ocf::pacemaker:Dummy): FAILED <COMPUTE_NAME> (blocked) -
Since these resources are stuck in
FAILEDstate,stonithcannot be enabled because it would keep rebooting these compute nodes again and again. -
Ideally, after a reboot of compute node the
compute-unfence-triggerresource should becomehealthy.
Environment
- Red Hat OpenStack Platform 13.0
- RHEL 7.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.