undeletable containers in "ERROR" state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxd (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Both on my amd64 laptop and on arm64 scalingstack instances I run into undeletable containers in error state over time:
$ lxc list
+------
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+------
| adt-virt-lxd-kntimp | ERROR | | | PERSISTENT | 0 |
+------
| adt-virt-lxd-rxwyjf | ERROR | | | PERSISTENT | 0 |
+------
$ lxc delete adt-virt-lxd-kntimp
error: couldn't detect filesystem for '/var/lib/
Indeed this directory does not exist any more, so it's gone from disk but still present in the database. It usually works to "sudo mkdir" this directory and "lxc delete" again.
I'll attach the corresponding /var/log/
I keep these two failed containers around for a while (i. e. don't do the mkdir/delete trick), in case you want to investigate anything on them.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lxd 2.0.0-0ubuntu4
ProcVersionSign
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: i3
Date: Thu Apr 28 09:24:33 2016
EcryptfsInUse: Yes
SourcePackage: lxd
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in lxd (Ubuntu): | |
importance: | Undecided → High |
Changed in lxd (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in lxd (Ubuntu): | |
status: | Fix Committed → Fix Released |
Not sure what's the source of the problem, but one thing we should do is allow for containers in such state to be removed.