Cannot recognize warning message from "multipath -l" command

Bug #1433204 reported by Tomoki Sekiyama
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Low
Sylvain Bauza

Bug Description

If iscsi_use_multipath=True is specified in nova.conf, a volume is attached to instances using "multipath -l" or "multipath -ll" command in order to find the multipath device. However, in some configuration, "multipath -l" command may report an error like below:

 # multipath -l
 Mar 17 12:31:18 | sda: No fc_host device for 'host-1'
 mpathb (360000000000000000e00000000010001) dm-4 IET ,VIRTUAL-DISK
 size=1.0G features='0' hwhandler='0' wp=rw
 |-+- policy='service-time 0' prio=0 status=active
 | `- 2:0:0:1 sda 8:0 active undef running
 `-+- policy='service-time 0' prio=0 status=enabled
   `- 3:0:0:1 sdb 8:16 active undef running

Current multipath parser implementation in Nova cannot recognize this warning message and regards "Mar" a valid multipath device name. As a result, the volume cannot be attached to instances correctly.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/165560

Changed in nova:
assignee: nobody → Tomoki Sekiyama (tsekiyama)
status: New → In Progress
Changed in nova:
importance: Undecided → Low
Changed in nova:
assignee: Tomoki Sekiyama (tsekiyama) → Sylvain Bauza (sylvain-bauza)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by Tomoki Sekiyama (<email address hidden>) on branch: master
Review: https://review.openstack.org/165560
Reason: This bug is fixed by moving to os-brick.

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → liberty-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: liberty-3 → 12.0.0
Revision history for this message
Bjoern (bjoern-t) wrote :

This is still an issue in kilo where libvirt uses the wrong name to construct the libvirt name :

# multipath -ll /dev/sdar
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
Dec 04 15:30:26 | io_setup failed
3514f0c55ab400004 dm-9 XtremIO ,XtremApp
size=1.7T features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 18:0:0:3 sdaw 67:0 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 19:0:0:3 sdaq 66:160 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 20:0:0:3 sdas 66:192 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 21:0:0:3 sdar 66:176 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 22:0:0:3 sdat 66:208 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 23:0:0:3 sdax 67:16 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 24:0:0:3 sdav 66:240 active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
  `- 25:0:0:3 sdau 66:224 active ready running

Target Source
------------------------------------------------
vda vms/35bb0716-f0d7-4446-93a6-83cbbfd27dd9_disk
vdb /dev/mapper/Dec
vdc /dev/mapper/Dec
vdd /dev/mapper/Dec
vde /dev/mapper/Dec
hdd /var/lib/nova/instances/35bb0716-f0d7-4446-93a6-83cbbfd27dd9/disk.config

As a result the instance can not be started nor can volumes attached of detached

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/kilo)

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/258191

Revision history for this message
Bjoern (bjoern-t) wrote :

I'm proposing a back port from os-brick to fix this issue for kilo. I currently have an environment which is affected by this issue. Liberty is currently too far away from us to be even considered and I like to stabilize the kilo branch as long as possible.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (stable/kilo)

Change abandoned by Dave Walker (<email address hidden>) on branch: stable/kilo
Review: https://review.openstack.org/258191
Reason: Kilo is now approaching EOL. We are in freeze pending the final release and no freeze exception has been raised. Therefore I am abandoning this change, if it is required in the release - please restore and raise a request. Thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.