My analysis was wrong and increasing the timeout [0] didn't help. The charm recovers eventually and running that new `update-ring` action [0] will be a valid workaround for removing `node1` from the corosync ring later on. I'll add an inline comment in the code and work around it in the functional tests.
So this isn't fixed but has a workaround and this seems to be happening a lot on zosci on groovy-victoria at the moment. [0] https://review.opendev.org/741592 [1] https://github.com/openstack-charmers/zaza-openstack-tests/pull/369 ** Summary changed: - Focal deploy creates a 'node1' node + Focal/Groovy deploy creates a 'node1' node ** Changed in: charm-hacluster Status: In Progress => Triaged ** Changed in: charm-hacluster Assignee: Aurelien Lourot (aurelien-lourot) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874719 Title: Focal/Groovy deploy creates a 'node1' node To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1874719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
