After failed 'demote' operation the resource start is delayed until next `cluster-recheck-interval`

Solution Unverified - Updated -

Issue

  • When the demote operation of a cluster resource fails, pacemaker doesn't start back the resource immediately. Instead, it waits for some action to happen in the cluster (like creation/update/delete of resource) or up to cluster-recheck-interval to start the resource again.
  • crm_simulate -LR output shows that the resource which failed the 'demote' operation should be started, but nothing is happening.

Environment

  • Red Hat Enterprise Linux 7 with High-Availability or Resilient Storage Add-on
  • pacemaker-1.1.16-12.el7_4.4

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