** Also affects: pacemaker (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: pacemaker (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu
In case anyone here wants to try the proposed solution, I did upload
corosync version 3.0.3-2ubuntu2.2~ppa1 to my PPA and it indeed fixes the
issue, it uses the hostname as the node name by default now:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/ha-stack
I'll be working to release
Hi Lucas
Thanks for the commentary and feedback on why this change was
introduced.
I feel this is worth looking at via the SRU process and yes please if
you have cycles that would be great!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is a change in the default corosync config file
(/etc/corosync/corosync.conf), it impacts pacemaker clusters but it is
not directly related to pacemaker. The change was made in Debian here:
https://salsa.debian.org/ha-team/corosync/-/commit/2f8aa88
Between corosync version 2.4.3 (present in
Setting the pacemaker distro task back to new - it seems very odd that a
system designed to manage a cluster of servers would install on every
node with a non-unique node id, which is a change in behaviour from
older versions of the same software.
Can we not sanity fix this to use the hostname,
** Changed in: pacemaker (Ubuntu)
Status: Invalid => New
--
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
** Tags added: seg
--
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:
Raising priority to "High" because this may lead to corosync/pacemaker
thinking there are 4 nodes instead of 3 on a fresh deployment, and then
we think we have an HA deployment where we are in fact not HA. Again
there is a workaround: running the `update-ring` action after
deployment.
** Changed
** Tags added: cdo-qa foundations-engine
--
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:
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
10 matches
Mail list logo
