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

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Mathew Hodson (mathew-hodson):

[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)"

** Affects: libqb (Ubuntu)
     Importance: Medium
         Status: Fix Released

** Affects: libqb (Ubuntu Trusty)
     Importance: Medium
     Assignee: Eric Desrochers (slashd)
         Status: Fix Committed

** Affects: libqb (Ubuntu Wily)
     Importance: Medium
     Assignee: Eric Desrochers (slashd)
         Status: In Progress


** Tags: patch sts sts-sru ubuntu-sponsors verification-done
-- 
Pacemaker fails to start and reports a Library Error
https://bugs.launchpad.net/bugs/1595627
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.