touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #33403
[Bug 1384751] Re: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc-restore-net: not found
Hello Tycho, or anyone else affected,
Accepted lxc into utopic-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/lxc/1.1.0~alpha2-0ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: lxc (Ubuntu Utopic)
Status: Triaged => Fix Committed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1384751
Title:
checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc-
restore-net: not found
Status in “lxc” package in Ubuntu:
Fix Released
Status in “lxc” source package in Utopic:
Fix Committed
Status in “lxc” source package in Vivid:
Fix Released
Bug description:
================================================================
Impact: restoring containers from a checkpoint doesn't work
Development fix: LXC uses /usr/lib/x86_64-linux-gnu/lxc as the path to moun the container's root filesystem in its private mount namespace before it pivot_roots during restore. Unfortunately, that's also the location of the lxc-restore-net script which criu tries to execute. Since at this point the container's fs has already been mounted there, the callback (and thus the restore) fails.
Stable fix: Same as development fix
Testcase: create a container, then do:
sudo lxc-checkpoint -n $foo -s -D /tmp/checkpoint
sudo lxc-checkpoint -r -n $foo -D /tmp/checkpoint
The restore fails with,
sh: 1: /usr/lib/x86_64-linux-gnu/lxc/lxc-restore-net: not found
Regression potential: This can't effect anything besides lxc-checkpoint -r, which is broken anyways, so there should be no regressions.
================================================================
A patch for this has been posted to the upstream LXC list here:
https://lists.linuxcontainers.org/pipermail/lxc-
devel/2014-October/010741.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+subscriptions