[Bug 1874719] Re: Focal/Groovy deploy creates a 'node1' node
** 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 Hirsute) Importance: Undecided Status: New ** Also affects: pacemaker (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu Focal) Status: New => Invalid ** Changed in: pacemaker (Ubuntu Hirsute) Status: New => Invalid ** Changed in: pacemaker (Ubuntu Groovy) Status: New => Invalid ** Changed in: corosync (Ubuntu Focal) Status: New => Triaged ** Changed in: corosync (Ubuntu Groovy) Status: New => Triaged ** Changed in: corosync (Ubuntu Hirsute) Status: New => Triaged ** Changed in: pacemaker (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: corosync (Ubuntu) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: corosync (Ubuntu Focal) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: corosync (Ubuntu Groovy) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: corosync (Ubuntu Hirsute) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Summary changed: - Focal/Groovy deploy creates a 'node1' node + [SRU] Use the hostname as the node name instead of hardcoded 'node1' -- 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: [SRU] Use the hostname as the node name instead of hardcoded 'node1' 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
[Bug 1874719] Re: Focal/Groovy deploy creates a 'node1' node
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 this as a SRU. -- 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: [SRU] Use the hostname as the node name instead of hardcoded 'node1' 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
[Bug 1874719] Re: Focal/Groovy deploy creates a 'node1' node
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 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
[Bug 1874719] Re: Focal/Groovy deploy creates a 'node1' node
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 Bionic) and version 3.0.3 (present in Focal) the 'nodelist' directive became required (as you can see in the commit message above). The decision was to configure a single node called 'node1' with 127.0.0.1 as the IP address link. This is not done in Bionic. To fix this and keep the old behavior (use the hostname instead of a hardcoded 'node1') we simply need to comment out the "name: node1" line in /etc/corosync/corosync.conf. I did the following in a Focal VM to test it: $ sudo apt-get install -y crmsh pacemaker $ sudo crm status Cluster Summary: * Stack: corosync * Current DC: node1 (version 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Thu Jun 10 11:23:33 2021 * Last change: Thu Jun 10 11:05:11 2021 by hacluster via crmd on node1 * 1 node configured * 0 resource instances configured Node List: * Online: [ node1 ] Full List of Resources: * No resources $ sudo sed -e '/name: node1/s/^/#/' -i /etc/corosync/corosync.conf $ sudo systemctl restart corosync $ sudo systemctl restart pacemaker $ $ sudo crm status Cluster Summary: * Stack: corosync * Current DC: focal (version 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Thu Jun 10 11:51:08 2021 * Last change: Thu Jun 10 11:36:45 2021 by hacluster via crmd on focal * 1 node configured * 0 resource instances configured Node List: * Online: [ focal ] Full List of Resources: * No resources In this case my hostname is 'focal', so I believe this will keep the old behavior. Do you believe this worth a SRU? Would you like me to work on this? ** Also affects: corosync (Ubuntu) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu) Status: New => Invalid ** Changed in: corosync (Ubuntu) Status: New => Triaged -- 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
[Bug 1874719] Re: Focal/Groovy deploy creates a 'node1' node
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, which was the old behaviour and makes way more sense? -- 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
[Bug 1874719] Re: Focal/Groovy deploy creates a 'node1' node
** 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 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
[Bug 1874719] Re: Focal/Groovy deploy creates a 'node1' node
** 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: 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
[Bug 1874719] Re: Focal/Groovy deploy creates a 'node1' node
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 in: charm-hacluster Importance: Medium => High -- 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
[Bug 1874719] Re: Focal/Groovy deploy creates a 'node1' node
** 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: 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
[Bug 1874719] 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 ** 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
