A db2 resource fails to promote when status is: INFO: DB2 database db2inst1(0)/sterdb has HADR status STANDBY/REMOTE_CATCHUP_PENDING/DISCONNECTED and will be promoted
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (resource-agents bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:3853
AWS is requesting 7.6.z and 7.7.z, as this is preventing failover of their customers' SAP deployments. I think these z-streams would be reasonable now that we know it's affecting SAP clusters.
Can we get this cloned?