yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Comment #5 is exactly correct. You can't tell nova which cinder AZ to
create a volume in if nova is creating the volume. If you need a
specific AZ for the volume, you need to pre-create the volume in cinder
and then provide that volume to nova during the server create request.
It's the same issue with using a non-default volume type, you'd have to
pre-create a volume and provide it to nova in that case.

** Changed in: nova
       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/1485578

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

Status in OpenStack Dashboard (Horizon):
  Confirmed
Status in OpenStack Compute (nova):
  Invalid

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:
https://bugs.launchpad.net/horizon/+bug/1485578/+subscriptions