Activity log for bug #1811795

Date Who What changed Old value New value Message
2019-01-15 10:46:04 Mariusz Tkaczyk bug added bug
2019-01-15 10:46:29 Mariusz Tkaczyk information type Public Private
2019-01-15 10:47:35 Mariusz Tkaczyk bug added subscriber Intel Team
2019-01-30 14:33:29 Launchpad Janitor mdadm (Ubuntu): status New Confirmed
2019-01-30 14:55:35 Christian Ehrhardt  bug added subscriber Christian Ehrhardt 
2019-01-30 14:55:39 Christian Ehrhardt  nominated for series Ubuntu Bionic
2019-01-30 14:55:39 Christian Ehrhardt  bug task added mdadm (Ubuntu Bionic)
2019-01-30 14:55:39 Christian Ehrhardt  nominated for series Ubuntu Cosmic
2019-01-30 14:55:39 Christian Ehrhardt  bug task added mdadm (Ubuntu Cosmic)
2019-01-30 14:55:43 Christian Ehrhardt  mdadm (Ubuntu): status Confirmed Fix Released
2019-02-11 15:09:14 Pawel Baldysiak information type Private Public
2019-04-10 14:27:39 Launchpad Janitor merge proposal linked https://code.launchpad.net/~paelzer/ubuntu/+source/mdadm/+git/mdadm/+merge/365794
2019-04-10 14:27:53 Launchpad Janitor merge proposal linked https://code.launchpad.net/~paelzer/ubuntu/+source/mdadm/+git/mdadm/+merge/365795
2019-04-10 14:41:05 Christian Ehrhardt  description Steps to reproduce: 1. Create IMSM container on 2 SATA disks. 2. Create R0 IMSM volume 3. Wait for resync to complete. 4. Fail one of disks Expected result: R0 Array should disappear form /proc/mdstat. Actual result: R0 array is visible in mdstat, link to container in /dev/md/ is removed. [Impact] * The response to device fails so far was to remove underlying containers. That failed if the device itself was not stopped before doing so causing issues. * Fix by backporting upstream fix [Test Case] * This needs a Intel(R) Matrix Storage Hardware which limits the systems this can be tested. 1. Create IMSM container on 2 SATA disks. 2. Create R0 IMSM volume 3. Wait for resync to complete. 4. Fail one of disks * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. [Regression Potential] * The patch changes the behavior on removing devices. So in that use-case lies the potential to regress somebody. It adds stopping the device before removing the containers associated to it (that is the fix). OTOH if there are cases where the kernel signals a device fail it would formerly not have removed it (the bug) but there are (very low) chances that somebody relies on that behavior. Since this avoids I/O errors on partially removed device elements I'd expect taking the change makes it better overall. [Other Info] * n/a --- Steps to reproduce: 1. Create IMSM container on 2 SATA disks. 2. Create R0 IMSM volume 3. Wait for resync to complete. 4. Fail one of disks Expected result: R0 Array should disappear form /proc/mdstat. Actual result: R0 array is visible in mdstat, link to container in /dev/md/ is removed.
2019-04-10 14:44:49 Christian Ehrhardt  mdadm (Ubuntu Cosmic): status New Incomplete
2019-04-10 14:44:51 Christian Ehrhardt  mdadm (Ubuntu Bionic): status New Incomplete
2019-04-19 13:09:16 Terry Rudd bug added subscriber Terry Rudd
2019-04-23 08:08:18 Christian Ehrhardt  description [Impact] * The response to device fails so far was to remove underlying containers. That failed if the device itself was not stopped before doing so causing issues. * Fix by backporting upstream fix [Test Case] * This needs a Intel(R) Matrix Storage Hardware which limits the systems this can be tested. 1. Create IMSM container on 2 SATA disks. 2. Create R0 IMSM volume 3. Wait for resync to complete. 4. Fail one of disks * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. [Regression Potential] * The patch changes the behavior on removing devices. So in that use-case lies the potential to regress somebody. It adds stopping the device before removing the containers associated to it (that is the fix). OTOH if there are cases where the kernel signals a device fail it would formerly not have removed it (the bug) but there are (very low) chances that somebody relies on that behavior. Since this avoids I/O errors on partially removed device elements I'd expect taking the change makes it better overall. [Other Info] * n/a --- Steps to reproduce: 1. Create IMSM container on 2 SATA disks. 2. Create R0 IMSM volume 3. Wait for resync to complete. 4. Fail one of disks Expected result: R0 Array should disappear form /proc/mdstat. Actual result: R0 array is visible in mdstat, link to container in /dev/md/ is removed. [Impact]  * The response to device fails so far was to remove underlying    containers. That failed if the device itself was not stopped    before doing so causing issues.  * Fix by backporting upstream fix [Test Case]  * This needs a Intel(R) Matrix Storage Hardware which limits the    systems this can be tested. 1. Create IMSM Container: mdadm -CR imsm0 -e imsm -n 2 /dev/sd[bc] 2. Create IMSM level 0 Array: mdadm -CR vol0 -l 0 -n 2 /dev/sd[bc] 3. Wait for resync to complete mdadm --wait /dev/md/vol0 4. Read /proc/mdstat and check /dev/md/ directory cat /proc/mdstat ls /dev/md/ 5. Fail one disk incrementaly (simulate device disappearing from system) mdadm -If sdc 6. Check mdstat file and /dev/md/ cat /proc/mdstat ls /dev/md/ Result: After disk fail [5] raid 0 array should disappear from mdstat, link /dev/md/imsm0 should exist.  * these should allow someone who is not familiar with the affected    package to reproduce the bug and verify that the updated package fixes    the problem. [Regression Potential]  * The patch changes the behavior on removing devices. So in that use-case    lies the potential to regress somebody.    It adds stopping the device before removing the containers associated    to it (that is the fix). OTOH if there are cases where the kernel    signals a device fail it would formerly not have removed it (the bug)    but there are (very low) chances that somebody relies on that behavior.    Since this avoids I/O errors on partially removed device elements I'd    expect taking the change makes it better overall. [Other Info]  * n/a --- Steps to reproduce: 1. Create IMSM container on 2 SATA disks. 2. Create R0 IMSM volume 3. Wait for resync to complete. 4. Fail one of disks Expected result: R0 Array should disappear form /proc/mdstat. Actual result: R0 array is visible in mdstat, link to container in /dev/md/ is removed.
2019-04-23 08:12:30 Christian Ehrhardt  mdadm (Ubuntu Bionic): status Incomplete Fix Committed
2019-04-23 08:12:32 Christian Ehrhardt  mdadm (Ubuntu Cosmic): status Incomplete Fix Committed
2019-04-23 08:12:35 Christian Ehrhardt  mdadm (Ubuntu Bionic): status Fix Committed In Progress
2019-04-23 08:12:36 Christian Ehrhardt  mdadm (Ubuntu Cosmic): status Fix Committed In Progress
2019-05-09 14:27:57 Łukasz Zemczak mdadm (Ubuntu Cosmic): status In Progress Fix Committed
2019-05-09 14:27:59 Łukasz Zemczak bug added subscriber Ubuntu Stable Release Updates Team
2019-05-09 14:28:36 Łukasz Zemczak bug added subscriber SRU Verification
2019-05-09 14:28:42 Łukasz Zemczak tags verification-needed verification-needed-cosmic
2019-05-09 14:50:02 Łukasz Zemczak mdadm (Ubuntu Bionic): status In Progress Fix Committed
2019-05-09 14:50:09 Łukasz Zemczak tags verification-needed verification-needed-cosmic verification-needed verification-needed-bionic verification-needed-cosmic
2019-05-13 10:17:08 Christian Ehrhardt  tags verification-needed verification-needed-bionic verification-needed-cosmic verification-done-bionic verification-needed verification-needed-cosmic
2019-05-20 09:20:27 Launchpad Janitor mdadm (Ubuntu Cosmic): status Fix Committed Fix Released
2019-05-20 09:20:38 Launchpad Janitor mdadm (Ubuntu Bionic): status Fix Committed Fix Released
2019-05-20 09:20:46 Łukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team