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
** Changed in: pacemaker (Ubuntu)
Status: New => Invalid
--
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 deploy creates a 'node1' node
To manage notifications about this b
HAving looked into it further it seems to be the name of the node that
has changed.
juju deploy cs:bionic/ubuntu bionic-ubuntu
juju deploy cs:focal/ubuntu focal-ubuntu
juju run --unit bionic-ubuntu/0 "sudo apt install --yes crmsh pacemaker"
juju run --unit focal-ubuntu/0 "sudo apt install --yes c
Here you will find the autopkgtests for pacemaker:
http://autopkgtest.ubuntu.com/packages/p/pacemaker/focal/amd64
the installation ends with a corosync node online:
Cluster Summary:
* Stack: corosync
* Current DC: node1 (version 2.0.3-4b1f869f0f) - partition with quorum
* Last updated: Fri
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
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 deploy creates a 'node1' node
