Activity log for bug #1538775

Date Who What changed Old value New value Message
2016-01-27 22:14:06 Stuart Hopkins bug added bug
2016-01-27 22:15:40 Stuart Hopkins affects saucy-backports multipath-tools (Ubuntu)
2016-02-01 14:45:23 Mathieu Trudel-Lapierre nominated for series Ubuntu Trusty
2016-02-01 14:45:23 Mathieu Trudel-Lapierre bug task added multipath-tools (Ubuntu Trusty)
2016-02-01 14:45:57 Mathieu Trudel-Lapierre multipath-tools (Ubuntu): status New Fix Released
2016-02-01 14:46:03 Mathieu Trudel-Lapierre multipath-tools (Ubuntu Trusty): status New In Progress
2016-02-01 14:46:05 Mathieu Trudel-Lapierre multipath-tools (Ubuntu Trusty): importance Undecided Medium
2016-02-01 14:46:07 Mathieu Trudel-Lapierre multipath-tools (Ubuntu Trusty): assignee Mathieu Trudel-Lapierre (mathieu-tl)
2016-02-01 14:48:24 Mathieu Trudel-Lapierre description Release: Ubuntu 14.04.3 LTS Kernel: linux-image-3.16.0-59-generic A clean system installed fresh today (2016-01-27) In attempting to configure a system to boot-from-SAN and enable multipath support I ran into an issue whereby despite the multiple paths being detected (when running the multipath command from the CLI) the configuration wasn't being enabled at boot. After examining /usr/share/initramfs-tools/scripts/local-top/multipath I found the following: verbose && log_begin_msg "Waiting for scsi storage" { rmmod scsi_wait_scan ; modprobe scsi_wait_scan ; rmmod scsi_wait_scan ; } >/dev/null 2>&1 verbose && log_end_msg The problem appears to be that the scsi_wait_scan module doesn't exist and so there is no wait before the multipath scan is performed. I managed to observe this briefly during bootup (with the script edited) and could see it performed the scan before sda/sdb was discovered. I also found a debian bug report indicating the module was removed a while back (https://lists.debian.org/debian-kernel/2012/05/msg00791.html). After adding in an artificial delay for testing the multipath command does what is expected and configures the paths accordingly. I'm not sure what the correct approach is if the scsi_wait_scan module is removed. I also found that the same local-top script doesnt have the dm-round-robin module loaded (but it is included in the initrd by the associated hook script), however I'm not sure if that is by design. I know I need it for my specific use-case, but don't know if it is deliberately excluded to prevent breakage on SAN units that don't support native round-robin. [Impact] Users of multipath may see an error message on every boot (when in verbose mode) about the scsi_wait_scan module being unavailable. [Test case] Boot 14.04 system with multipath-tools-boot. (Multipath devices installed, and the pacakge multipath-tools-boot installed). [Regression Potential] None. This module has been removed for a long while; as such this has no effect aside from removing an extra error message on boot. ------ Release: Ubuntu 14.04.3 LTS Kernel: linux-image-3.16.0-59-generic A clean system installed fresh today (2016-01-27) In attempting to configure a system to boot-from-SAN and enable multipath support I ran into an issue whereby despite the multiple paths being detected (when running the multipath command from the CLI) the configuration wasn't being enabled at boot. After examining /usr/share/initramfs-tools/scripts/local-top/multipath I found the following: verbose && log_begin_msg "Waiting for scsi storage" { rmmod scsi_wait_scan ; modprobe scsi_wait_scan ; rmmod scsi_wait_scan ; } >/dev/null 2>&1 verbose && log_end_msg The problem appears to be that the scsi_wait_scan module doesn't exist and so there is no wait before the multipath scan is performed. I managed to observe this briefly during bootup (with the script edited) and could see it performed the scan before sda/sdb was discovered. I also found a debian bug report indicating the module was removed a while back (https://lists.debian.org/debian-kernel/2012/05/msg00791.html). After adding in an artificial delay for testing the multipath command does what is expected and configures the paths accordingly. I'm not sure what the correct approach is if the scsi_wait_scan module is removed. I also found that the same local-top script doesnt have the dm-round-robin module loaded (but it is included in the initrd by the associated hook script), however I'm not sure if that is by design. I know I need it for my specific use-case, but don't know if it is deliberately excluded to prevent breakage on SAN units that don't support native round-robin.
2016-02-01 16:51:34 Mathieu Trudel-Lapierre bug added subscriber Ubuntu Stable Release Updates Team
2016-02-05 00:06:13 Brian Murray multipath-tools (Ubuntu Trusty): status In Progress Fix Committed
2016-02-05 00:06:16 Brian Murray bug added subscriber SRU Verification
2016-02-05 00:06:24 Brian Murray tags verification-needed
2016-02-05 10:37:20 Stuart Hopkins tags verification-needed verification-done
2016-02-11 19:09:03 Brian Murray tags verification-done
2016-02-11 19:09:04 Brian Murray tags verification-needed
2016-02-11 21:53:09 Mathieu Trudel-Lapierre tags verification-needed verification-done
2016-02-15 23:15:28 Launchpad Janitor multipath-tools (Ubuntu Trusty): status Fix Committed Fix Released
2016-02-15 23:16:04 Adam Conrad removed subscriber Ubuntu Stable Release Updates Team