no cluster across different subnet as Address is not in the IP whitelist
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL InnoDB Cluster Charm |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hi,
I'm doing some test of this charm on a dns-ha environment,
any of the units are placed on it's own network, as we can
see in the juju status:
$ juju status mysql
Model Controller Cloud/Region Version SLA Timestamp
openstack foundations-maas maas_cloud/default 2.7.7 unsupported 09:13:07Z
App Version Status Scale Charm Store Rev OS Notes
mysql 8.0.20 waiting 3 mysql-innodb-
Unit Workload Agent Machine Public address Ports Message
mysql/0* waiting executing 2/lxd/2 10.10.103.37 Not all instances clustered
mysql/1 waiting executing 3/lxd/3 10.10.101.47 Instance not yet in the cluster
mysql/2 waiting executing 4/lxd/2 10.10.102.41 Instance not yet in the cluster
Machine State DNS Inst id Series AZ Message
2 started 10.10.0.13 os-ha-3 focal zone-3 Deployed
2/lxd/2 started 10.10.103.37 juju-91c247-2-lxd-2 focal zone-3 Container started
3 started 10.10.0.17 os-ha-7 focal default Deployed
3/lxd/3 started 10.10.101.47 juju-91c247-3-lxd-3 focal default Container started
4 started 10.10.0.15 os-ha-5 focal zone-2 Deployed
4/lxd/2 started 10.10.102.41 juju-91c247-4-lxd-2 focal zone-2 Container started
Even when the networks are in the same space(internal-
10.10.111.
will be refused by the cluster leader as we can see in its
err.log:
2020-07-
2020-07-
2020-07-
From the secondary nodes, it's possible to read the following:
2020-07-
2020-07-
2020-07-
Thanks!
José.
Hi Jose
Please can you attach your bundle including any network space bindings to this bug report.