Bug 529846

Summary: kickstart --fstype ignored for /boot
Product: [Fedora] Fedora Reporter: Andrew Jones <drjones>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: anaconda-maint-list, cjg9411, crobinso, vanmeeuwen+fedora
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-13.7-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-21 18:42:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
updates.img to allow setting /boot fstype in kickstart none

Description Andrew Jones 2009-10-20 12:58:22 UTC 
Description of problem:

Created a rawhide virtual machine using a kickstart. The kickstart contained the line

part /boot --fstype=ext3 --size=400

but the /boot fs was still created as ext4.
Comment 1 Chris Lumens 2009-10-20 13:25:14 UTC 
This is by design - anaconda checks to make sure that /boot is of a certain type and if not, corrects the request to be of that type.  This is to make sure people don't do anything crazy like put /boot on vfat or something else that we won't be able to boot from later.
Comment 2 Andrew Jones 2009-10-21 15:50:49 UTC 
I really think that kickstart files should be honored. It seems strange to me that I'm allowed to do a kickstart install without a /boot file system, or, if I install manually, I can select ext3 for /boot, but I can't kickstart it that way. If a person doing manual partition table management can be trusted to select an appropriated fs, then I think the person writing a kickstart should be trusted as well.

Besides that, some boot loaders (xen pygrub, for example) lag behind a bit, and when you override the /boot fs to a newer, still not supported fs, then the new system is unbootable.

Reopenning for the arguments above.
Comment 3 Chris Lumens 2009-10-21 18:42:48 UTC 
This should be fixed in the next build of anaconda for Rawhide, but not for F12.
Comment 4 Chris Lumens 2009-10-30 13:10:31 UTC 
*** Bug 531951 has been marked as a duplicate of this bug. ***
Comment 5 Charles J. Gruener 2009-11-24 19:18:16 UTC 
So how to I kickstart my F12 Xen domU installs for my RHEL5.4 dom0 if this has been pushed to rawhide?
Comment 6 Orion Poplawski 2009-11-24 22:10:02 UTC 
Created attachment 373556 [details]
updates.img to allow setting /boot fstype in kickstart

See https://fedoraproject.org/wiki/Anaconda/Updates for how to use.