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.
Bug 2042431 - Recommended minimal /boot size 200MiB is not enough
Summary: Recommended minimal /boot size 200MiB is not enough
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: anaconda
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vendula Poncova
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-19 14:09 UTC by Jan Stodola
Modified: 2022-11-15 10:29 UTC (History)
2 users (show)

Fixed In Version: anaconda-34.25.1.10-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 09:58:06 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-108718 0 None None None 2022-01-19 14:21:58 UTC
Red Hat Issue Tracker RTT-4523 0 None None None 2022-05-16 16:45:38 UTC
Red Hat Issue Tracker RTT-4524 0 None None None 2022-05-16 16:45:42 UTC
Red Hat Product Errata RHBA-2022:7977 0 None None None 2022-11-15 09:58:24 UTC

Description Jan Stodola 2022-01-19 14:09:56 UTC
This bug was initially created as a copy of Bug #1844423

I am copying this bug because: 
This bug should also be fixed in RHEL-9.
The new recommended minimum should be 512 MiB, see the upstream PR:
https://github.com/rhinstaller/anaconda/pull/3302


Since RHEL 8.2, I always get an installation error of:

DNF error: Error in POSTTRANS scriptlet in rpm package kmod-kvdo

Finally I found anaconda recommends the size of /boot partition is 200 Mib or higher but 200 MB is not enough for the partition and the partition usage is 100% and causes above error.

Probably I think the minimum /boot size would be 300MB and the recommendation is 400MB in RHEL 8.y if I think the kernel update later.

Comment 1 Vendula Poncova 2022-05-10 15:04:00 UTC
Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/4096

Comment 6 Jan Stodola 2022-08-09 12:07:12 UTC
Checked that anaconda-34.25.1.10-1.el9 is in nightly compose RHEL-9.1.0-20220809.0

Moving to VERIFIED

Comment 8 errata-xmlrpc 2022-11-15 09:58:06 UTC
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 (anaconda 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-2022:7977


Note You need to log in before you can comment on or make changes to this bug.