Bug 965781 - cannot create a second volume group
cannot create a second volume group
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-05-21 13:32 EDT by Jeff Bastian
Modified: 2013-05-21 13:43 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-05-21 13:43:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jeff Bastian 2013-05-21 13:32:32 EDT
Description of problem:
I'm running the "Create multiple Volume Group (anaconda-lvm-1)" test for
the Fedora 19 Test Day.

I created a virtual machine with 4 disks (16 GB each) and started the
installation.  I selected all 4 disks and chose manual partitioning with LVM.

I hit "+" to create the / logical volume, size 8 GB, and it created a
"fedora" Volume Group.

Next I hit "+" again to create /home of size 4 GB.  It placed it on the
same "fedora" Volume Group, but I didn't want that, so I clicked the down-arrow
on the Volume Group and selected "Create a new volume group..."
I gave it the name "vg2" and selected the 2nd disk in the list.
(RAID Level None, Size policy Automatic).  I hit the "Save" button.

And the /home partition is still on the "fedora" Volume Group.
What happened to my "vg2" Volume Group?

Version-Release number of selected component (if applicable):

How reproducible:
every time

Steps to Reproduce:
1. create / logical volume on default "fedora" Volume Group
2. create /home logical volume
3. select "Create new volume group" for /home and create "vg2"

Actual results:
/home says on "fedora" Volume Group and "vg2" is not created

Expected results:
/home is on "vg2" Volume Group

Additional info:
Comment 1 Jeff Bastian 2013-05-21 13:43:38 EDT
Oh, it was my fault.  I forgot to hit the "Update Settings" button.  Never mind...

Note You need to log in before you can comment on or make changes to this bug.