[Bug 1673579] Re: Corosync/Pacemaker: Error when enabling Pacemaker service, Error when starting the cluster
Ubuntu Foundations Team Bug Bot
1673579 at bugs.launchpad.net
Tue Mar 21 16:28:47 UTC 2017
The attachment "pcs_0.9.149-1ubuntu2.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1673579
Title:
Corosync/Pacemaker: Error when enabling Pacemaker service,Error when
starting the cluster
Status in pcs package in Ubuntu:
New
Bug description:
[Impact]
* Low, requires users to change the config pcs just generated for them because the logging paths aren't correct on Debian/Ubuntu.
* While easy to workaround it its broken by default.
[Test Case]
Install Pacemaker packages:
sudo apt-get install pcs
Set the password for the default user:
sudo passwd hacluster
#To clear files
sudo pcs cluster destroy
Enable and start pcsd/pacemaker:
#this is not needed on yakkety/zesty, why?
sudo systemctl start pcsd
sudo pcs cluster auth pacemaker-1 pacemaker-2 -u hacluster -p
haclusterpassword
#this is not needed on yakkety/zesty, why?
sudo systemctl enable pacemaker
sudo pcs cluster setup --name hacluster pacemaker-1 pacemaker-2
sudo pcs cluster start
**FAILS***
Starting Cluster...
Job for corosync.service failed because the control process exited with error code. See "systemctl status corosync.service" and "journalctl -xe" for details.
Error: unable to start corosync
(Then to actually bring the cluster up you need to sudo systemctl
start pacemaker)
__
Workaround
On both nodes, Replace the line:
logfile: /var/log/cluster/corosync.log
with
logfile: /var/log/corosync/corosync.log
[Regression Potential]
* Seems unlikely this changes is only in the setup cluster function. This exact same fix is now in the Debian package, we just make the logging directory the right one.
* The only potential I see is if someone has scripted creating a cluster using pcs and worked around this bug by making the corosync directory instead of changing the config file.
[Other Info]
* This is already fixed in 16.10 and 17.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1673579/+subscriptions
More information about the Ubuntu-sponsors
mailing list