yahoo-eng-team team mailing list archive

[Mitsuhiro Tanino <mitsuhiro.tanino@xxxxxxx>]

This is because Nova does not pass any volume type during volume
creation at "boot from image (Create new volume)". There is a proposal
to support volume type during "boot from image (Create new volume)" but
based on the comment on review 241065, this API will be removed in the
future. Therefore, the proposal was rejected.

- https://blueprints.launchpad.net/nova/+spec/enable-volume-types
- https://review.openstack.org/#/c/241065/

** Also affects: nova
   Importance: Undecided
       Status: New

** Changed in: cinder
       Status: New => Invalid

-- 
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 Cinder:
  Invalid
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/cinder/+bug/1523447/+subscriptions