[hirsute] update-ring action fails on removing unreachable nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack HA Cluster Charm |
Fix Released
|
High
|
Aurelien Lourot |
Bug Description
Seen twice on hirsute in our test gate [0][1]
## Running Test zaza.openstack.
looking at application: {'name': 'keystone', 'type': {'pkg': 'keystone', 'origin_setting': 'openstack-
Using keystone API V3 (or later) for overcloud auth
looking at application: {'name': 'keystone', 'type': {'pkg': 'keystone', 'origin_setting': 'openstack-
test_930_scaleback (zaza.openstack
Remove one unit, recalculate quorum and re-add one unit.
...
Pausing unit keystone-
Removing keystone/1
Waiting for model to settle
Checking that corosync considers at least one node to be offline
Updating corosync ring
ERROR
=======
ERROR: test_930_scaleback (zaza.openstack
Remove one unit, recalculate quorum and re-add one unit.
-------
Traceback (most recent call last):
File "/home/
raise_
File "/home/
return run(_run_it())
File "/home/
return task.result()
File "/home/
return await f(*args, **kwargs)
File "/home/
raise ActionFailed(
zaza.model.
Note that `node1` is wrongly created by pacemaker because of another bug [2] and the update-ring action is supposed to successfully work around that by removing `node1`.
[0] https:/
[1] https:/
[2] lp:1874719
Changed in charm-hacluster: | |
assignee: | nobody → Aurelien Lourot (aurelien-lourot) |
Changed in charm-hacluster: | |
status: | New → In Progress |
importance: | Undecided → High |
Changed in charm-hacluster: | |
milestone: | none → 21.10 |
Changed in charm-hacluster: | |
status: | Fix Committed → Fix Released |
Issue also visible in this gate: /review. opendev. org/c/openstack /charm- hacluster/ +/794501
https:/