Comment 11 for bug 1894323

Everything is good and ready but I have discovered a small issue in the Bionic Backport... and relates to:

https://access.redhat.com/solutions/4642491

The story is this: when declaring the fence_aws primitive, you can either declare it as a single resource and describe the pcmk_host_map... OR you can declare one fence resource PER NODE doing the exact same thing BUT using the "plug/port" resource argument. The thing is... in Focal, both methods work but in Bionic, the second method does not work. It is not a big deal as there are some fence agents designed to work with "pcmk_host_map" only, and some others are designed to work with "plug/port" argument... but I have opened the bug:

https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1900374

to deal with this in a later moment (might require pacemaker bisecting, etc)

For this SRU.. after it is complete, the correct way of declaring the fence_aws resource is:

# focal

node 1: focal01
node 2: focal02
node 3: focal03

primitive fence-focal stonith:fence_aws \
 params access_key=xxxxxxxx secret_key="xxxxxxxx" region=us-east-1 pcmk_host_map="focal01:i-abcdefgh;focal02:i-ijlmnop;focal03:i-qrstuvxz"

property cib-bootstrap-options: \
 have-watchdog=false \
 dc-version=2.0.3-4b1f869f0f \
 cluster-infrastructure=corosync \
 stonith-enabled=on \
 stonith-action=reboot \
 no-quorum-policy=stop \
 cluster-name=focal

# bionic

node 1: bionic01
node 2: bionic02
node 3: bionic03

primitive fence-bionic stonith:fence_aws \
 params access_key=xxxxxxxx secret_key="xxxxxxxx" region=us-east-1 pcmk_host_map="bionic01:i-abcdefgh;bionic02:i-ijlmnop;bionic03:i-qrstuvxz"

property cib-bootstrap-options: \
    have-watchdog=false \
    dc-version=1.1.18-2b07d5c5a9 \
    cluster-infrastructure=corosync \
    stonith-enabled=on \
    stonith-action=reboot \
    no-quorum-policy=stop \
    cluster-name=bionic