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 Apr 17 22:55:34 2020 * Last change: Fri Apr 17 22:55:22 2020 by hacluster via crmd on node1 * 1 node configured * 0 resource instances configured Node List: * Online: [ node1 ] Active Resources: * No active resources pacemaker PASS pacemaker PASS So, for some reason, this localhost corosync installation made the service to be unavailable in your cause. I wonder if you have more logs so we can check what happened for it not to be online. -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1874719 Title: Focal deploy creates a 'node1' node Status in OpenStack hacluster charm: New Status in pacemaker package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1874719/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
