yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #58394
[Bug 1639350] Re: Use of CONF.libvirt.volume_use_multipath should not be mandatory
My bad on this; the actual problem is an unhandled failure/crash if
multipath-d isn't installed/running.
** Changed in: os-brick
Status: New => Opinion
** Changed in: os-brick
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1639350
Title:
Use of CONF.libvirt.volume_use_multipath should not be mandatory
Status in OpenStack Compute (nova):
Opinion
Status in os-brick:
Opinion
Bug description:
Currently if iscsi_multipath is set in nova.conf we require ALL
attachments to use multipath. The problem with this is that it's not
uncommon to have a mix of Cinder backends; one that supports multipath
and one that doesn't. The result with how we do this now is that you
can have only one or the other but not both.
We should be able to revert to single-path when multipath doesn't work
for the volume; also might be worth considering if the multipath
support should just be embedded as part of the volume object and skip
the need to configure it in Nova at all.
To reproduce, set up a default devstack with LIO and LVM; set
nova.conf iscsi_multipath=True, restart nova.
Create a volume, create an instance, try and attach the volume to the
instance.
Example stack trace here:
http://paste.openstack.org/show/587939/
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1639350/+subscriptions
References