LVM volume name (hostname derived) can conflict with devices names

[Phil Regnauld]

When installing 12.04 server (amd64, but shouldn't matter), and one selects "Guided - use entire disk and setup LVM", the default logical volume name uses the hostname. For instance, if I use the hostname "core", this causes problems: when selecting write changes to disk, the error appears:

"Unexpected error while creating volume group"
"Autopartitioning using LVM failed because an error occurred while creating the volume group"
"Check /var/log/syslog ..."

Output from syslog:

Apr 11 09:49:35 partman: Reading all physical volumes. This may take a while...
Apr 11 09:49:35 partman-lvm:
Apr 11 09:49:35 partman-lvm: No volume groups found
Apr 11 09:49:35 partman-lvm:
Apr 11 09:50:19 partman-lvm: Physical volume "/dev/sda5" successfully created
Apr 11 09:50:19 partman-lvm:
Apr 11 09:50:19 partman-lvm: /dev/core: already exists in filesystem
Apr 11 09:50:19 partman-lvm:
Apr 11 09:50:19 partman-lvm:
Apr 11 09:50:19 partman-lvm: New volume group name "core" is invalid
Apr 11 09:50:19 partman-lvm:
Apr 11 09:50:19 partman-lvm:
Apr 11 09:50:19 partman-lvm: Run `vgcreate --help' for more information.

Of course, since /dev/core already exists, it fails.

This breaks installation, but isn't clear to the user why it is happening. It's especially confusing as it is the default
recommended choice during install.

A solution - the volume name selection should append something distinct to avoid conflicting with the device name, for instance: -vg or -lv.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1167834/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Dave Gilbert (ubuntu-treblig)]

Triaged: The cause is identified
High: Failure to install (and without identifying problem)