** Description changed: + [Impact] + + Users upgrading from Bionic to Focal are getting a different default + node name, previously it was the hostname and now it is using a + hardcoded "node1". This issue was already fixed on Impish onward, so now + only Focal is using the hardcoded "node1" node name. + + [Test Plan] + + $ lxc launch ubuntu-daily:focal corosync-sru + $ lxc shell corosync-sru + # apt update && apt upgrade -y + # apt install -y corosync pacemaker crmsh + # crm status + Cluster Summary: + * Stack: corosync + * Current DC: corosync-sru (version 2.0.3-4b1f869f0f) - partition with quorum + * Last updated: Tue Apr 5 20:21:32 2022 + * Last change: Tue Apr 5 20:20:33 2022 by hacluster via crmd on corosync-sru + * 1 node configured + * 0 resource instances configured + + Node List: + * Online: [ corosync-sru ] + + Full List of Resources: + * No resources + + In the 'Node List' section the node should be called 'corosync-sru' and + not 'node1'. + + [Where problems could occur] + + This might be a problem if Focal users are already relying in the + 'node1' node name, other than that I do not foresee any issue. + + [Original Message] + Testing of masakari on focal zaza tests failed because the test checks that all pacemaker nodes are online. This check failed due the appearance of a new node called 'node1' which was marked as offline. I don't know where that node came from or what is supposed to represent but it seems like an unwanted change in behaviour.
-- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
