Looks like the units are attempting to connect to the 'old' mysql host, rather than mysql-router, until Vault is restarted. Restarting the first unit resulted in that error, but when the second unit was restarted, the cluster re-formed and hooks started to run again.
Looks like the units are attempting to connect to the 'old' mysql host, rather than mysql-router, until Vault is restarted. Restarting the first unit resulted in that error, but when the second unit was restarted, the cluster re-formed and hooks started to run again.
This is, therefore an issue that: /docs.openstack .org/project- deploy- guide/charm- deployment- guide/latest/ percona- series- upgrade- to-focal. html with some notes on how to properly restart.
- Vault needs to be restarted after changing the db relation, but is not (and, naturally, needs unsealing).
- the error message supplied by the charm doesn't actually tell us that
- vault needs to be added to the guide at https:/