Bug 1404531

Summary: Anaconda assign wrong size for biosboot partition when use PXE+kickstart installation
Product: Red Hat Enterprise Linux 7 Reporter: Dong <dfu>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: cww, dfu
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-19 17:00:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1420851    

Description Dong 2016-12-14 03:16:49 UTC 
Description of problem:
 When customer use PXE and kickstart to install RHEL 7.1 , the installation failed because the wrong size of biosboot partition.

 The size of biosboot partition is set as 1MB in ks.cfg :
~~~
part biosboot --fstype='biosboot' --ondisk=sda --size=1
~~~  
  But the actual size will be 4MiB and will see this information:
~~~
allowable size is 512 KiB to 2048 KiB
~~~
 Then the installation failed.


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

How reproducible:


Steps to Reproduce:
1. Use 16*600G hard driver set up RAID 1+0, the biosboot partition will be assigned 2MiB size and the install will be completed successfully. 
2. Use 16*600G hard driver set up RAID 0, the biosboot partition will be assigned 4MiB size and the install will be failed. 


Actual results:
  The actual allocation size and settings are inconsistent, the installation failed.

Expected results:
  The biosboot partition assigned size is the same as the setting.