Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
`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):
Rhel 7
How reproducible:
Everytime
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
Actual results:
anaconda-ks.cfg leaves out prepbot or biosboot options
Expected results:
Options used in kickstart installation should be present in anaconda-ks.cfg file created after installation
Additional info:
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: rramjattan 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
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.
Thanks,
Christian
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.
> Thanks,
> Christian
> IBM Linux Support
Yes, but not for 7.2
All,
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.
Thanks,
Christian
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.
https://rhn.redhat.com/errata/RHBA-2016-2168.html
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): Rhel 7 How reproducible: Everytime 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 Actual results: anaconda-ks.cfg leaves out prepbot or biosboot options Expected results: Options used in kickstart installation should be present in anaconda-ks.cfg file created after installation Additional info: