cinder volume on RBD not released after failure of zun

[Radosław Piliszek]

Make zun-compute succeed to mount RBD but fail to prepare the fs (e.g. by missing the tools).
The container will fail to start. Removing it forcibly does not release the volume and it is stuck in the following state (zun-test):

+--------------------------------------+----------+--------+------+----------------------------------------------------------------------------------------------------------------------+
| ID | Name | Status | Size | Attached to |
+--------------------------------------+----------+--------+------+----------------------------------------------------------------------------------------------------------------------+
| a72fbec8-899d-4491-a1a6-c27ca249c173 | zun-test | in-use | 1 | Attached to 588a2f81-4188-48f7-8c74-128b7f36897c on /dev/rbd/os-volumes/volume-a72fbec8-899d-4491-a1a6-c27ca249c173 |
| 9e90fa84-935d-4f87-927c-ea8e5ac52097 | | in-use | 1 | Attached to B on /dev/vda |
| 59229cd7-90e5-4871-a94c-9b9ed2b491fa | | in-use | 1 | Attached to A on /dev/vda |
+--------------------------------------+----------+--------+------+----------------------------------------------------------------------------------------------------------------------+

Horizon errors out on showing details or attachments.
I will try to debug it more later.

[Radosław Piliszek (yoctozepto)]

Side bug: cinder has no idea that it's not an ID of instance but container.

[hongbin (hongbin034)]

Right,

I do know that Horizon assume Cinder volume always mounted to a VM, thus some links don't work in the UI. Using CLI or other SDK don't have such problem.

I will investigate the RBD problem.