Bug 1321163 - RHEL 7.x: KickStart LVM provisioning issues
Summary: RHEL 7.x: KickStart LVM provisioning issues
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-24 20:08 UTC by Jason
Modified: 2016-05-26 21:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-26 21:02:08 UTC
Target Upstream Version:


Attachments (Terms of Use)
anaconda.log (7.38 KB, text/plain)
2016-03-24 20:32 UTC, Jason
no flags Details
Included disk partitioning (1.70 KB, text/plain)
2016-03-24 20:33 UTC, Jason
no flags Details
packaging.log (2.21 KB, text/plain)
2016-03-24 20:33 UTC, Jason
no flags Details
program.log (29.31 KB, text/plain)
2016-03-24 20:34 UTC, Jason
no flags Details
storage.log (123.71 KB, text/plain)
2016-03-24 20:34 UTC, Jason
no flags Details
storage.state (28.00 KB, text/plain)
2016-03-24 20:35 UTC, Jason
no flags Details
syslog (139.76 KB, text/plain)
2016-03-24 20:35 UTC, Jason
no flags Details

Description Jason 2016-03-24 20:08:08 UTC
Description of problem:
When multiple disks are used for a volume group anaconda provides the following errors:

GUI & Text installs produce:
Unable to allocate requested partition scheme

Output of /tmp/anaconda.log (relevant lines):
is_valid* all return true
is_valid_stage1_device(sda) = true
stage1 device cannot be of type lvmvg
stage1 device cannot be of type lvmlv


Version-Release number of selected component (if applicable):
RHEL-7.0
RHEL-7.1
RHEL-7.2


How reproducible:
When multiple volumes are combined into one volume group the error can be produced.


Steps to Reproduce:
The disk configuration used can be found under the 'additional info' section.

The disk(s) are partitioned as follows:
c0:
 |- d0
     |- p0 (sda)
     |- p1 (sdb)
 |- d1
     |- p0 (sdc)
     |- p1 (sdd)

Actual results:
Errors about partition scheme


Expected results:
The same kickstart disk partitions work in RHEL-6.5, 6.6 & 6.7.


Additional info:
# Zero the MBR
zerombr

# Clear out partitions for sda
clearpart --all --initlabel --drives=sda

# Create a /boot partition on sda of 500MB
part /boot --size=500 --fstype="ext4" --ondisk=sda

# Create an LVM partition of 172337MB on sda
part pv.root --size=172337 --ondisk=sda --grow --asprimary

# Create the root volume group
volgroup rootvg --pesize=4096 pv.root

# Create a memory partition of 31962MB
logvol swap --fstype="swap" --name="swaplv" --vgname="rootvg" --size=31962

# Create logical volume for the / mount point
logvol / --fstype="ext4" --name="rootlv" --vgname="rootvg" --size=102400

# Create logical volume for the /var mount point
logvol /var --fstype="ext4" --name="varlv" --vgname="rootvg" --size=40960

# Create logical volume for the /export/home mount point
logvol /export/home --fstype="ext4" --name="homelv" --vgname="rootvg" --size=10240

# Create logical volume for the /tmp mount point
logvol /tmp --fstype="ext4" --name="tmplv" --vgname="rootvg" --size=2048

# Create new physical volume on sdb as pv.optapp.1
part pv.optapp.1 --size=78741 --grow --ondisk=sdb

# Create new physical volume on sdc as pv.optapp.2
part pv.optapp.2 --size=100352 --grow --ondisk=sdc

# Create new physical volume on sdd as pv.optapp.3
part pv.optapp.3 --size=100352 --grow --ondisk=sdd

# Create new physical volume on sde as pv.optapp.4
part pv.optapp.4 --size=78741 --grow --ondisk=sde

# Create a new volume group with all the physical volumes
volgroup optappvg pv.optapp.1 pv.optapp.2 pv.optapp.3 pv.optapp.4 --pesize=4096

# Create a new logical volume for /opt/app mount point
logvol /opt/app --fstype="ext4" --name="optapplv" --vgname="optappvg" --size=268639

Comment 1 David Shea 2016-03-24 20:11:26 UTC
Please attach the logs from /tmp to this bug as individual, text/plain attachments.

Comment 3 Jason 2016-03-24 20:32:24 UTC
Created attachment 1140140 [details]
anaconda.log

Comment 4 Jason 2016-03-24 20:33:01 UTC
Created attachment 1140153 [details]
Included disk partitioning

Comment 5 Jason 2016-03-24 20:33:34 UTC
Created attachment 1140154 [details]
packaging.log

Comment 6 Jason 2016-03-24 20:34:00 UTC
Created attachment 1140155 [details]
program.log

Comment 7 Jason 2016-03-24 20:34:21 UTC
Created attachment 1140156 [details]
storage.log

Comment 8 Jason 2016-03-24 20:35:00 UTC
Created attachment 1140157 [details]
storage.state

Comment 9 Jason 2016-03-24 20:35:55 UTC
Created attachment 1140158 [details]
syslog

Comment 10 Jason 2016-03-24 20:38:14 UTC
I have attached the logs as requested. If necessary I can provide the kickstart script used but the attachment titled 'Included disk partitioning' is the output of that tool.

Comment 11 Jason 2016-03-24 21:39:03 UTC
FYI: If I modify the /tmp/ks-diskconfig file which is used to create the LVM & physical partitions to comment out the following I do not receive errors:

I am accommodating for the ext4 overhead per disk by %2 of the total bytes prior to the values shown below.

# Create new physical volume on sdb as pv.optapp.1
#part pv.optapp.1 --size=78741 --grow --ondisk=sdb

# Create new physical volume on sdc as pv.optapp.2
#part pv.optapp.2 --size=100352 --grow --ondisk=sdc

# Create new physical volume on sdd as pv.optapp.3
#part pv.optapp.3 --size=100352 --grow --ondisk=sdd

# Create new physical volume on sde as pv.optapp.4
#part pv.optapp.4 --size=78741 --grow --ondisk=sde

# Create a new volume group with all the physical volumes
#volgroup optappvg pv.optapp.1 pv.optapp.2 pv.optapp.3 pv.optapp.4 --pesize=4096

# Create a new logical volume for /opt/app mount point
#logvol /opt/app --fstype="ext4" --name="optapplv" --vgname="optappvg" --size=268639

Comment 12 David Lehman 2016-03-28 12:39:14 UTC
20:28:29,361 ERR anaconda: storage configuration failed: The following problem occurred on line 35 of the kickstart file:

Specified unpartitioned disk sdb in partition command


Perhaps you forgot to add sdb to the clearpart drive list?

Comment 13 Jason 2016-03-28 13:17:27 UTC
Would that be a change from 6.5, 6.6 & 6.7 to 7.x?

Comment 14 David Lehman 2016-03-28 13:22:59 UTC
Not that I'm aware of.

Comment 15 Jason 2016-03-28 13:28:41 UTC
Strange, it works without the 'clearpart' for each disk in all versions except > 7.x

Comment 16 David Lehman 2016-03-28 14:01:13 UTC
It looks like you have to include sdb to the clearpart drive list to make anaconda create a new disklabel on it.

Comment 17 Jason 2016-03-28 14:25:40 UTC
Ok you can close this out. Where version 6.5, 6.6 & 6.7 allow the originally attached ks-diskconfig version 7.x for multiple disks do require the following modification:

# Worked for 6.5, 6.6 & 6.7
clearpart --all --initlabel --drives=sda

# Required for > 7.x
clearpart --all --initlabel --drives=sda,sdb,sdc,sdd,sde

Thanks, looks like this bug was filed in error.


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