Customer's deployment has units in multiple subnets so can't use L2 vip. If the MAAS API key changes, running juju config does not update the pacemaker configuration.
After running:
juju config hacluster-mysql maas_credentials='<new api key>'
Checking pacemaker shows the old key:
juju ssh hacluster-mysql/0 sudo crm configure show
Reopening this.
Customer's deployment has units in multiple subnets so can't use L2 vip. If the MAAS API key changes, running juju config does not update the pacemaker configuration.
After running:
juju config hacluster-mysql maas_credential s='<new api key>'
Checking pacemaker shows the old key:
juju ssh hacluster-mysql/0 sudo crm configure show