unit missing in allowed_units when leadership changes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL InnoDB Cluster Charm |
Triaged
|
High
|
Rodrigo Barbieri |
Bug Description
Using mysql-innodb-
Steps to reproduce:
1) deploy 3 units of keystone, mysql-router and mysql-innodb-
2) If upon complete deployment the mysql-innodb-
a) check data using:
juju show-unit keystone-
b) clear data using:
juju run -u mysql-innodb-
3) Now, confirm that mysql-innodb-
juju show-unit keystone-
4) move mysql-innodb-
5) add a new keystone unit:
juju add-unit keystone
6) Wait for it to finish deployment and the problem is seen in juju status.
7) See that the relation-data is stale for mysql-innodb-
juju show-unit keystone-
Changed in charm-mysql-innodb-cluster: | |
assignee: | nobody → Rodrigo Barbieri (rodrigo-barbieri2010) |
Changed in charm-mysql-innodb-cluster: | |
status: | In Progress → Triaged |
importance: | Undecided → High |
according to [1] and the fact that we cannot determine a leader if we are not the unit calling is_leader, then mysql-innodb- cluster units MUST somehow agree on their relation-data.
[1] https:/ /github. com/juju- solutions/ charms. reactive/ blob/8496d04e64 97200ca8530d84e ff4a3191509ed0f /charms/ reactive/ relations. py#L817