| 2017-03-16 19:12:27 |
Akash Chandrashekar |
bug |
|
|
added bug |
| 2017-03-16 20:39:19 |
Bryan Quigley |
bug |
|
|
added subscriber Bryan Quigley |
| 2017-03-20 19:13:32 |
Bryan Quigley |
description |
16.04.2 LTS for Ubuntu, 1.1.14 for pacemaker and 0.9.149 for pcs.
Error when enabling Pacemaker service
# sudo systemctl enable pacemaker
Synchronizing state of pacemaker.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable pacemaker
update-rc.d: error: pacemaker Default-Start contains no runlevels, aborting.
Error when starting the cluster
sudo pcs cluster start --all
mbubuntu1: 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.
mbubuntu2: 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.
And the output of the log file is:
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/lib/systemd/system/corosync.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2017-03-16 11:13:17 PDT; 29s ago
Process: 22052 ExecStart=/usr/sbin/corosync -f $OPTIONS (code=exited, status=7)
Main PID: 22052 (code=exited, status=7)
Mar 16 11:13:17 mbubuntu2 systemd[1]: Starting Corosync Cluster Engine...
Mar 16 11:13:17 mbubuntu2 corosync[22052]: parse error in config: Can't open logfile '/var/log/cluster/corosync.log' for reason: No such file or directory (2).
Mar 16 11:13:17 mbubuntu2 systemd[1]: corosync.service: Main process exited, code=exited, status=7/NOTRUNNING
Mar 16 11:13:17 mbubuntu2 systemd[1]: Failed to start Corosync Cluster Engine.
Mar 16 11:13:17 mbubuntu2 systemd[1]: corosync.service: Unit entered failed state.
Mar 16 11:13:17 mbubuntu2 systemd[1]: corosync.service: Failed with result 'exit-code'.
~
Errors are very easy to repro and consistent |
16.04.2 LTS for Ubuntu, 1.1.14 for pacemaker and 0.9.149 for pcs.
Install Pacemaker packages:
sudo apt-get install pacemaker pcs fence-agents resource-agents
Set the password for the default user:
sudo passwd hacluster
#To clear files
sudo pcs cluster destroy
Enable and start pcsd/pacemaker:
sudo systemctl enable pcsd
sudo systemctl start pcsd
sudo systemctl enable pacemaker
sudo pcs cluster auth pacemaker-1 pacemaker-2 -u hacluster -p haclusterpassword
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
Workaround
On both nodes, Replace the line:
logfile: /var/log/cluster/corosync.log
with
logfile: /var/log/corosync/corosync.log
(or create the expected log file.
Errors are very easy to repro and consistent |
|
| 2017-03-20 21:31:01 |
Bryan Quigley |
description |
16.04.2 LTS for Ubuntu, 1.1.14 for pacemaker and 0.9.149 for pcs.
Install Pacemaker packages:
sudo apt-get install pacemaker pcs fence-agents resource-agents
Set the password for the default user:
sudo passwd hacluster
#To clear files
sudo pcs cluster destroy
Enable and start pcsd/pacemaker:
sudo systemctl enable pcsd
sudo systemctl start pcsd
sudo systemctl enable pacemaker
sudo pcs cluster auth pacemaker-1 pacemaker-2 -u hacluster -p haclusterpassword
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
Workaround
On both nodes, Replace the line:
logfile: /var/log/cluster/corosync.log
with
logfile: /var/log/corosync/corosync.log
(or create the expected log file.
Errors are very easy to repro and consistent |
16.04.2 LTS for Ubuntu, 1.1.14 for pacemaker and 0.9.149 for pcs.
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
Workaround
On both nodes, Replace the line:
logfile: /var/log/cluster/corosync.log
with
logfile: /var/log/corosync/corosync.log
(or create the expected log file.
Errors are very easy to repro and consistent |
|
| 2017-03-20 21:31:14 |
Bryan Quigley |
affects |
ubuntu |
pcs (Ubuntu) |
|
| 2017-03-20 21:31:32 |
Bryan Quigley |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-03-21 14:05:06 |
Bryan Quigley |
description |
16.04.2 LTS for Ubuntu, 1.1.14 for pacemaker and 0.9.149 for pcs.
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
Workaround
On both nodes, Replace the line:
logfile: /var/log/cluster/corosync.log
with
logfile: /var/log/corosync/corosync.log
(or create the expected log file.
Errors are very easy to repro and consistent |
[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
__
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. |
|
| 2017-03-21 14:14:22 |
Bryan Quigley |
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
__
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. |
[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. |
|
| 2017-03-21 14:48:09 |
Bryan Quigley |
attachment added |
|
pcs_0.9.149-1ubuntu2.debdiff https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1673579/+attachment/4841690/+files/pcs_0.9.149-1ubuntu2.debdiff |
|
| 2017-03-21 16:28:38 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2017-03-21 16:28:45 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2017-03-21 23:08:00 |
Mathew Hodson |
pcs (Ubuntu): importance |
Undecided |
Low |
|
| 2017-03-21 23:09:06 |
Mathew Hodson |
tags |
patch |
patch xenial |
|
| 2017-03-21 23:09:31 |
Mathew Hodson |
bug |
|
|
added subscriber Mathew Hodson |
| 2017-03-24 14:58:39 |
Bryan Quigley |
pcs (Ubuntu): status |
New |
Fix Released |
|
| 2017-03-25 21:48:50 |
Mathew Hodson |
removed subscriber Mathew Hodson |
|
|
|
| 2017-03-28 14:21:38 |
Robie Basak |
bug task added |
|
pcs (Ubuntu Xenial) |
|
| 2017-03-28 14:22:12 |
Bryan Quigley |
pcs (Ubuntu Xenial): assignee |
|
Bryan Quigley (bryanquigley) |
|
| 2017-04-01 05:10:37 |
Mathew Hodson |
pcs (Ubuntu Xenial): importance |
Undecided |
Low |
|
| 2017-04-03 18:36:51 |
Bryan Quigley |
pcs (Ubuntu Xenial): status |
New |
Triaged |
|
| 2017-04-03 18:37:04 |
Bryan Quigley |
pcs (Ubuntu Xenial): status |
Triaged |
In Progress |
|
| 2017-04-04 15:26:46 |
Bryan Quigley |
tags |
patch xenial |
patch sts xenial |
|
| 2017-04-04 15:27:13 |
Bryan Quigley |
bug |
|
|
added subscriber Canonical Support |
| 2017-05-04 21:47:01 |
Brian Murray |
pcs (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-05-04 21:47:05 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-05-04 21:47:07 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2017-05-04 21:47:14 |
Brian Murray |
tags |
patch sts xenial |
patch sts verification-needed xenial |
|
| 2017-05-05 14:29:24 |
Bryan Quigley |
tags |
patch sts verification-needed xenial |
patch sts verification-done xenial |
|
| 2017-05-17 11:54:38 |
Robie Basak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-05-17 12:04:41 |
Launchpad Janitor |
pcs (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
