I have seen this issue while working on https://review.opendev.org/741592 (adding an action for cleaning up the corosync ring). When adding a unit, sometimes pacemaker names it node1, but then renames it 2.5 minutes later with the correct name. However a function wait_for_pcmk() in the charm timed out after only 2 minutes waiting for the node to show up with the proper name. This then led to the charm taking further actions too early.
I believe the review I've just mentioned will fix this.
I have seen this issue while working on https:/ /review. opendev. org/741592 (adding an action for cleaning up the corosync ring). When adding a unit, sometimes pacemaker names it node1, but then renames it 2.5 minutes later with the correct name. However a function wait_for_pcmk() in the charm timed out after only 2 minutes waiting for the node to show up with the proper name. This then led to the charm taking further actions too early.
I believe the review I've just mentioned will fix this.