Comment 21 for bug 1927981

Related to lathiat's comment - I had the same thing happen on a customer cloud. It seems that during the bootstrap of mysql-router, a [metadata_cache:bootstrap] section is created. The cluster-name of mysql-innodb-cluster was jujuCluster. We had to redeploy a vault unit, and that's when we saw this break.

When I test upgrading from cs:mysql-router-15 to ch:mysql-router --channel 8.0/stable locally, I see that the end result of the upgrade is that that the [metadata_cache:jujuCluster] section is dropped and the [metadata_cache:bootstrap] section is retained.

I don't know enough about mysql-router to know whether the destinations clauses need to be updated though. I see they still refer to jujuCluster; is that normal and expected, even with the metadata_cache section being labeled "bootstrap"?