| 2012-05-16 17:19:28 |
Jacob Smith |
bug |
|
|
added bug |
| 2012-05-16 17:23:58 |
Jacob Smith |
bug task added |
|
linux (Ubuntu) |
|
| 2012-05-16 17:30:06 |
Brad Figg |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2012-05-16 18:40:30 |
Jacob Smith |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2012-05-16 18:42:53 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
Medium |
|
| 2012-05-16 18:45:05 |
Joseph Salisbury |
tags |
|
lucid regression-update |
|
| 2012-05-16 19:11:34 |
Jacob Smith |
description |
Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8
Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685
This causes the drbd fencing script's exit codes to be incorrectly interpreted which then breaks the drbd fencing:
To replicate:
Have fencing enabled in drbd config:
In handlers section: fence-peer "/usr/lib/drbd/crm-fence-peer.sh"
In the disk section: fencing resource-only;
Have both drbd nodes uptodate with one primary one secondary
Make the fence-peer get executed. I did this by:
Having drbd under pacemaker control. Both pacemaker nodes were online and in-sync. Drbd in primary on node 1. Put node 1 in standby. Fence-peer will get executed.
Fence handler will report fence-peer exited with 0 (broken) - such as this:
May 15 09:45:17 kernel: [56645.420714] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0
May 15 09:45:17 kernel: [56645.420920] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 exit code 0 (0x0)
May 15 09:45:17 kernel: [56645.420925] block drbd0: fence-peer helper broken, returned 0
If you log debug output of fence-peer script (crm-fence-peer.sh) when executed it exits 4 not the kernel reported 0.
This commit in drbd git should fix this behavior:
http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43
This will cause complete failure of a drbd setup using fencing to auto-recover or continue without manual intervention and repair. |
Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8
Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685
This causes the drbd fencing script's exit codes to be incorrectly interpreted which then breaks the drbd fencing:
**** This also affects linux source in all distributions after Lucid with the applicable kernel versions patched in bug 963685 above since the drbd kernel module is mainlined in those more recent kernel versions ****
To replicate:
Have fencing enabled in drbd config:
In handlers section: fence-peer "/usr/lib/drbd/crm-fence-peer.sh"
In the disk section: fencing resource-only;
Have both drbd nodes uptodate with one primary one secondary
Make the fence-peer get executed. I did this by:
Having drbd under pacemaker control. Both pacemaker nodes were online and in-sync. Drbd in primary on node 1. Put node 1 in standby. Fence-peer will get executed.
Fence handler will report fence-peer exited with 0 (broken) - such as this:
May 15 09:45:17 kernel: [56645.420714] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0
May 15 09:45:17 kernel: [56645.420920] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 exit code 0 (0x0)
May 15 09:45:17 kernel: [56645.420925] block drbd0: fence-peer helper broken, returned 0
If you log debug output of fence-peer script (crm-fence-peer.sh) when executed it exits 4 not the kernel reported 0.
This commit in drbd git should fix this behavior:
http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43
This will cause complete failure of a drbd setup using fencing to auto-recover or continue without manual intervention and repair. |
|
| 2012-05-16 19:38:44 |
Jacob Smith |
drbd8 (Ubuntu): status |
New |
Confirmed |
|
| 2012-05-17 07:24:58 |
Ante Karamatić |
linux (Ubuntu): status |
Confirmed |
Invalid |
|
| 2012-05-17 07:25:50 |
Ante Karamatić |
nominated for series |
|
Ubuntu Lucid |
|
| 2012-05-17 07:32:57 |
Ante Karamatić |
drbd8 (Ubuntu): importance |
Undecided |
Medium |
|
| 2012-05-17 07:33:18 |
Ante Karamatić |
attachment added |
|
Upstream solution for the problem https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+attachment/3150177/+files/lp-1000355.debdiff |
|
| 2012-05-17 07:35:02 |
Ante Karamatić |
summary |
drbd fence-peer breaks when using kernel 2.6.32-41 |
[SRU] drbd fence-peer breaks when using kernel 2.6.32-41 |
|
| 2012-05-17 07:38:09 |
Ante Karamatić |
description |
Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8
Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685
This causes the drbd fencing script's exit codes to be incorrectly interpreted which then breaks the drbd fencing:
**** This also affects linux source in all distributions after Lucid with the applicable kernel versions patched in bug 963685 above since the drbd kernel module is mainlined in those more recent kernel versions ****
To replicate:
Have fencing enabled in drbd config:
In handlers section: fence-peer "/usr/lib/drbd/crm-fence-peer.sh"
In the disk section: fencing resource-only;
Have both drbd nodes uptodate with one primary one secondary
Make the fence-peer get executed. I did this by:
Having drbd under pacemaker control. Both pacemaker nodes were online and in-sync. Drbd in primary on node 1. Put node 1 in standby. Fence-peer will get executed.
Fence handler will report fence-peer exited with 0 (broken) - such as this:
May 15 09:45:17 kernel: [56645.420714] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0
May 15 09:45:17 kernel: [56645.420920] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 exit code 0 (0x0)
May 15 09:45:17 kernel: [56645.420925] block drbd0: fence-peer helper broken, returned 0
If you log debug output of fence-peer script (crm-fence-peer.sh) when executed it exits 4 not the kernel reported 0.
This commit in drbd git should fix this behavior:
http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43
This will cause complete failure of a drbd setup using fencing to auto-recover or continue without manual intervention and repair. |
SRU Justification
Upstream commit:
e6cbc43 - http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43
Description:
Latest 10.04 kernel (2.6.32-41) fixed and issue described in bug 963685. Cause of this change, drbd module, build with dkms, regressed and can not be used as intended.
Notes (original report):
Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8
Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685
This causes the drbd fencing script's exit codes to be incorrectly interpreted which then breaks the drbd fencing:
**** This also affects linux source in all distributions after Lucid with the applicable kernel versions patched in bug 963685 above since the drbd kernel module is mainlined in those more recent kernel versions ****
To replicate:
Have fencing enabled in drbd config:
In handlers section: fence-peer "/usr/lib/drbd/crm-fence-peer.sh"
In the disk section: fencing resource-only;
Have both drbd nodes uptodate with one primary one secondary
Make the fence-peer get executed. I did this by:
Having drbd under pacemaker control. Both pacemaker nodes were online and in-sync. Drbd in primary on node 1. Put node 1 in standby. Fence-peer will get executed.
Fence handler will report fence-peer exited with 0 (broken) - such as this:
May 15 09:45:17 kernel: [56645.420714] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0
May 15 09:45:17 kernel: [56645.420920] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 exit code 0 (0x0)
May 15 09:45:17 kernel: [56645.420925] block drbd0: fence-peer helper broken, returned 0
If you log debug output of fence-peer script (crm-fence-peer.sh) when executed it exits 4 not the kernel reported 0.
This commit in drbd git should fix this behavior:
http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43
This will cause complete failure of a drbd setup using fencing to auto-recover or continue without manual intervention and repair. |
|
| 2012-05-17 07:38:29 |
Ante Karamatić |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2012-05-17 07:40:01 |
Ante Karamatić |
drbd8 (Ubuntu): assignee |
|
Ante Karamatić (ivoks) |
|
| 2012-05-17 07:43:31 |
Ante Karamatić |
description |
SRU Justification
Upstream commit:
e6cbc43 - http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43
Description:
Latest 10.04 kernel (2.6.32-41) fixed and issue described in bug 963685. Cause of this change, drbd module, build with dkms, regressed and can not be used as intended.
Notes (original report):
Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8
Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685
This causes the drbd fencing script's exit codes to be incorrectly interpreted which then breaks the drbd fencing:
**** This also affects linux source in all distributions after Lucid with the applicable kernel versions patched in bug 963685 above since the drbd kernel module is mainlined in those more recent kernel versions ****
To replicate:
Have fencing enabled in drbd config:
In handlers section: fence-peer "/usr/lib/drbd/crm-fence-peer.sh"
In the disk section: fencing resource-only;
Have both drbd nodes uptodate with one primary one secondary
Make the fence-peer get executed. I did this by:
Having drbd under pacemaker control. Both pacemaker nodes were online and in-sync. Drbd in primary on node 1. Put node 1 in standby. Fence-peer will get executed.
Fence handler will report fence-peer exited with 0 (broken) - such as this:
May 15 09:45:17 kernel: [56645.420714] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0
May 15 09:45:17 kernel: [56645.420920] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 exit code 0 (0x0)
May 15 09:45:17 kernel: [56645.420925] block drbd0: fence-peer helper broken, returned 0
If you log debug output of fence-peer script (crm-fence-peer.sh) when executed it exits 4 not the kernel reported 0.
This commit in drbd git should fix this behavior:
http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43
This will cause complete failure of a drbd setup using fencing to auto-recover or continue without manual intervention and repair. |
SRU Justification
Upstream commit:
e6cbc43 - http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43
Description:
Latest 10.04 kernel (2.6.32-41) fixed an issue described in bug 963685. Cause of this change, drbd module, built with dkms, regressed and can not be used as intended.
Notes (original report):
Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8
Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685
This causes the drbd fencing script's exit codes to be incorrectly interpreted which then breaks the drbd fencing:
**** This also affects linux source in all distributions after Lucid with the applicable kernel versions patched in bug 963685 above since the drbd kernel module is mainlined in those more recent kernel versions ****
To replicate:
Have fencing enabled in drbd config:
In handlers section: fence-peer "/usr/lib/drbd/crm-fence-peer.sh"
In the disk section: fencing resource-only;
Have both drbd nodes uptodate with one primary one secondary
Make the fence-peer get executed. I did this by:
Having drbd under pacemaker control. Both pacemaker nodes were online and in-sync. Drbd in primary on node 1. Put node 1 in standby. Fence-peer will get executed.
Fence handler will report fence-peer exited with 0 (broken) - such as this:
May 15 09:45:17 kernel: [56645.420714] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0
May 15 09:45:17 kernel: [56645.420920] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 exit code 0 (0x0)
May 15 09:45:17 kernel: [56645.420925] block drbd0: fence-peer helper broken, returned 0
If you log debug output of fence-peer script (crm-fence-peer.sh) when executed it exits 4 not the kernel reported 0.
This commit in drbd git should fix this behavior:
http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43
This will cause complete failure of a drbd setup using fencing to auto-recover or continue without manual intervention and repair. |
|
| 2012-05-17 14:19:50 |
Herton R. Krzesinski |
bug task deleted |
linux (Ubuntu) |
|
|
| 2012-05-17 14:20:28 |
Herton R. Krzesinski |
nominated for series |
|
Ubuntu Lucid |
|
| 2012-05-17 14:27:12 |
Herton R. Krzesinski |
bug |
|
|
added subscriber Herton R. Krzesinski |
| 2012-05-17 15:29:53 |
Tim Gardner |
attachment added |
|
Added usermodehelper-consistently.dpatch to debian/patches/00list https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+attachment/3150746/+files/diff.txt |
|
| 2012-05-17 15:30:55 |
Tim Gardner |
bug task added |
|
drbd8 (Ubuntu Lucid) |
|
| 2012-05-17 15:31:03 |
Tim Gardner |
drbd8 (Ubuntu Lucid): status |
New |
Fix Committed |
|
| 2012-05-17 15:33:37 |
Tim Gardner |
drbd8 (Ubuntu Lucid): assignee |
|
Ante Karamatić (ivoks) |
|
| 2012-05-17 15:33:47 |
Tim Gardner |
drbd8 (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2012-05-17 18:31:54 |
Bryce Harrington |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2012-05-18 08:16:49 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2012-05-18 08:16:54 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2012-05-18 08:16:55 |
Martin Pitt |
tags |
lucid regression-update |
lucid regression-update verification-needed |
|
| 2012-05-18 08:49:41 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/lucid-proposed/drbd8 |
|
| 2012-05-26 21:18:37 |
tmortensen |
bug |
|
|
added subscriber tmortensen |
| 2012-06-05 14:47:17 |
Netadmin |
bug |
|
|
added subscriber Netadmin |
| 2012-06-06 07:01:38 |
Ante Karamatić |
tags |
lucid regression-update verification-needed |
lucid regression-update verification-done |
|
| 2012-06-07 10:11:16 |
Launchpad Janitor |
drbd8 (Ubuntu Lucid): status |
Fix Committed |
Fix Released |
|
