Red Hat Bugzilla – Bug 747417
anaconda is ignoring kickstart --fsprofile when combined with --useexisting or --onpart
Last modified: 2017-03-13 07:34:59 EDT
Created attachment 529079 [details]
I'm attempting to set custom mke2fs options by adding a section to /etc/mke2fs.conf in %pre and using it via --fsprofile. It appears that anaconda is ignoring the --fsprofile option though (this is with F16-Beta).
I'll attach a sample kickstart that shows the problem in a VM for me.
Anaconda is erroneously ignoring fsprofile when combined with --useexisting or --onpart.
An updates image is available for the time being which can be used with the version of anaconda in the Fedora 16 Beta. To use it, add the following to the boot command line:
I'm proposing this as a NTH for F16 since the patch is very straightforward and low-risk.
NTH is f16-accepted, not f16blocker.
+1 NTH, useful patch can't be fixed post-release, low risk.
Discussed at 2011-10-21 NTH review meeting, accepted as NTH for the reasons mentioned in comment #4.
anaconda-16.23-1.fc16 has been submitted as an update for Fedora 16.
This should be fixed now, let's close. Re-open if it's still happening in post-16.23 F16 RCs. thanks!
Fedora Bugzappers volunteer triage team