The pcs resource move command fails for a promotable clone unless "--master" is specified

Solution In Progress - Updated -

Issue

  • It is no longer possible to move or ban an entire promotable clone resource in one step. I must now move only the master role of the clone.
  • It's impossible to fail over an SAPHana resource manually according to the Automated SAP HANA System Replication in Scale-Up in pacemaker cluster article.
  • The pcs resource move command fails for a promotable clone resource with the error below:

    [root@fastvm-rhel-8-0-23 pacemaker]# pcs resource move dummy-clone
    Error: to move promotable clone resources you must use --master and the promotable clone id (dummy-clone)
    
  • The pcs resource move <this_resource>-clone --master command in RHEL 8 doesn't behave the same way as the old pcs resource move <this_resource>-master command in RHEL 7.

Environment

  • Red Hat Enterprise Linux 8 (with the High Availability Add-on)

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