This bug was fixed in the package lxc - 0.9.0-0ubuntu3.3
---
lxc (0.9.0-0ubuntu3.3) raring-proposed; urgency=low
* 0006-lxc-clone-fix-lvm-blockdev-usage: fix use of wrong pathnames for both
block devices and mount targets in the LVM case. (LP: #1183354)
-- Serge Hallyn
This bug was fixed in the package lxc - 0.9.0-0ubuntu3.3
---
lxc (0.9.0-0ubuntu3.3) raring-proposed; urgency=low
* 0006-lxc-clone-fix-lvm-blockdev-usage: fix use of wrong pathnames for both
block devices and mount targets in the LVM case. (LP: #1183354)
-- Serge Hallyn
Hello Brian
Just tested 0.9.0-0ubuntu3.3
The bug is fixed.
# apt-cache policy lxc
lxc:
Installed: 0.9.0-0ubuntu3.3
Candidate: 0.9.0-0ubuntu3.3
Version table:
*** 0.9.0-0ubuntu3.3 0
500 http://archive.ubuntu.com/ubuntu/ raring-proposed/universe amd64
Packages
100
Hello Brian
Just tested 0.9.0-0ubuntu3.3
The bug is fixed.
# apt-cache policy lxc
lxc:
Installed: 0.9.0-0ubuntu3.3
Candidate: 0.9.0-0ubuntu3.3
Version table:
*** 0.9.0-0ubuntu3.3 0
500 http://archive.ubuntu.com/ubuntu/ raring-proposed/universe amd64
Packages
100
Hello Sergey, or anyone else affected,
Accepted lxc into raring-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lxc/0.9.0-0ubuntu3.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Sergey, or anyone else affected,
Accepted lxc into raring-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lxc/0.9.0-0ubuntu3.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ ***
+ 1. Impact: lxc-clone for lvm-backed containers is broken
+ 2. Development fix: saucy fixed the use of wrong pathnames in the
+ lxc-clone script.
+ 3. Stable fix: same as development fix
+ 4. Test case:
+ * Create an lvm
** Description changed:
+ ***
+ 1. Impact: lxc-clone for lvm-backed containers is broken
+ 2. Development fix: saucy fixed the use of wrong pathnames in the
+ lxc-clone script.
+ 3. Stable fix: same as development fix
+ 4. Test case:
+ * Create an lvm
** Branch linked: lp:~ubuntu-branches/ubuntu/saucy/lxc/saucy1
--
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/1183354
Title:
lxc-clone makes unbootable clone when using lvm backing
** Branch linked: lp:~ubuntu-branches/ubuntu/saucy/lxc/saucy1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1183354
Title:
lxc-clone makes unbootable clone when using lvm backing store
To manage
Thank you, Serge.
Rebuild lxc 0.9.0-0ubuntu9 for raring, works as expected now!
--
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/1183354
Title:
lxc-clone makes unbootable clone when
Thank you, Serge.
Rebuild lxc 0.9.0-0ubuntu9 for raring, works as expected now!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1183354
Title:
lxc-clone makes unbootable clone when using lvm backing
Thanks for submitting this bug. Note that snapshots do seem to work
(sudo lxc-clone -s -o r1 -n r2), but non-snapshot ones do indeed hang.
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
--
You received this bug
** Also affects: lxc (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Saucy)
Importance: Medium
Status: Confirmed
** Changed in: lxc (Ubuntu Saucy)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification
The patch introduced to fix this in saucy should be cleanly applicable
to raring.
** Changed in: lxc (Ubuntu Raring)
Importance: Undecided = High
** Changed in: lxc (Ubuntu Saucy)
Importance: Medium = High
** Changed in: lxc (Ubuntu Raring)
Status: New = Triaged
** Changed in: lxc
This bug was fixed in the package lxc - 0.9.0-0ubuntu9
---
lxc (0.9.0-0ubuntu9) saucy; urgency=low
* 0006-lxc-clone-fix-lvm-blockdev-usage: fix use of wrong pathnames for both
block devices and mount targets in the LVM case. (LP: #1183354)
-- Serge Hallyn
Thanks for submitting this bug. Note that snapshots do seem to work
(sudo lxc-clone -s -o r1 -n r2), but non-snapshot ones do indeed hang.
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
--
You received this bug
** Also affects: lxc (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Saucy)
Importance: Medium
Status: Confirmed
** Changed in: lxc (Ubuntu Saucy)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification
The patch introduced to fix this in saucy should be cleanly applicable
to raring.
** Changed in: lxc (Ubuntu Raring)
Importance: Undecided = High
** Changed in: lxc (Ubuntu Saucy)
Importance: Medium = High
** Changed in: lxc (Ubuntu Raring)
Status: New = Triaged
** Changed in: lxc
This bug was fixed in the package lxc - 0.9.0-0ubuntu9
---
lxc (0.9.0-0ubuntu9) saucy; urgency=low
* 0006-lxc-clone-fix-lvm-blockdev-usage: fix use of wrong pathnames for both
block devices and mount targets in the LVM case. (LP: #1183354)
-- Serge Hallyn
20 matches
Mail list logo
