RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1131609 - [Doc] RHEL7 RC1/anaconda not working with multiple volumes
Summary: [Doc] RHEL7 RC1/anaconda not working with multiple volumes
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Installation_Guide
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Bokoc
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On: 1093144
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-19 16:27 UTC by Petr Bokoc
Modified: 2019-03-06 00:43 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1093144
Environment:
Last Closed: 2014-09-23 12:28:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Petr Bokoc 2014-08-19 16:27:26 UTC 
+++ This bug was initially created as a clone of Bug #1093144 +++
Description of problem:

In RHEL7 beta I installed VMs with more than one drive using anaconda. When I do the same thing (the exact same anaconda configuration) but in RHEL7 RC1 it produces this:

ValueError: not enough free space in volume group

This seems to be regardless of the --size argument used. I gave it volume files as large as 50 GB and passed --size=12000, --size=1, --size=20000... nothing worked for RC1.

The anaconda file (well, the partition information segment) is this:

#----------------
zerombr
clearpart --all --initlabel --drives=sda,sdb

part raid.11 --size=500 --ondrive=sda
part raid.12 --size=1 --grow --ondrive=sda

part raid.21 --size=500 --ondrive=sdb
part raid.22 --size=12000 --grow --ondrive=sdb

raid /boot --fstype ext4 --device md1 --level=RAID1 raid.11 raid.21
raid pv.01 --device md0 --level=RAID1 raid.12 raid.22

volgroup sysvg pv.01
logvol / --vgname=sysvg --size=8000 --name=lv_root --fstype=ext4
logvol swap --vgname=sysvg --name=lv_swap --grow --size=1024 --maxsize=2048
logvol /mnt/edata --vgname=sysvg --size=1 --grow --name=mntedata
#----------------

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

RHEL rc1

How reproducible:

Trying to install RHEL7 rc1 VMs using anaconda/qemu with two volumes rather than one (the latter worked fine for me). 

Please note again that the exact same configuration works fine for RHEL7 beta, I just tested it. Everything is the same - host, kickstart, IP, image file sizes, etc.

Steps to Reproduce:
1. Use two image files in kickstart rather than one as above.
2. Try to install
3. Get error message

Actual results:

ValueError: not enough free space in volume group

Expected results:

RHEL7 rc1 installs with two volumes.

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