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.
Also on RHEL-9.2.0-20221101.d.0 with anaconda-34.25.2.1-1.el9, python3-blivet-3.6.0-2.el9.
+++ This bug was initially created as a clone of Bug #2139187 +++
Description of problem:
Kickstart installation fails with the following error:
==========
Failed to save storage configuration
The following problem occurred on line 9 of the kickstart file:
device is too small for new format
==========
The partitioning defined in the kickstart file:
bootloader --location=mbr
zerombr
clearpart --all --initlabel
part swap --recommended
part / --grow
reqpart --add-boot
part raid.01 --size=100
part raid.02 --size=100
raid /raid --level=0 --device=raid-test raid.01 raid.02
The same kickstart works fine on RHEL-8.7.
Version-Release number of selected component (if applicable):
RHEL-8.8.0-20221101.d.1
anaconda-33.16.8.1-1.el8
python3-blivet-3.6.0-2.el8
How reproducible:
Always
Steps to Reproduce:
1. Run a kickstart installation with the partitioning commands above.
Actual results:
Error: device is too small for new format
Expected results:
A successful installation.
We've increased the min size for XFS in blivet 3.6[1] to 300 MiB to match the new filesystem size limits implemented in xfsprogs 5.19. RHEL is still on xfsprogs 5.0 so this limit doesn't apply here so I will revert this change.
[1] https://github.com/storaged-project/blivet/pull/1070
Checked that python-blivet-3.6.0-3.el9 is in nightly compose RHEL-9.2.0-20221110.2
There's no documentation needed for this bug - not checking
No further testing is needed during verification based on comment 3
Moving to VERIFIED
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 (python-blivet bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2023:2230