cinder cross_az_attach uses instance AZ value

[Roman Podoliaka]

Upstream bug https://bugs.launchpad.net/nova/+bug/1255347

Steps to reproduce:

Boot 2 VMs:

nova boot ac-instance --flavor micro --image 6.5.1-latest --nic net id=neid

nova boot ac2-instance --flavor micro --image 6.5.1-latest --nic net-id=netid --availability-zone=az1b

Create volume in the same az:

$ cinder create 100 --availability-zone az1b
Attach to the instance with scheduler-picked az

$ nova volume-attach ac-instance bfdaf9f5-1f4e-4d5f-89ca-26bc839cfb0f
ERROR (BadRequest): Invalid volume: Instance and volume not in same availability_zone (HTTP 400) (Request-ID: req-75fde250-c9d8-437d-bc64-2897d82f1ad4)
Attach to the instance with explicit az:
$ nova volume-attach ac2-instance bfdaf9f5-1f4e-4d5f-89ca-26bc839cfb0f
+----------+--------------------------------------+
| Property | Value |
+----------+--------------------------------------+
| device | /dev/vdb |
| id | bfdaf9f5-1f4e-4d5f-89ca-26bc839cfb0f |
| serverId | 3f9b4366-c17d-43c0-968e-6731dc6af851 |
| volumeId | bfdaf9f5-1f4e-4d5f-89ca-26bc839cfb0f |
+----------+--------------------------------------+

[Dmitry Mescheryakov (dmitrymex)]

Roman, please specify which version is affected. I guess it is 5.x only, right?

[Roman Podoliaka (rpodolyaka)]

Dmitry, done.

[Oleksii Aleksieiev (alexzzman)]

I have tested patch for icehouse proposed by Roman. It work properly.

I was able to attach volume to instance booted without AZ while still getting reject if i try to attach volume to host booted in another AZ.

[Alexander Gubanov (ogubanov)]

I have verified it on mos6.0 (build 56)
Proof: http://pastebin.com/cPKqx5XF

[Vitaly Sedelnik (vsedelnik)]

The issue was fixed for 6.0, this is feature request for 5.1.1 - Won't Fix in 5.1.1-updates