Bug 1404531 - Anaconda assign wrong size for biosboot partition when use PXE+kickstart installation
Summary: Anaconda assign wrong size for biosboot partition when use PXE+kickstart inst...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1420851
TreeView+ depends on / blocked
 
Reported: 2016-12-14 03:16 UTC by Dong
Modified: 2020-08-13 08:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-19 17:00:55 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


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