Activity log for bug #1595627

Date Who What changed Old value New value Message
2016-06-23 17:12:06 Eric Desrochers bug added bug
2016-06-23 17:29:02 Brian Murray nominated for series Ubuntu Wily
2016-06-23 17:29:02 Brian Murray bug task added libqb (Ubuntu Wily)
2016-06-23 17:29:02 Brian Murray nominated for series Ubuntu Trusty
2016-06-23 17:29:02 Brian Murray bug task added libqb (Ubuntu Trusty)
2016-06-23 17:34:40 Eric Desrochers libqb (Ubuntu Trusty): assignee Eric Desrochers (slashd)
2016-06-23 17:34:42 Eric Desrochers libqb (Ubuntu Wily): assignee Eric Desrochers (slashd)
2016-06-23 17:34:47 Eric Desrochers libqb (Ubuntu Trusty): importance Undecided Medium
2016-06-23 17:34:50 Eric Desrochers libqb (Ubuntu Wily): importance Undecided Medium
2016-06-23 17:37:46 Eric Desrochers 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)" [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. A test package has been tested by a user experiencing the problem and user confirms it solve the issue. 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)"
2016-06-23 17:59:10 Eric Desrochers libqb (Ubuntu): status New Fix Released
2016-06-23 18:01:30 David A. Desrosiers bug added subscriber David A. Desrosiers
2016-06-23 18:02:18 Launchpad Janitor libqb (Ubuntu Trusty): status New Confirmed
2016-06-23 18:02:18 Launchpad Janitor libqb (Ubuntu Wily): status New Confirmed
2016-06-23 18:02:38 Leonardo Borda bug added subscriber Leonardo Borda
2016-06-23 19:08:20 Eric Desrochers attachment added lp1595627_trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/libqb/+bug/1595627/+attachment/4689260/+files/lp1595627_trusty.debdiff
2016-06-23 19:09:05 Eric Desrochers attachment added lp1595627_wily.debdiff https://bugs.launchpad.net/ubuntu/+source/libqb/+bug/1595627/+attachment/4689261/+files/lp1595627_wily.debdiff
2016-06-23 19:09:56 Eric Desrochers tags patch sts sts-sponsor sts-sru ubuntu-sponsors
2016-06-23 19:10:07 Eric Desrochers bug added subscriber Ubuntu Sponsors Team
2016-06-23 19:10:14 Eric Desrochers bug added subscriber SRU Verification
2016-06-23 19:10:19 Eric Desrochers libqb (Ubuntu Trusty): status Confirmed In Progress
2016-06-23 19:10:22 Eric Desrochers libqb (Ubuntu Wily): status Confirmed In Progress
2016-06-23 19:14:14 Eric Desrochers 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. A test package has been tested by a user experiencing the problem and user confirms it solve the issue. 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)" [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)"
2016-06-24 15:33:23 Martin Pitt libqb (Ubuntu Trusty): status In Progress Fix Committed
2016-06-24 15:33:25 Martin Pitt bug added subscriber Ubuntu Stable Release Updates Team
2016-06-24 15:33:33 Martin Pitt tags patch sts sts-sponsor sts-sru ubuntu-sponsors patch sts sts-sponsor sts-sru ubuntu-sponsors verification-needed
2016-06-24 15:33:50 Martin Pitt removed subscriber Ubuntu Sponsors Team
2016-06-24 20:21:45 Eric Desrochers tags patch sts sts-sponsor sts-sru ubuntu-sponsors verification-needed patch sts sts-sru ubuntu-sponsors verification-needed
2016-06-27 20:26:51 Eric Desrochers tags patch sts sts-sru ubuntu-sponsors verification-needed patch sts sts-sru ubuntu-sponsors verification-done
2016-06-28 06:04:24 Mathew Hodson libqb (Ubuntu): importance Undecided Medium
2016-06-28 06:04:49 Mathew Hodson bug added subscriber Ubuntu Sponsors Team
2016-07-04 09:59:01 Launchpad Janitor libqb (Ubuntu Trusty): status Fix Committed Fix Released
2016-07-04 09:59:08 Martin Pitt removed subscriber Ubuntu Stable Release Updates Team
2016-07-04 15:26:33 Martin Pitt removed subscriber Ubuntu Sponsors Team
2016-07-15 14:35:35 Eric Desrochers libqb (Ubuntu Wily): status In Progress Won't Fix
2016-11-09 12:22:53 Louis Bouchard tags patch sts sts-sru ubuntu-sponsors verification-done patch sts ubuntu-sponsors verification-done