[Bug 154086] Re: Installing to HDD with previous ubuntu fails to create fresh LVM claiming group already in use
Peter Matulis
peter.matulis at canonical.com
Fri Oct 12 13:32:02 UTC 2012
This looks good to me.
== Test method ==
I used
http://archive.ubuntu.com/ubuntu/dists/precise-updates/main/installer-
amd64/current/images/netboot/netboot.tar.gz
and
APPEND initrd=ubuntu-installer/amd64/initrd.gz priority=critical
locale=en_US interface=eth0 url=http://10.153.107.1/preseed.txt
DEBCONF_DEBUG=developer apt-setup/proposed=true
Then, with an existing install on-disk, I rebooted, removed the array,
redid the same array, and installed successfully.
After that, I removed 'apt-setup/proposed=true', rebooted, removed the
array, redid the same array, and eventually got the error:
"Volume group name already in use"
I would say that the proposed Precise fix has been verified.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to partman-auto-lvm in Ubuntu.
https://bugs.launchpad.net/bugs/154086
Title:
Installing to HDD with previous ubuntu fails to create fresh LVM
claiming group already in use
Status in “partman-auto-lvm” package in Ubuntu:
Fix Released
Status in “partman-lvm” package in Ubuntu:
Won't Fix
Status in “partman-auto-lvm” source package in Precise:
Fix Committed
Status in “partman-auto-lvm” source package in Quantal:
Fix Released
Status in “partman-auto-lvm” package in Debian:
New
Bug description:
[IMPACT]
* Fail to pre-seed automatic LVM installation on machines with:
- empty / new partition table
- not-zeroed out disks
- which had the same partition layout
- and the same volume group names
* this affects large scale automated installs / deployments, as it is
very easy to get all of those conditions when reinstalling.
* To fix this bug partman-auto-lvm should be updated with the proposed fix
* the fixed partman-auto-lvm should also make it onto affected images
[TESTCASE]
* Pre-seed or manually execute "Guided partitioning - LVM"
* Remove/Clear partition table with e.g.:
# fdisk /dev/vda << EOF
o
w
EOF
* Pre-seed or manually execute "Guided partitioning - LVM" again
[Regression Potential]
* while the current behaviour is broken, it did allow to "resurrect"
LVM groups by bailing out the install after the zombie VGs groups
became detected, but it is not guaranteed that the resurrected VGs are
correct: the partition can be too small and VG can be incomplete (only
1 out of many physical volumes). Some people may have been relying on
this. The correct behaviour will attempt to delete the zombie VGs by
asking a question that can be pre-seeded or manually backed out of.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto-lvm/+bug/154086/+subscriptions
More information about the foundations-bugs
mailing list