yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1523447] Re: When multiple cinder backend enabled , Cinder picks up first enabled backend during boot from image(create new volume)

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: deepali verneya <deepali.verneya@xxxxxx>
Date: Tue, 08 Dec 2015 06:44:28 -0000
Reply-to: Bug 1523447 <1523447@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** No longer affects: cinder

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

Title:
  When multiple cinder backend enabled ,Cinder picks up first enabled
  backend during  boot from image(create new volume)

Status in OpenStack Compute (nova):
  New

Bug description:
  Steps to reproduce-

  	1- Enable Cinder Block storage driver .For example - HPE 3PAR FC/iSCSI or HPE Lefthand .
  	2- Enable another Cinder Block storage driver . Eg VMWARE VMFS driver.
  	3-  Try to launch an instance by selecting option "boot from image (Create new volume)" using image <image-name>.VMDK

  Actual Behaviour  -

   Cinder uses the volume type info to associate the request during the
  create volume call. However in this case it goes with the default
  volume host, that would be the first one in the enabled backend as
  there is no way to specify volume type  during this operation.

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