Unable to detach existing and attached volume #610
Labels
Comments
|
I'm fairly certain this is related to #609 and its solution will be this issue's as well. |
|
@akutz as an update, that volume (which I could not remove) was created with an earlier version of rexray. So not sure if that is relevant. Though I was able to remove it with a direct curl call. |
|
@vladimirvivien The issue you're seeing is #609, not the version of RR that created the volume. But thanks for the info. More diag is almost never a bad thing. |
akutz
added a commit
to akutz/rexray
that referenced
this issue
Oct 31, 2016
This patch updates REX-Ray to request a volume's attachments if a CLI command is executed that depends upon a volume's status to determine its candidacy for said operation. For example, only "available" volumes (those not attached to another host) can be attached to a host. Only volumes that are "attached" can be detached. This patch handles issue 610 (rexray#610) and part of issue 609 (rexray#609).
|
Closed with #635. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This may be a bug in the libstorage client code.
I was unable to detach an existing volume that was attached using the virtualbox driver. In the end, I used direct
curlcommand to detach the volume. See this gist page for detail https://gist.github.com/vladimirvivien/3569c26754647eb977388f24a8bd7350.The text was updated successfully, but these errors were encountered: