Already bootstraped with name <name> use force

[David Ames]

In [0], the nova-mysql-router/1 unit attempted to bootstrap but failed in the first attempt due to a race with the cluster adding the mysqlrouter user.

Failed to bootstrap mysqlrouter: Error: Unable to connect to the metadata server: Error connecting to MySQL server at 172.17.110.20:0: Access denied for user 'mysqlrouteruser'@'172.17.110.7' (using password: YES) (1045)

Then subsequent attempts failed with:

Failed to bootstrap mysqlrouter: # Bootstrapping MySQL Router instance at '/var/lib/mysql/nova-mysql-router'...

Error: It appears that a router instance named 'nova-mysql-router' has been previously configured in this host. If that instance no longer exists, use the --force option to overwrite it.

[0] https://openstack-ci-reports.ubuntu.com/artifacts/test_charm_pipeline_func_full/openstack/charm-mysql-router/780992/1/8266/index.html

[Aurelien Lourot (aurelien-lourot)]

Fix: https://review.opendev.org/c/openstack/charm-mysql-router/+/781923

[Alex Dodson (alexdodson)]

Is there a manual workaround to resolve this? I have this with multiple units after re-adding them back to an existing model.

[Trent Lloyd (lathiat)]

You can upgrade the charm to workaround the issue even once it's stuck.

Otherwise the manual workaround is to DELETE the rows from the mysql_innodb_cluster_metadata.routers table with the IP address matching the unit that can't create the new router. Likely in that charm version the router 'name' is set to '' but if there is more than 1 router for the same IP you also need to match the name. (Fairly sure the name sending was added after the --force fix)