Hi Jonathan, Alan, Thanks for the replies. Yep those are what we tried Alan and also tried yours Jonathan, it showed it actually still had an attachment so I removed that and set it from state "reserved" to "available". We think we figured out after I sent the original mail that it's not an openstack issue, we have it backended on Quobyte and we can interact with all the other volumes there but not this particular one so we believe the issue is there. Thanks for the help anyway. Regards,Derek On Wednesday 30 March 2022, 23:52:30 IST, Alan Bishop abishop@redhat.com wrote:
On Wed, Mar 30, 2022 at 2:42 PM Jonathan Proulx jon@csail.mit.edu wrote:
On Wed, Mar 30, 2022 at 08:16:12AM +0000, Derek O keeffe wrote: :Hi all, :We are having an issue with a volume. The volume was created and attached to an instance that was then deleted. We now need to attach the volume to another instance to rescue the data on it but it still thinks it's attached to the deleted instance and we can't "manage attachments" or view the details of the volume.
When you say
:We have tried forcing it from the cli to detach but with no luck. We were thinking of doing it through the DB but said we'd askhere first in case anyone has experienced the same and has a better way of approaching the issue. Thanks in advance.
is this what you tried?
cinder reset-state --attach-status detached <UUID>
Assuming your cloud is based on Queens or later, these commands may also help: cinder --os-volume-api-version 3.44 attachment-listcinder --os-volume-api-version 3.44 attachment-delete <attachment ID> Alan
I've had the stale attachement problem a number of times and that one's always worked for me so here's hoping it's not what you tried...
-Jon