** Description changed:

- 16.04.2 LTS for Ubuntu, 1.1.14 for pacemaker and 0.9.149 for pcs.
+ [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
  
- (or create the expected log file.
  
- Errors are very easy to repro and consistent
+ [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.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673579

Title:
  Corosync/Pacemaker: Error when enabling Pacemaker service,Error when
  starting the cluster

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1673579/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to