`biosboot` and `prepboot` are now included in the Kickstart file after installation
When a Kickstart file included instructions to create `biosboot` or `prepboot` partitions, the Blivet module did not pass this information in Kickstart data. Consequently, after a Kickstart installation, the Kickstart file on the newly installed system did not include the options for creating `biosboot` and `prepboot` partitions and could not be reused successfully on other systems. With this update, the Kickstart output includes these options as expected, and the Kickstart file can be used on other systems to create the `biosboot` and `prepboot` partitions.
Description of problem:
After kickstart installation, /root/anaconda-ks.cfg does not contain either biosboot or prepboot option that is required and was used for kickstart install
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Modify kickstart file to use
"part biosboot --fstype=biosboot --size=2 --ondisk=sda"
OR "part prepboot --fstype=prepboot --size=10 --ondisk=sda"
2. Successfully install system using kickstart file
3. Inspect /root/anaconda-ks.cfg on newly installed system for biosboot or prepboot options
anaconda-ks.cfg leaves out prepbot or biosboot options
Options used in kickstart installation should be present in anaconda-ks.cfg file created after installation
This was done on an IBM Power 8 Model 824 server.
We built an LPAR on this and observed the "part prepboot" entry for power systems was excluded each time we installed the system - Either from VNC menus or a NFS kickstart file. THis was build from a Redhat 7.1 BE iso downloaded very recently from RedHat. If you need further information: firstname.lastname@example.org or 9546096386
Note for the future, the reason why these aren't being included is that everything w/o a real mountpoint (except swap) is filtered out in blivet in _updateCustomStorageKSData
Is this going to still be pursued as a bug? As of now there is no option for a kickstart file to work properly for ppc without manually making changes to the anaconda-ks.cfg file.
IBM Linux Support
(In reply to ibm_cskoehle from comment #5)
> Hi Brian,
> Is this going to still be pursued as a bug? As of now there is no option
> for a kickstart file to work properly for ppc without manually making
> changes to the anaconda-ks.cfg file.
> IBM Linux Support
Yes, but not for 7.2
Is there anyway the fix for this issue can be included in RHEL 7.2? It seems like a very small fix and don't really see why the customer should need to wait for a year or more to see this implemented.
Just checking again on this bug. Any progress on getting this to be included in RHEL 7.2?
Customer is requesting that this be added to 7.2. I advised the customer that 7.2 is already at a point in development that this may not be possible.
------- Comment From email@example.com 2016-02-10 13:56 EDT-------
Whats the status on this issue?
*** Bug 1256249 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.