This bug was fixed in the package lxc - 0.7.5-3ubuntu66
---
lxc (0.7.5-3ubuntu66) precise-proposed; urgency=low
[ William Grant ]
* lxc-start-ephemeral: exit with the command's status, not always 0.
(LP: #1050351)
[ Serge Hallyn ]
* 0227-ubuntu-cloud-parsing: fix some
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu39
---
lxc (0.8.0~rc1-4ubuntu39) quantal-proposed; urgency=low
* 0227-ubuntu-cloud-parsing: fix some option parsing bugs in ubuntu-cloud
template (LP: #1076031)
* 0229-lxc-clone-mount-fix: fix wrong handling of
Confirmed in precise.
--
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
Confirmed in quantal
** Tags removed: needssru verification-needed
** Tags added: verification-done
--
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
Hello Serge, or anyone else affected,
Accepted lxc into quantal-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lxc/0.8.0~rc1-4ubuntu39
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/lxc
--
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
** Changed in: lxc (Ubuntu Quantal)
Status: Triaged = In Progress
** Changed in: lxc (Ubuntu Quantal)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu Precise)
Status: Triaged = In Progress
** Changed in: lxc (Ubuntu Precise)
Assignee:
** 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
While fixing this one, can you also have lxc-clone properly change the
lxc.mount line to point to the clone (if lxc.mount exists for the source).
I thought that was done, but apparently not, I spent half an hour yesterday
trying to figure out why a container was ignoring new fstab entries,
Quoting Stéphane Graber (stgra...@stgraber.org):
While fixing this one, can you also have lxc-clone properly change the
lxc.mount line to point to the clone (if lxc.mount exists for the source).
Are you sure? I looked at the code before filing this and it was doing
the right thing, using
Well, I did a lxc-clone yesterday using a daily build of the staging tree and
it definitely was still pointing at the source.
Now maybe we have some patch in Ubuntu that's not in staging and that fixes
that, or staging recently regressed, not sure...
--
You received this bug notification
Actually it's a bit worse than that. The code in the package was not
fixed quite the same way as upstream. Instead of looking for
'lxc.mount[ \t]', it looks for any 'lxc.mount'. If found it removes all
those entries and adds a new fstab entry. The problem is that the
lxc.conf always can have
** Tags added: needssru
--
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 was fixed in the package lxc - 0.8.0~rc1-4ubuntu46
---
lxc (0.8.0~rc1-4ubuntu46) raring; urgency=low
* 0229-lxc-clone-mount-fix: fix wrong handling of lxc.mount entries in
lxc-clone. (LP: #1084089)
* debian/apparmor/abstractions-lxc-container-base: deny read/write
14 matches
Mail list logo
