We’re still using Rancher 1.1.4, and are working on upgrading to Rancher 1.3.x (with Rancher-NFS) so this may not be a huge issue if it cannot be solved, or if it’s due to a known (and fixed) bug in 1.1.4.
We have a Convoy-NFS service and at some point, the convoy-nfs-storagepool service crashed (showed as 0 containers when looking at system stacks). We noticed this problem because creating a new volume got hung in the “activating” state. After restarting the convoy-nfs-storagepool service, the volume went from the “activating” state to “active”, but it does not have any API actions associated with it – the volume cannot be deleted or purged (which is what I need to do now).
How do I go about forcibly removing the volume? I presume that if the API won’t let me deactivate or delete the volume, that I’ll probably have to remove it directly from the MySQL database – that’s OK, I just need to know what row(s) need to be removed to make it go away.
The volume itself never actually initialized, so there’s no data at risk here. No containers ever actually used the volume. It’s just lingering in the volume list and I can’t get rid of the entry.