rgmanager leaves a service in a Stopped state even when a node is available after node reboots when using exclusive=1 and an ordered failoverdomain in a RHEL 6 High Availability cluster

Solution Unverified - Updated -

Issue

  • We reboot our nodes in a rolling fashion and the services move around. After one of these reboots, we are always left with one of our services being in a Stopped state, and rgmanager doesn't make any attempt to start it.

  • exclusive service not getting started on a free node if its primary node is hosting another service.

  • Service is left in a Stopped state by rgmanager if its preferred node has an exclusive service on it, even if another node is available.

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
  • rgmanager
  • One or more services marked with exclusive=1 residing in a failoverdomain with nofailback=1 and ordered=1

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