Monitoring pacemaker resources getting timed out

Solution Verified - Updated -

Issue

  • Monitoring pacemaker cluster resources by podman getting timed out.
  • Many pacemaker cluster resources (below) are impacted randomly across cluster nodes,

    rabbitmq-bundle-podman-x
    ovn-dbs-bundle-podman-y
    haproxy-bundle-podman-z
    
  • Timed out behavior causing cluster resources to restart which brings the high impact in the environment.

Environment

  • Red Hat Openstack Platform 16.2

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