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
