Booting instance from volume fails when nova AZ does not match available cinder AZ

Solution Verified - Updated -

Issue

What problem/issue/behavior are you having trouble with? What do you expect to see?

We'd like to introduce the AZ architecture first:

  • There are several nova Availability zones (3)
  • There is only 1 cinder availability zone (named nova, as the default)

When booting an instance from volume in the AZ1, a 400 error is returned by the cinder API even when the AZ filter has been removed from the scheduler.

Environment

  • Red Hat OpenStack Platform 7.0
  • openstack-nova < 2015.1.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content