Comment 4 for bug 1874719

Revision history for this message
Aurelien Lourot (aurelien-lourot) wrote : Re: Focal/Groovy deploy creates a 'node1' node

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