Cannot attach volume to instance in a different AZ

[bertinatto]

PR #42
changed the CreateDisk behaviour by creating a volume in a random AZ
if such isn't provided. However, the volume might be created in an AZ where there's no driver
running.

This is the error that I'm getting:

Warning  FailedAttachVolume  84s  attachdetach-controller  (combined from similar events): AttachVolume.Attach failed for volume "pvc-44c2c835-cc91-11e8-93bb-0e3fe2b5fad4" : rpc error: code = Internal desc = Could not attach volume "vol-06899fef1736f24b9" to node "i-0a7e7ab68218ef0e0": could not attach volume "vol-06899fef1736f24b9" to node "i-0a7e7ab68218ef0e0": InvalidVolume.ZoneMismatch: The volume 'vol-06899fef1736f24b9' is not in the same availability zone as instance 'i-0a7e7ab68218ef0e0'

[bertinatto]

/kind bug

[leakingtapan]

@bertinatto this issue could be resolved, right?

[bertinatto]

/close

[k8s-ci-robot]

@bertinatto: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.