- 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
SAPHanaresource manually according to the Automated SAP HANA System Replication in Scale-Up in pacemaker cluster article.
pcs resource movecommand 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)
pcs resource move <this_resource>-clone --mastercommand in RHEL 8 doesn't behave the same way as the old
pcs resource move <this_resource>-mastercommand in RHEL 7.
- Red Hat Enterprise Linux 8 (with the High Availability Add-on)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.