Description of Problem: --bytes-per-inode option in kickstart install mode does not work on per partition basis, but globally. In addition the last value used in per partition option is set for all partitions having the option. Note that it happens ONLY in kickstart mode How Reproducible: Use kickstart install file with options alike: part /part1 [other opts] --on-disk=sda part /part2 [other opts] --on-disk=sdb --bytes-per-inode=266144 [I'm not sure if the same will happen if you have partitions on same disk] Then install the system using it, check number of bytes per inode with dumpe2fs. Actual Results: /part1 and /part2 will have 266144 bytes per inode ... Expected Results: /part1 - default bytes-per-inode /part2 266144 bytes-per-inode Additional Information: It seems that some values are not cleared in a for loop in anaconda's sources: kickstart.py file.
Will be fixed in the next release.
Deferring to future release.
I'm reopening this bug because it was never fixed and I now have a customer that is hitting this issue.
-