Right, what Halverneus described is basically the only supported way to
get you back to something that works when you remove the storage pool
LXD is using from under it.
LXD assumes it's got control of any storage pool you provide it, we
don't support any kind of outside interference with it so I'm marking
this issue invalid as the only way to recover from this is to entirely
reset your LXD daemon.
** Changed in: lxd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579988
Title:
Image will not delete
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1579988/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
