In my understanding, the only way is to create a volume in advance and
then launch an instance with a precreated volume.

When considering how to fix it, we need to care whether cross AZ attach is 
allowed or not.
- In case of cross AZ attach is not allowed, a volume should be created with a 
same name as Nova AZ.
- In case of cross AZ attach is allowed, we need to provide a way to specify a 
volume AZ.


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

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).

  It is not possible to select AZ for new Cinder volume during the VM

Status in OpenStack Dashboard (Horizon):

Bug description:
  Steps To Reproduce:
  1. Deploy OpenStack cluster with several Nova availability zones, for 
example, 'nova1' and 'nova2' and with several Cinder availability zones, for 
example, 'storage1' and 'storage2' (availability zones for Nova and Cinder 
should be different).
  2. Login to Horizon dashboard and navigate to Project > Instances
  3. Click on 'Launch Instance' button
  4. Set all required parameters, select Nova AZ 'nova1' for new VM and select 
Instance Boot Source = "Boot from image (creates new volume)"
  5. Click on 'Launch' button

  Observed Result:
  Instance will fail with "Failure prepping block device" error (please see 
attached screenshot horizon_az_bug.png)

  Expected Result:
  As a user I expect that Horizon UI will provide me the ability to select the 
availability zone for new volume if I want to create new volume and boot VM 
from it. We can't use Nova AZ as availability zone for Cinder volume because 
these zones are different availability zones (we can have, for example, 1 Nova 
availability zones and many Cinder availability zone or one Cinder AZ and many 
Nova AZs - it depends on users needs).

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to