Compute node stopped for pacemaker 'compute-unfence-trigger' after

Solution In Progress - Updated -

Issue

After compute evacuation, compute node had symptoms of this Nova compute service is down

  • compute-unfence-trigger on compute node ppk00004-compute is in stopped status
# pcs status
...
 stonith-fence_compute-fence-nova       (stonith:fence_compute):        Started ppk00001-controller
 Clone Set: compute-unfence-trigger-clone [compute-unfence-trigger]
     Started: [ ppk00000-compute ppk00001-compute ppk00002-compute ppk00003-compute ppk00005-compute ppk00007-compute ]
     Stopped: [ ppk00004-compute ppk00006-compute ppk00000-controller ppk00001-controller ppk00002-controller ]
 nova-evacuate  (ocf::openstack:NovaEvacuate):  Started ppk00001-controller
 stonith-fence_ipmilan-98039b057e3e     (stonith:fence_ipmilan):        Started ppk00001-controller
 stonith-fence_ipmilan-98039b05719e     (stonith:fence_ipmilan):        Started ppk00002-controller
 stonith-fence_ipmilan-98039b05713e     (stonith:fence_ipmilan):        Started ppk00001-controller
 stonith-fence_ipmilan-98039b057e16     (stonith:fence_ipmilan):        Started ppk00000-controller
...

Environment

Red Hat OpenStack Platform 13

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content