[Bug 1595627] Re: Pacemaker fails to start and reports a Library Error

[Martin Pitt]

Hello Eric, or anyone else affected,

Accepted libqb into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/libqb/0.16.0.real-
1ubuntu5 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libqb (Ubuntu Trusty)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
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/1595627

Title:
  Pacemaker fails to start and reports a Library Error

Status in libqb package in Ubuntu:
  Fix Released
Status in libqb source package in Trusty:
  Fix Committed
Status in libqb source package in Wily:
  In Progress

Bug description:
  [SRU JUSTIFICATION]

  [Impact]

  Pacemaker fails to start and reports a Library Error as follow :
  "notice: mcp_read_config: 	Configured corosync to accept connections from group 124: Library error (2)"

  [Test Case]

  - Have a corosync/pacemaker cluster with libqb version <=0.16.0.real-1ubuntu4
  - You need sequentially start/stop Corosync/Pacemaker for some amount of times to trigger the issue (until both PIDs of corosync/pacemaker are >99999 and fd >=10 to trigger this issue)

  [Regression Potential]

  The patch is already in place in Debian & Xenial and late Ubuntu
  release version.

  This patch make the description field larger to satisfy all possible
  pids and file descriptor values.

  [Other Info]

  Upstream Commit:

  0766a3ca Increase the length of description field
  https://github.com/ClusterLabs/libqb/commit/0766a3ca5473a9e126e91022075b4b3798b8d5bc

  Note : The commit has been introduced first in upstream branch :
  v0.17.2

  [Original Description]

  It has been brought to my attention by a user the following :

  Pacemaker fails to start if its PID is greater than 99999, then it
  reports a Library error as follow :

  notice: mcp_read_config: Configured corosync to accept connections
  from group 124: Library error (2)"

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