** Description changed:
+ ======================
+ SRU Justification:
+ 1. Impact: lxc-clone can produce non-functional containers
+ 2. Development fix: fix lxc-clone's handling of updates to lxc.mount entries.
+ 3. Stable fix: same as development fix
+ 4. Test case:
+ lxc-create -t ubuntu -n c1
+ sudo sed -i 's/lxc.mount =/lxc.mount =/' /var/lib/lxc/c1/config
+ sudo lxc-clone -o c1 -n c2
+ grep fstab /var/lib/lxc/c2/config
+ 5. Regression potential: only lxc-clone is updated, so regressions would be
+ contained in lxc-clone and in the code which is already broken for updating
+ lxc.mount.
+ ======================
+
Rene K. Mueller reports that when an original container does not have an
fstab, lxc-clone still adds a 'lxc.mount = ..../fstab' line, breaking
container start.
** Changed in: lxc (Ubuntu Precise)
Assignee: Serge Hallyn (serge-hallyn) => (unassigned)
** Changed in: lxc (Ubuntu Quantal)
Assignee: Serge Hallyn (serge-hallyn) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1084089
Title:
lxc-clone shouldn't add fstab line if it wasn't there originally
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1084089/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
