This bug was fixed in the package pcs - 0.9.149-1ubuntu1.1
---
pcs (0.9.149-1ubuntu1.1) xenial; urgency=medium
* Patch d/p/0009-Fix-corosync-log.patch makes the generated config
use the right log directory so it doesn't fail to start
(LP: #1673579).
-- Bryan Quigley Thu, 27 Apr 2017
11:11:22 -0700
** Changed in: pcs (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
Fix Released
Status in pcs source package in Xenial:
Fix Released
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
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
