| 2014-10-28 10:49:20 |
bugproxy |
bug |
|
|
added bug |
| 2014-10-28 10:49:23 |
bugproxy |
tags |
|
architecture-ppc64le bugnameltc-117319 severity-high targetmilestone-inin--- |
|
| 2014-10-28 10:49:24 |
bugproxy |
attachment added |
|
xml file of the guest https://bugs.launchpad.net/bugs/1386637/+attachment/4246996/+files/uu04g1.xml |
|
| 2014-10-28 12:40:09 |
Ubuntu Foundations Team Bug Bot |
tags |
architecture-ppc64le bugnameltc-117319 severity-high targetmilestone-inin--- |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- |
|
| 2014-10-28 14:32:49 |
Brian Murray |
affects |
ubuntu |
multipath-tools (Ubuntu) |
|
| 2015-08-13 22:09:10 |
Mathieu Trudel-Lapierre |
description |
Problem Description
======================
non-multpath disks are classified as multipath after the multipath-tools package is installed.
---uname output---
Linux uu04g1 3.16.0-21-generic #28-Ubuntu SMP Mon Oct 6 15:57:32 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Tuleta pKVM guest
Steps to Reproduce
=========================
1) Create a guest with an unused, non-mpath disk (not the install disk) (a qemu img file is fine).
2) apt-get install multipath-tools.
3) multipath -ll.
4) Note that your file backed disks are showing up as mpath disks.
Userspace tool common name: multipath
The userspace tool has the following bit modes: 64
System Dump Info:
The system is not configured to capture a system dump.
Userspace rpm: multipath-tools
Userspace tool obtained from project website: multipath-tools v0.4.9 (05/33, 2016)
== Comment: #1 - Edward R. Cheslek <echeslak@us.ibm.com> - ==
root@uu04g1:~# multipath -ll
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:1:0 sdb 8:16 active ready running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:2:0 sdc 8:32 active ready running
root@uu04g1:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 20G 0 disk
??sda1 8:1 0 7M 0 part
??sda2 8:2 0 19.1G 0 part /
??sda3 8:3 0 896M 0 part [SWAP]
sdb 8:16 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-1-0
252:0 0 20G 0 mpath
sdc 8:32 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-2-0
252:1 0 20G 0 mpath
root@uu04g1:~#
root@uu04g1:~# lsscsi
[0:0:0:0] disk QEMU QEMU HARDDISK 2.0. /dev/sda
[0:0:1:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdb
[0:0:2:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdc
== Comment: #2 - Edward R. Cheslek <echeslak@us.ibm.com> - 2014-10-08 22:27:09 ==
This is the xml file of the affected guest. Please note that all disks are file backed.
root@uu04g1:~# multipath -l
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:1:0 sdb 8:16 active undef running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:2:0 sdc 8:32 active undef running
root@uu04g1:~# multipath -v2
root@uu04g1:~# |
[Impact]
Users of multipath-tools on systems which exhibit both multipathed and non-multipathed drives or some USB devices (some USB devices may still be picked up by multipath-tools if multipath-capable).
[Test case]
- Boot on a system with multipathed disks with the previous version of multipath-tools
- Upgrade to the new version; verify that /etc/multipath/wwids is created and contains all the right device WWIDs, and that 'sudo multipath -ll' has the same devices.
- Reboot and verify that the system still boots correctly.
After rebooting, you should verify that /proc/mounts correctly lists the multipath device (/dev/mapper/*), and that /proc/swaps also lists any swap partitions that should be on a multipathed disk as a /dev/dm-* device.
[Regression potential]
Systems in complex setups mixing both multipathed and non-multipathed disks, or with particularly slow disk controllers may fail to boot or show delays in booting. Systems requiring a particular set of partitions to be available in early boot (past the typical installs on /, some may require /usr to be available for some daemons to load on boot) could fail to properly start up all the software on boot; these should be considered as regressions only if devices do not properly show up in 'sudo multipath -ll' output.
Users seeing issues should preferrably include the output of 'sudo multipath -v4' to bug reports to help developers in debugging.
---
Problem Description
======================
non-multpath disks are classified as multipath after the multipath-tools package is installed.
---uname output---
Linux uu04g1 3.16.0-21-generic #28-Ubuntu SMP Mon Oct 6 15:57:32 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Tuleta pKVM guest
Steps to Reproduce
=========================
1) Create a guest with an unused, non-mpath disk (not the install disk) (a qemu img file is fine).
2) apt-get install multipath-tools.
3) multipath -ll.
4) Note that your file backed disks are showing up as mpath disks.
Userspace tool common name: multipath
The userspace tool has the following bit modes: 64
System Dump Info:
The system is not configured to capture a system dump.
Userspace rpm: multipath-tools
Userspace tool obtained from project website: multipath-tools v0.4.9 (05/33, 2016)
== Comment: #1 - Edward R. Cheslek <echeslak@us.ibm.com> - ==
root@uu04g1:~# multipath -ll
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:1:0 sdb 8:16 active ready running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:2:0 sdc 8:32 active ready running
root@uu04g1:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 20G 0 disk
??sda1 8:1 0 7M 0 part
??sda2 8:2 0 19.1G 0 part /
??sda3 8:3 0 896M 0 part [SWAP]
sdb 8:16 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-1-0
252:0 0 20G 0 mpath
sdc 8:32 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-2-0
252:1 0 20G 0 mpath
root@uu04g1:~#
root@uu04g1:~# lsscsi
[0:0:0:0] disk QEMU QEMU HARDDISK 2.0. /dev/sda
[0:0:1:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdb
[0:0:2:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdc
== Comment: #2 - Edward R. Cheslek <echeslak@us.ibm.com> - 2014-10-08 22:27:09 ==
This is the xml file of the affected guest. Please note that all disks are file backed.
root@uu04g1:~# multipath -l
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:1:0 sdb 8:16 active undef running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:2:0 sdc 8:32 active undef running
root@uu04g1:~# multipath -v2
root@uu04g1:~# |
|
| 2015-08-18 08:40:26 |
Mathieu Trudel-Lapierre |
description |
[Impact]
Users of multipath-tools on systems which exhibit both multipathed and non-multipathed drives or some USB devices (some USB devices may still be picked up by multipath-tools if multipath-capable).
[Test case]
- Boot on a system with multipathed disks with the previous version of multipath-tools
- Upgrade to the new version; verify that /etc/multipath/wwids is created and contains all the right device WWIDs, and that 'sudo multipath -ll' has the same devices.
- Reboot and verify that the system still boots correctly.
After rebooting, you should verify that /proc/mounts correctly lists the multipath device (/dev/mapper/*), and that /proc/swaps also lists any swap partitions that should be on a multipathed disk as a /dev/dm-* device.
[Regression potential]
Systems in complex setups mixing both multipathed and non-multipathed disks, or with particularly slow disk controllers may fail to boot or show delays in booting. Systems requiring a particular set of partitions to be available in early boot (past the typical installs on /, some may require /usr to be available for some daemons to load on boot) could fail to properly start up all the software on boot; these should be considered as regressions only if devices do not properly show up in 'sudo multipath -ll' output.
Users seeing issues should preferrably include the output of 'sudo multipath -v4' to bug reports to help developers in debugging.
---
Problem Description
======================
non-multpath disks are classified as multipath after the multipath-tools package is installed.
---uname output---
Linux uu04g1 3.16.0-21-generic #28-Ubuntu SMP Mon Oct 6 15:57:32 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Tuleta pKVM guest
Steps to Reproduce
=========================
1) Create a guest with an unused, non-mpath disk (not the install disk) (a qemu img file is fine).
2) apt-get install multipath-tools.
3) multipath -ll.
4) Note that your file backed disks are showing up as mpath disks.
Userspace tool common name: multipath
The userspace tool has the following bit modes: 64
System Dump Info:
The system is not configured to capture a system dump.
Userspace rpm: multipath-tools
Userspace tool obtained from project website: multipath-tools v0.4.9 (05/33, 2016)
== Comment: #1 - Edward R. Cheslek <echeslak@us.ibm.com> - ==
root@uu04g1:~# multipath -ll
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:1:0 sdb 8:16 active ready running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:2:0 sdc 8:32 active ready running
root@uu04g1:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 20G 0 disk
??sda1 8:1 0 7M 0 part
??sda2 8:2 0 19.1G 0 part /
??sda3 8:3 0 896M 0 part [SWAP]
sdb 8:16 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-1-0
252:0 0 20G 0 mpath
sdc 8:32 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-2-0
252:1 0 20G 0 mpath
root@uu04g1:~#
root@uu04g1:~# lsscsi
[0:0:0:0] disk QEMU QEMU HARDDISK 2.0. /dev/sda
[0:0:1:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdb
[0:0:2:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdc
== Comment: #2 - Edward R. Cheslek <echeslak@us.ibm.com> - 2014-10-08 22:27:09 ==
This is the xml file of the affected guest. Please note that all disks are file backed.
root@uu04g1:~# multipath -l
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:1:0 sdb 8:16 active undef running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:2:0 sdc 8:32 active undef running
root@uu04g1:~# multipath -v2
root@uu04g1:~# |
[Impact]
Users of multipath-tools on systems which exhibit both multipathed and non-multipathed drives or some USB devices (some USB devices may still be picked up by multipath-tools if multipath-capable).
[Test case]
- Boot on a system with multipathed disks with the previous version of multipath-tools
- Upgrade to the new version; verify that /etc/multipath/wwids is created and contains all the right device WWIDs, and that 'sudo multipath -ll' has the same devices.
- Reboot and verify that the system still boots correctly.
- Using Fibre-Channel hardware: verify that multipath still behaves correctly for path degradation scenarios (see below).
After rebooting, you should verify that /proc/mounts correctly lists the multipath device (/dev/mapper/*), and that /proc/swaps also lists any swap partitions that should be on a multipathed disk as a /dev/dm-* device.
PATH DEGRADATION:
-- This test requires fibre-channel hardware or another method to be able to disconnect paths to a drive.
1) verify that on disconnecting a path, it is properly detected as being in degraded mode by multipath-tools; and shows as such in 'multipath -ll'.
2) verify that on reconnection, the path shows up again as ready or OK in 'multipath -ll'.
[Regression potential]
Systems in complex setups mixing both multipathed and non-multipathed disks, or with particularly slow disk controllers may fail to boot or show delays in booting. Systems requiring a particular set of partitions to be available in early boot (past the typical installs on /, some may require /usr to be available for some daemons to load on boot) could fail to properly start up all the software on boot; these should be considered as regressions only if devices do not properly show up in 'sudo multipath -ll' output.
Users seeing issues should preferrably include the output of 'sudo multipath -v4' to bug reports to help developers in debugging.
---
Problem Description
======================
non-multpath disks are classified as multipath after the multipath-tools package is installed.
---uname output---
Linux uu04g1 3.16.0-21-generic #28-Ubuntu SMP Mon Oct 6 15:57:32 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Tuleta pKVM guest
Steps to Reproduce
=========================
1) Create a guest with an unused, non-mpath disk (not the install disk) (a qemu img file is fine).
2) apt-get install multipath-tools.
3) multipath -ll.
4) Note that your file backed disks are showing up as mpath disks.
Userspace tool common name: multipath
The userspace tool has the following bit modes: 64
System Dump Info:
The system is not configured to capture a system dump.
Userspace rpm: multipath-tools
Userspace tool obtained from project website: multipath-tools v0.4.9 (05/33, 2016)
== Comment: #1 - Edward R. Cheslek <echeslak@us.ibm.com> - ==
root@uu04g1:~# multipath -ll
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:1:0 sdb 8:16 active ready running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:2:0 sdc 8:32 active ready running
root@uu04g1:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 20G 0 disk
??sda1 8:1 0 7M 0 part
??sda2 8:2 0 19.1G 0 part /
??sda3 8:3 0 896M 0 part [SWAP]
sdb 8:16 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-1-0
252:0 0 20G 0 mpath
sdc 8:32 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-2-0
252:1 0 20G 0 mpath
root@uu04g1:~#
root@uu04g1:~# lsscsi
[0:0:0:0] disk QEMU QEMU HARDDISK 2.0. /dev/sda
[0:0:1:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdb
[0:0:2:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdc
== Comment: #2 - Edward R. Cheslek <echeslak@us.ibm.com> - 2014-10-08 22:27:09 ==
This is the xml file of the affected guest. Please note that all disks are file backed.
root@uu04g1:~# multipath -l
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:1:0 sdb 8:16 active undef running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:2:0 sdc 8:32 active undef running
root@uu04g1:~# multipath -v2
root@uu04g1:~# |
|
| 2015-08-18 08:40:40 |
Mathieu Trudel-Lapierre |
description |
[Impact]
Users of multipath-tools on systems which exhibit both multipathed and non-multipathed drives or some USB devices (some USB devices may still be picked up by multipath-tools if multipath-capable).
[Test case]
- Boot on a system with multipathed disks with the previous version of multipath-tools
- Upgrade to the new version; verify that /etc/multipath/wwids is created and contains all the right device WWIDs, and that 'sudo multipath -ll' has the same devices.
- Reboot and verify that the system still boots correctly.
- Using Fibre-Channel hardware: verify that multipath still behaves correctly for path degradation scenarios (see below).
After rebooting, you should verify that /proc/mounts correctly lists the multipath device (/dev/mapper/*), and that /proc/swaps also lists any swap partitions that should be on a multipathed disk as a /dev/dm-* device.
PATH DEGRADATION:
-- This test requires fibre-channel hardware or another method to be able to disconnect paths to a drive.
1) verify that on disconnecting a path, it is properly detected as being in degraded mode by multipath-tools; and shows as such in 'multipath -ll'.
2) verify that on reconnection, the path shows up again as ready or OK in 'multipath -ll'.
[Regression potential]
Systems in complex setups mixing both multipathed and non-multipathed disks, or with particularly slow disk controllers may fail to boot or show delays in booting. Systems requiring a particular set of partitions to be available in early boot (past the typical installs on /, some may require /usr to be available for some daemons to load on boot) could fail to properly start up all the software on boot; these should be considered as regressions only if devices do not properly show up in 'sudo multipath -ll' output.
Users seeing issues should preferrably include the output of 'sudo multipath -v4' to bug reports to help developers in debugging.
---
Problem Description
======================
non-multpath disks are classified as multipath after the multipath-tools package is installed.
---uname output---
Linux uu04g1 3.16.0-21-generic #28-Ubuntu SMP Mon Oct 6 15:57:32 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Tuleta pKVM guest
Steps to Reproduce
=========================
1) Create a guest with an unused, non-mpath disk (not the install disk) (a qemu img file is fine).
2) apt-get install multipath-tools.
3) multipath -ll.
4) Note that your file backed disks are showing up as mpath disks.
Userspace tool common name: multipath
The userspace tool has the following bit modes: 64
System Dump Info:
The system is not configured to capture a system dump.
Userspace rpm: multipath-tools
Userspace tool obtained from project website: multipath-tools v0.4.9 (05/33, 2016)
== Comment: #1 - Edward R. Cheslek <echeslak@us.ibm.com> - ==
root@uu04g1:~# multipath -ll
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:1:0 sdb 8:16 active ready running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:2:0 sdc 8:32 active ready running
root@uu04g1:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 20G 0 disk
??sda1 8:1 0 7M 0 part
??sda2 8:2 0 19.1G 0 part /
??sda3 8:3 0 896M 0 part [SWAP]
sdb 8:16 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-1-0
252:0 0 20G 0 mpath
sdc 8:32 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-2-0
252:1 0 20G 0 mpath
root@uu04g1:~#
root@uu04g1:~# lsscsi
[0:0:0:0] disk QEMU QEMU HARDDISK 2.0. /dev/sda
[0:0:1:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdb
[0:0:2:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdc
== Comment: #2 - Edward R. Cheslek <echeslak@us.ibm.com> - 2014-10-08 22:27:09 ==
This is the xml file of the affected guest. Please note that all disks are file backed.
root@uu04g1:~# multipath -l
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:1:0 sdb 8:16 active undef running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:2:0 sdc 8:32 active undef running
root@uu04g1:~# multipath -v2
root@uu04g1:~# |
[Impact]
Users of multipath-tools on systems which exhibit both multipathed and non-multipathed drives or some USB devices (some USB devices may still be picked up by multipath-tools if multipath-capable).
[Test case]
- Boot on a system with multipathed disks with the previous version of multipath-tools
- Upgrade to the new version; verify that /etc/multipath/wwids is created and contains all the right device WWIDs, and that 'sudo multipath -ll' has the same devices.
- Reboot and verify that the system still boots correctly.
- [udev] Using Fibre-Channel hardware: verify that multipath still behaves correctly for path degradation scenarios (see below).
After rebooting, you should verify that /proc/mounts correctly lists the multipath device (/dev/mapper/*), and that /proc/swaps also lists any swap partitions that should be on a multipathed disk as a /dev/dm-* device.
PATH DEGRADATION:
-- This test requires fibre-channel hardware or another method to be able to disconnect paths to a drive.
1) verify that on disconnecting a path, it is properly detected as being in degraded mode by multipath-tools; and shows as such in 'multipath -ll'.
2) verify that on reconnection, the path shows up again as ready or OK in 'multipath -ll'.
[Regression potential]
Systems in complex setups mixing both multipathed and non-multipathed disks, or with particularly slow disk controllers may fail to boot or show delays in booting. Systems requiring a particular set of partitions to be available in early boot (past the typical installs on /, some may require /usr to be available for some daemons to load on boot) could fail to properly start up all the software on boot; these should be considered as regressions only if devices do not properly show up in 'sudo multipath -ll' output.
Users seeing issues should preferrably include the output of 'sudo multipath -v4' to bug reports to help developers in debugging.
---
Problem Description
======================
non-multpath disks are classified as multipath after the multipath-tools package is installed.
---uname output---
Linux uu04g1 3.16.0-21-generic #28-Ubuntu SMP Mon Oct 6 15:57:32 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Tuleta pKVM guest
Steps to Reproduce
=========================
1) Create a guest with an unused, non-mpath disk (not the install disk) (a qemu img file is fine).
2) apt-get install multipath-tools.
3) multipath -ll.
4) Note that your file backed disks are showing up as mpath disks.
Userspace tool common name: multipath
The userspace tool has the following bit modes: 64
System Dump Info:
The system is not configured to capture a system dump.
Userspace rpm: multipath-tools
Userspace tool obtained from project website: multipath-tools v0.4.9 (05/33, 2016)
== Comment: #1 - Edward R. Cheslek <echeslak@us.ibm.com> - ==
root@uu04g1:~# multipath -ll
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:1:0 sdb 8:16 active ready running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:2:0 sdc 8:32 active ready running
root@uu04g1:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 20G 0 disk
??sda1 8:1 0 7M 0 part
??sda2 8:2 0 19.1G 0 part /
??sda3 8:3 0 896M 0 part [SWAP]
sdb 8:16 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-1-0
252:0 0 20G 0 mpath
sdc 8:32 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-2-0
252:1 0 20G 0 mpath
root@uu04g1:~#
root@uu04g1:~# lsscsi
[0:0:0:0] disk QEMU QEMU HARDDISK 2.0. /dev/sda
[0:0:1:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdb
[0:0:2:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdc
== Comment: #2 - Edward R. Cheslek <echeslak@us.ibm.com> - 2014-10-08 22:27:09 ==
This is the xml file of the affected guest. Please note that all disks are file backed.
root@uu04g1:~# multipath -l
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:1:0 sdb 8:16 active undef running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:2:0 sdc 8:32 active undef running
root@uu04g1:~# multipath -v2
root@uu04g1:~# |
|
| 2015-08-18 08:43:41 |
Mathieu Trudel-Lapierre |
description |
[Impact]
Users of multipath-tools on systems which exhibit both multipathed and non-multipathed drives or some USB devices (some USB devices may still be picked up by multipath-tools if multipath-capable).
[Test case]
- Boot on a system with multipathed disks with the previous version of multipath-tools
- Upgrade to the new version; verify that /etc/multipath/wwids is created and contains all the right device WWIDs, and that 'sudo multipath -ll' has the same devices.
- Reboot and verify that the system still boots correctly.
- [udev] Using Fibre-Channel hardware: verify that multipath still behaves correctly for path degradation scenarios (see below).
After rebooting, you should verify that /proc/mounts correctly lists the multipath device (/dev/mapper/*), and that /proc/swaps also lists any swap partitions that should be on a multipathed disk as a /dev/dm-* device.
PATH DEGRADATION:
-- This test requires fibre-channel hardware or another method to be able to disconnect paths to a drive.
1) verify that on disconnecting a path, it is properly detected as being in degraded mode by multipath-tools; and shows as such in 'multipath -ll'.
2) verify that on reconnection, the path shows up again as ready or OK in 'multipath -ll'.
[Regression potential]
Systems in complex setups mixing both multipathed and non-multipathed disks, or with particularly slow disk controllers may fail to boot or show delays in booting. Systems requiring a particular set of partitions to be available in early boot (past the typical installs on /, some may require /usr to be available for some daemons to load on boot) could fail to properly start up all the software on boot; these should be considered as regressions only if devices do not properly show up in 'sudo multipath -ll' output.
Users seeing issues should preferrably include the output of 'sudo multipath -v4' to bug reports to help developers in debugging.
---
Problem Description
======================
non-multpath disks are classified as multipath after the multipath-tools package is installed.
---uname output---
Linux uu04g1 3.16.0-21-generic #28-Ubuntu SMP Mon Oct 6 15:57:32 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Tuleta pKVM guest
Steps to Reproduce
=========================
1) Create a guest with an unused, non-mpath disk (not the install disk) (a qemu img file is fine).
2) apt-get install multipath-tools.
3) multipath -ll.
4) Note that your file backed disks are showing up as mpath disks.
Userspace tool common name: multipath
The userspace tool has the following bit modes: 64
System Dump Info:
The system is not configured to capture a system dump.
Userspace rpm: multipath-tools
Userspace tool obtained from project website: multipath-tools v0.4.9 (05/33, 2016)
== Comment: #1 - Edward R. Cheslek <echeslak@us.ibm.com> - ==
root@uu04g1:~# multipath -ll
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:1:0 sdb 8:16 active ready running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:2:0 sdc 8:32 active ready running
root@uu04g1:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 20G 0 disk
??sda1 8:1 0 7M 0 part
??sda2 8:2 0 19.1G 0 part /
??sda3 8:3 0 896M 0 part [SWAP]
sdb 8:16 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-1-0
252:0 0 20G 0 mpath
sdc 8:32 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-2-0
252:1 0 20G 0 mpath
root@uu04g1:~#
root@uu04g1:~# lsscsi
[0:0:0:0] disk QEMU QEMU HARDDISK 2.0. /dev/sda
[0:0:1:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdb
[0:0:2:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdc
== Comment: #2 - Edward R. Cheslek <echeslak@us.ibm.com> - 2014-10-08 22:27:09 ==
This is the xml file of the affected guest. Please note that all disks are file backed.
root@uu04g1:~# multipath -l
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:1:0 sdb 8:16 active undef running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:2:0 sdc 8:32 active undef running
root@uu04g1:~# multipath -v2
root@uu04g1:~# |
[Impact]
Users of multipath-tools on systems which exhibit both multipathed and non-multipathed drives or some USB devices (some USB devices may still be picked up by multipath-tools if multipath-capable).
[Test case]
- Boot on a system with multipathed disks with the previous version of multipath-tools
- Upgrade to the new version; verify that /etc/multipath/wwids is created and contains all the right device WWIDs, and that 'sudo multipath -ll' has the same devices.
- Reboot and verify that the system still boots correctly.
- [udev] Using Fibre-Channel hardware: verify that multipath still behaves correctly for path degradation scenarios (see below).
After rebooting, you should verify that /proc/mounts correctly lists the multipath device (/dev/mapper/*), and that /proc/swaps also lists any swap partitions that should be on a multipathed disk as a /dev/dm-* device.
PATH DEGRADATION:
-- This test requires fibre-channel hardware or another method to be able to disconnect paths to a drive.
1) verify that on disconnecting a path, it is properly detected as being in degraded mode by multipath-tools; and shows as such in 'multipath -ll'.
2) verify that on reconnection, the path shows up again as ready or OK in 'multipath -ll'.
[Regression potential]
Systems in complex setups mixing both multipathed and non-multipathed disks, or with particularly slow disk controllers may fail to boot or show delays in booting. Systems requiring a particular set of partitions to be available in early boot (past the typical installs on /, some may require /usr to be available for some daemons to load on boot) could fail to properly start up all the software on boot; these should be considered as regressions only if devices do not properly show up in 'sudo multipath -ll' output.
Users seeing issues should preferrably include the output of 'sudo multipath -v4' to bug reports to help developers in debugging.
Udev rules have been changed in this case, because they interfere with the proper behavior of multipath 0.4.9 with the patches included as backported from 0.5.0; this has the potential to strongly impact the detection of change events on multipath devices; if path degradation or new device detection fails, this should be considered an important regression of multipath-tools.
---
Problem Description
======================
non-multpath disks are classified as multipath after the multipath-tools package is installed.
---uname output---
Linux uu04g1 3.16.0-21-generic #28-Ubuntu SMP Mon Oct 6 15:57:32 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Tuleta pKVM guest
Steps to Reproduce
=========================
1) Create a guest with an unused, non-mpath disk (not the install disk) (a qemu img file is fine).
2) apt-get install multipath-tools.
3) multipath -ll.
4) Note that your file backed disks are showing up as mpath disks.
Userspace tool common name: multipath
The userspace tool has the following bit modes: 64
System Dump Info:
The system is not configured to capture a system dump.
Userspace rpm: multipath-tools
Userspace tool obtained from project website: multipath-tools v0.4.9 (05/33, 2016)
== Comment: #1 - Edward R. Cheslek <echeslak@us.ibm.com> - ==
root@uu04g1:~# multipath -ll
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:1:0 sdb 8:16 active ready running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 0:0:2:0 sdc 8:32 active ready running
root@uu04g1:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 20G 0 disk
??sda1 8:1 0 7M 0 part
??sda2 8:2 0 19.1G 0 part /
??sda3 8:3 0 896M 0 part [SWAP]
sdb 8:16 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-1-0
252:0 0 20G 0 mpath
sdc 8:32 0 20G 0 disk
??0QEMU\x20\x20\x20\x20QEMU\x20HARDDISK\x20\x20\x20drive-scsi0-0-2-0
252:1 0 20G 0 mpath
root@uu04g1:~#
root@uu04g1:~# lsscsi
[0:0:0:0] disk QEMU QEMU HARDDISK 2.0. /dev/sda
[0:0:1:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdb
[0:0:2:0] disk QEMU QEMU HARDDISK 2.0. /dev/sdc
== Comment: #2 - Edward R. Cheslek <echeslak@us.ibm.com> - 2014-10-08 22:27:09 ==
This is the xml file of the affected guest. Please note that all disks are file backed.
root@uu04g1:~# multipath -l
0QEMU QEMU HARDDISK drive-scsi0-0-1-0 dm-0 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:1:0 sdb 8:16 active undef running
0QEMU QEMU HARDDISK drive-scsi0-0-2-0 dm-1 QEMU,QEMU HARDDISK
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 0:0:2:0 sdc 8:32 active undef running
root@uu04g1:~# multipath -v2
root@uu04g1:~# |
|
| 2015-08-18 18:27:26 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-08-18 18:27:32 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2015-08-18 18:27:42 |
Steve Langasek |
tags |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- verification-needed |
|
| 2015-08-19 14:20:07 |
Mathew Hodson |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-08-19 14:21:08 |
Mathew Hodson |
multipath-tools (Ubuntu): importance |
Undecided |
Medium |
|
| 2015-08-19 14:27:51 |
Mathew Hodson |
multipath-tools (Ubuntu): importance |
Medium |
High |
|
| 2015-08-19 14:37:16 |
Mathew Hodson |
multipath-tools (Ubuntu): status |
New |
Triaged |
|
| 2015-08-25 16:24:50 |
Steve Langasek |
bug task added |
|
multipath-tools (Ubuntu Trusty) |
|
| 2015-08-25 16:24:58 |
Steve Langasek |
multipath-tools (Ubuntu Trusty): status |
New |
Fix Committed |
|
| 2015-08-25 16:25:41 |
Steve Langasek |
multipath-tools (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2015-08-25 16:25:50 |
Mathieu Trudel-Lapierre |
multipath-tools (Ubuntu): status |
Triaged |
Fix Released |
|
| 2015-08-25 16:47:55 |
brandyseres256@gmail.com |
multipath-tools (Ubuntu): assignee |
|
brandyseres256@gmail.com (brandyseres256) |
|
| 2015-08-26 02:02:06 |
Mathieu Trudel-Lapierre |
multipath-tools (Ubuntu): assignee |
brandyseres256@gmail.com (brandyseres256) |
|
|
| 2015-08-30 20:12:06 |
Mathew Hodson |
multipath-tools (Ubuntu Trusty): milestone |
|
trusty-updates |
|
| 2015-09-22 12:20:12 |
Mauricio Faria de Oliveira |
tags |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- verification-needed |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- verification-failed |
|
| 2015-09-22 12:22:26 |
Mauricio Faria de Oliveira |
bug |
|
|
added subscriber Mauricio Faria de Oliveira |
| 2015-10-08 22:43:35 |
Brian Murray |
tags |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- verification-failed |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- |
|
| 2015-10-08 22:43:36 |
Brian Murray |
tags |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- verification-needed |
|
| 2015-10-22 15:31:16 |
Steve Langasek |
bug |
|
|
added subscriber Steve Langasek |
| 2015-10-29 16:30:20 |
bugproxy |
attachment added |
|
xml file of the guest https://bugs.launchpad.net/bugs/1386637/+attachment/4508591/+files/uu04g1.xml |
|
| 2015-11-20 16:31:26 |
Mathieu Trudel-Lapierre |
tags |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- verification-needed |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- verification-done |
|
| 2015-11-24 18:44:17 |
Launchpad Janitor |
multipath-tools (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2015-11-24 18:44:24 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2015-12-01 16:56:37 |
Mathieu Trudel-Lapierre |
nominated for series |
|
Ubuntu Vivid |
|
| 2015-12-01 16:56:37 |
Mathieu Trudel-Lapierre |
bug task added |
|
multipath-tools (Ubuntu Vivid) |
|
| 2015-12-01 16:56:45 |
Mathieu Trudel-Lapierre |
multipath-tools (Ubuntu Vivid): status |
New |
In Progress |
|
| 2015-12-01 16:56:47 |
Mathieu Trudel-Lapierre |
multipath-tools (Ubuntu Vivid): importance |
Undecided |
High |
|
| 2015-12-01 16:57:08 |
Mathieu Trudel-Lapierre |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-12-03 20:22:21 |
Brian Murray |
multipath-tools (Ubuntu Vivid): status |
In Progress |
Fix Committed |
|
| 2015-12-03 20:22:29 |
Brian Murray |
tags |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- verification-done |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- |
|
| 2015-12-03 20:22:30 |
Brian Murray |
tags |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- verification-needed |
|
| 2016-03-04 20:30:56 |
Ubuntu Foundations Team Bug Bot |
tags |
architecture-ppc64le bot-comment bugnameltc-117319 severity-high targetmilestone-inin--- verification-needed |
architecture-ppc64le bot-comment bugnameltc-117319 removal-candidate severity-high targetmilestone-inin--- verification-needed |
|
| 2016-05-12 13:50:46 |
Martin Pitt |
multipath-tools (Ubuntu Vivid): status |
Fix Committed |
Won't Fix |
|
| 2016-05-12 13:50:49 |
Martin Pitt |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-05-12 13:50:50 |
Martin Pitt |
removed subscriber SRU Verification |
|
|
|
| 2016-05-12 13:50:51 |
Martin Pitt |
tags |
architecture-ppc64le bot-comment bugnameltc-117319 removal-candidate severity-high targetmilestone-inin--- verification-needed |
architecture-ppc64le bot-comment bugnameltc-117319 removal-candidate severity-high targetmilestone-inin--- |
|
