Placing a node in unstandby fails when automating a Pacemaker rolling update procedure using an Ansible Playbook

Solution Verified - Updated -

Issue

Automating the task 'pcs node unstandby' fails when using an Ansible Playbook for a rolling update

Environment

  • Red Hat Enterprise Linux 8
  • Ansible 2.9
  • pcs-0.10.6-4.el8.x86_64
  • 5 node cluster

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