Public bug reported:
Run a fresh xenial amd64 cloud image, install lxd, and then purge lxd or
just do "sudo systemctl stop lxd-containers". This hangs for a long time
on
root 2221 0.0 0.6 132820 13484 ? Ssl 11:02 0:00
/usr/bin/lxd shutdown
and eventually fails:
● lxd-containers.service - LXD - container startup/shutdown
Loaded: loaded (/lib/systemd/system/lxd-containers.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Tue 2016-04-05 11:03:07 UTC; 13s ago
Process: 2221 ExecStop=/usr/bin/lxd shutdown (code=exited, status=1/FAILURE)
Main PID: 1866 (code=exited, status=0/SUCCESS)
Apr 05 11:01:26 autopkgtest systemd[1]: Starting LXD - container
startup/shutdown...
Apr 05 11:01:26 autopkgtest systemd[1]: Started LXD - container
startup/shutdown.
Apr 05 11:02:07 autopkgtest systemd[1]: Stopping LXD - container
startup/shutdown...
Apr 05 11:03:07 autopkgtest lxd[2221]: error: LXD still running after 60s
timeout.
Apr 05 11:03:07 autopkgtest systemd[1]: lxd-containers.service: Control process
exited, code=exited status=1
Apr 05 11:03:07 autopkgtest systemd[1]: Stopped LXD - container
startup/shutdown.
Apr 05 11:03:07 autopkgtest systemd[1]: lxd-containers.service: Unit entered
failed state.
Apr 05 11:03:07 autopkgtest systemd[1]: lxd-containers.service: Failed with
result 'exit-code'.
Note that there are no running/defined containers there, "lxc list" is
empty.
This affects both 2.0.0~rc8-0ubuntu2 and the brand new
2.0.0~rc8-0ubuntu3 in xenial.
** Affects: lxd (Ubuntu)
Importance: Undecided
Status: New
** Tags: xenial
** Description changed:
Run a fresh xenial amd64 cloud image, install lxd, and then purge lxd or
just do "sudo systemctl stop lxd-containers". This hangs for a long time
on
root 2221 0.0 0.6 132820 13484 ? Ssl 11:02 0:00
/usr/bin/lxd shutdown
and eventually fails:
● lxd-containers.service - LXD - container startup/shutdown
- Loaded: loaded (/lib/systemd/system/lxd-containers.service; enabled;
vendor preset: enabled)
- Active: failed (Result: exit-code) since Tue 2016-04-05 11:03:07 UTC; 13s
ago
- Process: 2221 ExecStop=/usr/bin/lxd shutdown (code=exited, status=1/FAILURE)
- Main PID: 1866 (code=exited, status=0/SUCCESS)
+ Loaded: loaded (/lib/systemd/system/lxd-containers.service; enabled;
vendor preset: enabled)
+ Active: failed (Result: exit-code) since Tue 2016-04-05 11:03:07 UTC; 13s
ago
+ Process: 2221 ExecStop=/usr/bin/lxd shutdown (code=exited, status=1/FAILURE)
+ Main PID: 1866 (code=exited, status=0/SUCCESS)
Apr 05 11:01:26 autopkgtest systemd[1]: Starting LXD - container
startup/shutdown...
Apr 05 11:01:26 autopkgtest systemd[1]: Started LXD - container
startup/shutdown.
Apr 05 11:02:07 autopkgtest systemd[1]: Stopping LXD - container
startup/shutdown...
Apr 05 11:03:07 autopkgtest lxd[2221]: error: LXD still running after 60s
timeout.
Apr 05 11:03:07 autopkgtest systemd[1]: lxd-containers.service: Control
process exited, code=exited status=1
Apr 05 11:03:07 autopkgtest systemd[1]: Stopped LXD - container
startup/shutdown.
Apr 05 11:03:07 autopkgtest systemd[1]: lxd-containers.service: Unit entered
failed state.
Apr 05 11:03:07 autopkgtest systemd[1]: lxd-containers.service: Failed with
result 'exit-code'.
Note that there are no running/defined containers there, "lxc list" is
empty.
+
+ This affects both 2.0.0~rc8-0ubuntu2 and the brand new
+ 2.0.0~rc8-0ubuntu3 in xenial.
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566253
Title:
Stopping lxd-containers.service hangs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1566253/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
