The test wouldn't have failed if it were creating the attachment directly in Cinder and then deleting the attachment, even if it had the instance uuid, because Cinder would see that there is no nova instance or that the instance doesn't have the volume attached or that it's not using the attachment record.
Unfortunately we've found, looking at that tempest test, that there is yet another way to detach volumes in Cinder: using the "os-detach" volume action. So I need to update the cinder patch to also protect that endpoint.
We have also determined that Glance could expose the wrong image contents because it's not passing `force=True` on the os-brick `disconnect_volume`. This should be a small patch, and Brian will be working on it.
Quick update.
The test wouldn't have failed if it were creating the attachment directly in Cinder and then deleting the attachment, even if it had the instance uuid, because Cinder would see that there is no nova instance or that the instance doesn't have the volume attached or that it's not using the attachment record.
Unfortunately we've found, looking at that tempest test, that there is yet another way to detach volumes in Cinder: using the "os-detach" volume action. So I need to update the cinder patch to also protect that endpoint.
We have also determined that Glance could expose the wrong image contents because it's not passing `force=True` on the os-brick `disconnect_ volume` . This should be a small patch, and Brian will be working on it.