Comment 1 for bug 2015774

So the 'reason' it didn't cluster is due to the leader not being able to contact the followers:

023-04-08 13:41:49 INFO unit.mysql-innodb-cluster/1.juju-log server.go:316 Invoking reactive handler: reactive/mysql_innodb_cluster_handlers.py:138:check_quorum
2023-04-08 13:41:49 DEBUG unit.mysql-innodb-cluster/1.juju-log server.go:316 Found peers: 192.168.33.214,192.168.33.219
2023-04-08 13:41:49 DEBUG unit.mysql-innodb-cluster/1.juju-log server.go:316 Expect 2 peers
2023-04-08 13:41:49 DEBUG unit.mysql-innodb-cluster/1.juju-log server.go:316 Reached quorum
2023-04-08 13:41:49 INFO unit.mysql-innodb-cluster/1.juju-log server.go:316 Invoking reactive handler: reactive/mysql_innodb_cluster_handlers.py:172:configure_instances_for_clustering
2023-04-08 13:41:49 DEBUG unit.mysql-innodb-cluster/1.juju-log server.go:316 Configuring instances for clustering.
2023-04-08 13:41:49 INFO unit.mysql-innodb-cluster/1.juju-log server.go:316 Configuring instance for clustering: 192.168.33.214.
2023-04-08 13:41:55 ERROR unit.mysql-innodb-cluster/1.juju-log server.go:316 Failed configuring instance 192.168.33.214: Cannot set LC_ALL to locale en_US.UTF-8: No such file or directory
Traceback (most recent call last):
  File "<string>", line 1, in <module>
mysqlsh.DBError: MySQL Error (2003): Dba.configure_instance: Can't connect to MySQL server on '192.168.33.214' (113)

2023-04-08 13:41:55 DEBUG unit.mysql-innodb-cluster/1.juju-log server.go:316 Checking cluster status.
2023-04-08 13:41:56 INFO unit.mysql-innodb-cluster/1.juju-log server.go:316 Adding instance, 192.168.33.214, to the cluster.
2023-04-08 13:41:58 ERROR unit.mysql-innodb-cluster/1.juju-log server.go:316 Failed adding instance 192.168.33.214 to cluster: Cannot set LC_ALL to locale en_US.UTF-8: No such file or directory
ESC[31mERROR: ESC[0mUnable to connect to the target instance '192.168.33.214:3306'. Please verify the connection settings, make sure the instance is available and try again.
Traceback (most recent call last):
  File "<string>", line 3, in <module>
mysqlsh.DBError: MySQL Error (2003): Cluster.add_instance: Could not open connection to '192.168.33.214:3306': Can't connect to MySQL server on '192.168.33.214' (113)

2023-04-08 13:41:58 INFO unit.mysql-innodb-cluster/1.juju-log server.go:316 Configuring instance for clustering: 192.168.33.219.
2023-04-08 13:42:01 ERROR unit.mysql-innodb-cluster/1.juju-log server.go:316 Failed configuring instance 192.168.33.219: Cannot set LC_ALL to locale en_US.UTF-8: No such file or directory
Traceback (most recent call last):
  File "<string>", line 1, in <module>
mysqlsh.DBError: MySQL Error (2003): Dba.configure_instance: Can't connect to MySQL server on '192.168.33.219' (113)

2023-04-08 13:42:01 DEBUG unit.mysql-innodb-cluster/1.juju-log server.go:316 Checking cluster status.
2023-04-08 13:42:02 INFO unit.mysql-innodb-cluster/1.juju-log server.go:316 Adding instance, 192.168.33.219, to the cluster.
2023-04-08 13:42:04 ERROR unit.mysql-innodb-cluster/1.juju-log server.go:316 Failed adding instance 192.168.33.219 to cluster: Cannot set LC_ALL to locale en_US.UTF-8: No such file or directory
ESC[31mERROR: ESC[0mUnable to connect to the target instance '192.168.33.219:3306'. Please verify the connection settings, make sure the instance is available and try again.
Traceback (most recent call last):
  File "<string>", line 3, in <module>
mysqlsh.DBError: MySQL Error (2003): Cluster.add_instance: Could not open connection to '192.168.33.219:3306': Can't connect to MySQL server on '192.168.33.219' (113)

It's not obvious from any of the logs *why* the lead unit couldn't contact the other two instances.