Comment 1 for bug 1973761

Can you include the version of Juju that you are running and the bundle that you are trying to deploy?
It would also be helpful to include any logs associated with the failures. I do see:
neutron-mysql-router/0* blocked idle 192.168.15.45 Failed to connect to MySQL

But that doesn't include enough information to understand why it is failing to connect to MySQL.

It does appear that MySQL is available:
mysql-innodb-cluster/0 active idle 0/lxd/3 192.168.15.48 Unit is ready: Mode: R/O, Cluster is ONLINE and can tolerate up to ONE failure.
mysql-innodb-cluster/1 active idle 1/lxd/2 192.168.15.43 Unit is ready: Mode: R/O, Cluster is ONLINE and can tolerate up to ONE failure.
mysql-innodb-cluster/2* active idle 2/lxd/2 192.168.15.60 Unit is ready: Mode: R/W, Cluster is ONLINE and can tolerate up to ONE failure.

There is nothing that indicates this is a bug in Juju (vs a bug in the charm, vs configuration, etc).
Though if it is something that "it worked yesterday with Juju 2.9.25 and fails today with 2.9.27" that could be something that we changed.