Nova compute containers stays unhealthy after the compute node gets fenced

Solution Verified - Updated -

Issue

  • The nova container is waiting forfence flag to set down.

    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-trigger resources stay in FAILED state.

     compute-unfence-trigger    (ocf::pacemaker:Dummy): FAILED <COMPUTE_NAME> (blocked)
    
  • Since these resources are stuck in FAILED state, stonith cannot be enabled because it would keep rebooting these compute nodes again and again.

  • Ideally, after a reboot of compute node the compute-unfence-trigger resource should become healthy.

Environment

  • Red Hat OpenStack Platform 13.0
  • RHEL 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In