Tempest Tests with multilpe Availability Zones

Bug #1647999 reported by Daniel Haupt on 2016-12-07
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Takashi Kajinami

Bug Description

We have different Availability Zones configured and also set "cross_az_attach = false" in nova.conf.
For following tempest tests, we got the error message, that the Instance and Volume are in different AZ (mounting is of course forbidden). So the tests are failing.

Details: {u'message': u'Invalid volume: Instance 1234 and volume 4567 are not in the same availability_zone. Instance is in "AZ1". Volume is in "AZ2"', u'code': 400}

Tempest Tests:

To make the tests work again, it would be good to have a new param in tempest.conf to specify the AZ for the Instances and Volumes.

Marc Koderer (m-koderer) on 2016-12-07
Changed in tempest:
assignee: nobody → Marc Koderer (m-koderer)
importance: Undecided → Low
status: New → Confirmed
Ghanshyam Mann (ghanshyammann) wrote :

Nice bug, we actually did not care about cross_az_attach in tempest.

Almost all tests goes with default AZ which is same on nova and cinder side. So we actually never tested the cross AZ things.

may be we can add "cross_az_attach" in tempest conf and test can pass diff AZ if true otherwise same.
This way we can actually tests cross AZ things in our tests.

Fix proposed to branch: master
Review: https://review.openstack.org/408498

Changed in tempest:
status: Confirmed → In Progress
Changed in tempest:
assignee: Marc Koderer (m-koderer) → Takashi Kajinami (kajinamit)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers