| 2015-03-13 21:46:18 |
Mauricio Faria de Oliveira |
bug |
|
|
added bug |
| 2015-03-17 20:41:37 |
Mathieu Trudel-Lapierre |
multipath-tools (Ubuntu): status |
New |
Triaged |
|
| 2015-03-17 20:41:40 |
Mathieu Trudel-Lapierre |
multipath-tools (Ubuntu): importance |
Undecided |
Medium |
|
| 2015-03-17 20:41:44 |
Mathieu Trudel-Lapierre |
multipath-tools (Ubuntu): assignee |
|
Mathieu Trudel-Lapierre (mathieu-tl) |
|
| 2015-04-13 22:35:40 |
Mauricio Faria de Oliveira |
attachment added |
|
multipath-tools_whitespacedIDs.debdiff https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1432062/+attachment/4374518/+files/multipath-tools_whitespacedIDs.debdiff |
|
| 2015-04-13 22:36:42 |
Mauricio Faria de Oliveira |
summary |
Ship the default /etc/multipath.conf on multipath-tools-boot (for user_friendly_names) |
multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers |
|
| 2015-04-13 22:36:58 |
Mauricio Faria de Oliveira |
tags |
|
patch |
|
| 2015-04-14 00:21:44 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2015-04-22 14:39:54 |
Mauricio Faria de Oliveira |
attachment added |
|
multipath-tools_whitespacedIDs.debdiff https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1432062/+attachment/4381491/+files/multipath-tools_whitespacedIDs.debdiff |
|
| 2015-06-04 13:12:57 |
Scott Moser |
description |
If a system is not installed w/ multipath support (i.e., no disk-detect/multipath/enable=true), the /etc/multipath.conf file is not installed.
If an user later installs multipath-tools-boot, it will enable the udev rules for multipath support.
Those rules don't handle disk devices w/ spaces on their names/uuids/models very well..
That's because of udev's SYMLINK command using spaces to separate multiple links, and the kernel sysfs/dm informing \x20 instead, which is not correctly interpreted by some commands, resulting in file not found errors, for example.
Thus, the system fails to boot.
There's no problem, however, if user_friendly_names is enabled in multipath.conf (which is enabled in the default multipath.conf from the installer, if it has multipath enabled).
Notice it's an acceptable case to install w/out multipath support, and enable it later for booting.
Disk devices w/ spaces in naming is not common over SAN/storage systems, but that happens often for conventional disks; for example:
- IBM IPR ( IBM IPR-0 5DB6F40000000080 )
- IBM VDASD ( AIX VDASD 00c96f0700004c000000014bb8e713f0.14 )
- QEMU HARDDISK ( QEMU QEMU HARDDISK <serial> )
So, please, is it possible to ship the default multipath.conf (e.g., from installer) w/ multipath-tools-boot?
For users not to their systems failing to boot after installing multipath-tools-boot manually, after a non-multipath install. |
If a system is not installed w/ multipath support (i.e., no disk-detect/multipath/enable=true), the /etc/multipath.conf file is not installed.
If an user later installs multipath-tools-boot, it will enable the udev rules for multipath support.
Those rules don't handle disk devices w/ spaces on their names/uuids/models very well..
That's because of udev's SYMLINK command using spaces to separate multiple links, and the kernel sysfs/dm informing \x20 instead, which is not correctly interpreted by some commands, resulting in file not found errors, for example.
Thus, the system fails to boot.
There's no problem, however, if user_friendly_names is enabled in multipath.conf (which is enabled in the default multipath.conf from the installer, if it has multipath enabled).
Notice it's an acceptable case to install w/out multipath support, and enable it later for booting.
Disk devices w/ spaces in naming is not common over SAN/storage systems, but that happens often for conventional disks; for example:
- IBM IPR ( IBM IPR-0 5DB6F40000000080 )
- IBM VDASD ( AIX VDASD 00c96f0700004c000000014bb8e713f0.14 )
- QEMU HARDDISK ( QEMU QEMU HARDDISK <serial> )
So, please, is it possible to ship the default multipath.conf (e.g., from installer) w/ multipath-tools-boot?
For users not to their systems failing to boot after installing multipath-tools-boot manually, after a non-multipath install.
Related bugs:
* bug 1371634: block devices appear twice |
|
| 2015-07-28 15:49:19 |
Mauricio Faria de Oliveira |
multipath-tools (Ubuntu): status |
Triaged |
Fix Committed |
|
| 2015-07-28 15:49:52 |
Mauricio Faria de Oliveira |
multipath-tools (Ubuntu): status |
Fix Committed |
Confirmed |
|
| 2015-07-28 17:33:53 |
Mauricio Faria de Oliveira |
tags |
patch |
patch targetmilestone-inin1404 targetmilestone-inin1504 |
|
| 2015-09-02 13:04:12 |
Mathieu Trudel-Lapierre |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2016-01-07 19:00:36 |
Mauricio Faria de Oliveira |
attachment added |
|
multipath-tools_kpartx-spaces.debdiff https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1432062/+attachment/4545834/+files/multipath-tools_kpartx-spaces.debdiff |
|
| 2016-01-30 02:35:39 |
Launchpad Janitor |
multipath-tools (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2016-02-01 14:53:30 |
Mathieu Trudel-Lapierre |
nominated for series |
|
Ubuntu Trusty |
|
| 2016-02-01 14:53:30 |
Mathieu Trudel-Lapierre |
bug task added |
|
multipath-tools (Ubuntu Trusty) |
|
| 2016-02-01 14:53:38 |
Mathieu Trudel-Lapierre |
multipath-tools (Ubuntu Trusty): status |
New |
In Progress |
|
| 2016-02-01 14:53:40 |
Mathieu Trudel-Lapierre |
multipath-tools (Ubuntu Trusty): importance |
Undecided |
Medium |
|
| 2016-02-01 14:53:42 |
Mathieu Trudel-Lapierre |
multipath-tools (Ubuntu Trusty): assignee |
|
Mathieu Trudel-Lapierre (mathieu-tl) |
|
| 2016-02-01 14:59:54 |
Mathieu Trudel-Lapierre |
description |
If a system is not installed w/ multipath support (i.e., no disk-detect/multipath/enable=true), the /etc/multipath.conf file is not installed.
If an user later installs multipath-tools-boot, it will enable the udev rules for multipath support.
Those rules don't handle disk devices w/ spaces on their names/uuids/models very well..
That's because of udev's SYMLINK command using spaces to separate multiple links, and the kernel sysfs/dm informing \x20 instead, which is not correctly interpreted by some commands, resulting in file not found errors, for example.
Thus, the system fails to boot.
There's no problem, however, if user_friendly_names is enabled in multipath.conf (which is enabled in the default multipath.conf from the installer, if it has multipath enabled).
Notice it's an acceptable case to install w/out multipath support, and enable it later for booting.
Disk devices w/ spaces in naming is not common over SAN/storage systems, but that happens often for conventional disks; for example:
- IBM IPR ( IBM IPR-0 5DB6F40000000080 )
- IBM VDASD ( AIX VDASD 00c96f0700004c000000014bb8e713f0.14 )
- QEMU HARDDISK ( QEMU QEMU HARDDISK <serial> )
So, please, is it possible to ship the default multipath.conf (e.g., from installer) w/ multipath-tools-boot?
For users not to their systems failing to boot after installing multipath-tools-boot manually, after a non-multipath install.
Related bugs:
* bug 1371634: block devices appear twice |
[Impact]
If a system is not installed w/ multipath support (i.e., no disk-detect/multipath/enable=true), the /etc/multipath.conf file is not installed.
If an user later installs multipath-tools-boot, it will enable the udev rules for multipath support.
Those rules don't handle disk devices w/ spaces on their names/uuids/models very well..
That's because of udev's SYMLINK command using spaces to separate multiple links, and the kernel sysfs/dm informing \x20 instead, which is not correctly interpreted by some commands, resulting in file not found errors, for example.
Thus, the system fails to boot.
[Test case]
Requires installing on a system where there are spaces in the name of the device make/model data; for instance, on POWER8 with IPR disks, or with QEMU.
1) Install system with multipath support ('disk-detect/multipath/enable=true').
2) Boot the system.
3) Edit /etc/multipath.conf, remove "user_friendly_names yes" ; replace with "user_friendly_names no", or remove /etc/multipath.conf.
4) Update the initramfs: sudo update-initramfs -u
5) Reboot.
[Regression potential]
Minimal. Systems with names in the disk make/model data would not boot without user_friendly_names enabled. This patch will allow multipath-tools to correctly handle these devices in the case where friendly names are not enabled by using the devices major/minor numbers rather that its path.
----
There's no problem, however, if user_friendly_names is enabled in multipath.conf (which is enabled in the default multipath.conf from the installer, if it has multipath enabled).
Notice it's an acceptable case to install w/out multipath support, and enable it later for booting.
Disk devices w/ spaces in naming is not common over SAN/storage systems, but that happens often for conventional disks; for example:
- IBM IPR ( IBM IPR-0 5DB6F40000000080 )
- IBM VDASD ( AIX VDASD 00c96f0700004c000000014bb8e713f0.14 )
- QEMU HARDDISK ( QEMU QEMU HARDDISK <serial> )
So, please, is it possible to ship the default multipath.conf (e.g., from installer) w/ multipath-tools-boot?
For users not to their systems failing to boot after installing multipath-tools-boot manually, after a non-multipath install.
Related bugs:
* bug 1371634: block devices appear twice |
|
| 2016-02-01 16:48:45 |
Mathieu Trudel-Lapierre |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-02-05 00:04:49 |
Brian Murray |
multipath-tools (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2016-02-05 00:04:53 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2016-02-05 00:04:56 |
Brian Murray |
tags |
patch targetmilestone-inin1404 targetmilestone-inin1504 |
patch targetmilestone-inin1404 targetmilestone-inin1504 verification-needed |
|
| 2016-02-05 12:16:46 |
Mauricio Faria de Oliveira |
tags |
patch targetmilestone-inin1404 targetmilestone-inin1504 verification-needed |
patch targetmilestone-inin1404 targetmilestone-inin1504 verification-done |
|
| 2016-02-11 19:07:56 |
Brian Murray |
tags |
patch targetmilestone-inin1404 targetmilestone-inin1504 verification-done |
patch targetmilestone-inin1404 targetmilestone-inin1504 |
|
| 2016-02-11 19:07:57 |
Brian Murray |
tags |
patch targetmilestone-inin1404 targetmilestone-inin1504 |
patch targetmilestone-inin1404 targetmilestone-inin1504 verification-needed |
|
| 2016-02-11 21:48:37 |
Mathieu Trudel-Lapierre |
tags |
patch targetmilestone-inin1404 targetmilestone-inin1504 verification-needed |
patch targetmilestone-inin1404 targetmilestone-inin1504 verification-done |
|
| 2016-02-15 23:15:28 |
Launchpad Janitor |
multipath-tools (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2016-02-15 23:15:46 |
Adam Conrad |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-03-02 14:27:14 |
Scott Moser |
description |
[Impact]
If a system is not installed w/ multipath support (i.e., no disk-detect/multipath/enable=true), the /etc/multipath.conf file is not installed.
If an user later installs multipath-tools-boot, it will enable the udev rules for multipath support.
Those rules don't handle disk devices w/ spaces on their names/uuids/models very well..
That's because of udev's SYMLINK command using spaces to separate multiple links, and the kernel sysfs/dm informing \x20 instead, which is not correctly interpreted by some commands, resulting in file not found errors, for example.
Thus, the system fails to boot.
[Test case]
Requires installing on a system where there are spaces in the name of the device make/model data; for instance, on POWER8 with IPR disks, or with QEMU.
1) Install system with multipath support ('disk-detect/multipath/enable=true').
2) Boot the system.
3) Edit /etc/multipath.conf, remove "user_friendly_names yes" ; replace with "user_friendly_names no", or remove /etc/multipath.conf.
4) Update the initramfs: sudo update-initramfs -u
5) Reboot.
[Regression potential]
Minimal. Systems with names in the disk make/model data would not boot without user_friendly_names enabled. This patch will allow multipath-tools to correctly handle these devices in the case where friendly names are not enabled by using the devices major/minor numbers rather that its path.
----
There's no problem, however, if user_friendly_names is enabled in multipath.conf (which is enabled in the default multipath.conf from the installer, if it has multipath enabled).
Notice it's an acceptable case to install w/out multipath support, and enable it later for booting.
Disk devices w/ spaces in naming is not common over SAN/storage systems, but that happens often for conventional disks; for example:
- IBM IPR ( IBM IPR-0 5DB6F40000000080 )
- IBM VDASD ( AIX VDASD 00c96f0700004c000000014bb8e713f0.14 )
- QEMU HARDDISK ( QEMU QEMU HARDDISK <serial> )
So, please, is it possible to ship the default multipath.conf (e.g., from installer) w/ multipath-tools-boot?
For users not to their systems failing to boot after installing multipath-tools-boot manually, after a non-multipath install.
Related bugs:
* bug 1371634: block devices appear twice |
[Impact]
If a system is not installed w/ multipath support (i.e., no disk-detect/multipath/enable=true), the /etc/multipath.conf file is not installed.
If an user later installs multipath-tools-boot, it will enable the udev rules for multipath support.
Those rules don't handle disk devices w/ spaces on their names/uuids/models very well..
That's because of udev's SYMLINK command using spaces to separate multiple links, and the kernel sysfs/dm informing \x20 instead, which is not correctly interpreted by some commands, resulting in file not found errors, for example.
Thus, the system fails to boot.
[Test case]
Requires installing on a system where there are spaces in the name of the device make/model data; for instance, on POWER8 with IPR disks, or with QEMU.
1) Install system with multipath support ('disk-detect/multipath/enable=true').
2) Boot the system.
3) Edit /etc/multipath.conf, remove "user_friendly_names yes" ; replace with "user_friendly_names no", or remove /etc/multipath.conf.
4) Update the initramfs: sudo update-initramfs -u
5) Reboot.
[Regression potential]
Minimal. Systems with names in the disk make/model data would not boot without user_friendly_names enabled. This patch will allow multipath-tools to correctly handle these devices in the case where friendly names are not enabled by using the devices major/minor numbers rather that its path.
----
There's no problem, however, if user_friendly_names is enabled in multipath.conf (which is enabled in the default multipath.conf from the installer, if it has multipath enabled).
Notice it's an acceptable case to install w/out multipath support, and enable it later for booting.
Disk devices w/ spaces in naming is not common over SAN/storage systems, but that happens often for conventional disks; for example:
- IBM IPR ( IBM IPR-0 5DB6F40000000080 )
- IBM VDASD ( AIX VDASD 00c96f0700004c000000014bb8e713f0.14 )
- QEMU HARDDISK ( QEMU QEMU HARDDISK <serial> )
So, please, is it possible to ship the default multipath.conf (e.g., from installer) w/ multipath-tools-boot?
For users not to their systems failing to boot after installing multipath-tools-boot manually, after a non-multipath install.
Related bugs:
* bug 1371634: block devices appear twice
* bug 1551937: lvm and multipath and xenial not happy together
* bug 1429327: Boot from a unique, stable, multipath-dependent symlink |
|
