Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

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

Solution Unverified - Updated 2018-11-01T15:34:35+00:00 -

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

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)