← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2015894] [NEW] VMs failing to go up with RBD volume + volume_use_multipath

 

Public bug reported:

For a VM that's using an RBD volume when `volume_use_multipath` is set
to true, VMs will fail to go up.

https://github.com/openstack/os-
brick/blob/28ffcdbfa138859859beca2f80627c076269be56/os_brick/initiator/linuxscsi.py#L212-L233

It seems like we always call os_brick with enforce_multipath=True, so if
that is set to enabled, it ends up failing for all newly provisioned
VMs, even if multipath is not in use/necessary.

Ideally, we should be able to safely ignore it if we're trying to plug a
backend that doesn't use/support multipath..

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/2015894

Title:
  VMs failing to go up with RBD volume + volume_use_multipath

Status in OpenStack Compute (nova):
  New

Bug description:
  For a VM that's using an RBD volume when `volume_use_multipath` is set
  to true, VMs will fail to go up.

  https://github.com/openstack/os-
  brick/blob/28ffcdbfa138859859beca2f80627c076269be56/os_brick/initiator/linuxscsi.py#L212-L233

  It seems like we always call os_brick with enforce_multipath=True, so
  if that is set to enabled, it ends up failing for all newly
  provisioned VMs, even if multipath is not in use/necessary.

  Ideally, we should be able to safely ignore it if we're trying to plug
  a backend that doesn't use/support multipath..

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2015894/+subscriptions



Follow ups