[FEATURE REQUEST] Include a CI test to exercise sufficiency of `/boot` paritition
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 105
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
The 2026.02.01 builds were producing (CentOS Stream 9) AMIs with insufficient space in /boot to support kernel patch-ups. While the resulting AMI was bootable and other RPMs could be updated, space in /boot was insufficient to support a second /boot/initramfs-* file, rendering EC2s launched from the AMI unable to be adequately secured.
Note: the build-jobs for the CentOS Stream 9 images were indicating a space problem
- CentOS 9 Stream - Commercial (CI Job #63867106796)
- CentOS 9 Stream - GovCloud(CI Job #63867107155)
However, the EL9 version of dnf doesn't seem to declare %posttrans job-failures as fatal errors. As such, the builds complete, even though the resultant images are arguably broken.
Have attempted to contact Red Hat on the dnf issue via AWS (since the official, PAYG images for RHEL 9 include basic OS support).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CentOS 9 Stream CI jobs linked in the issue and trace the build entry points that produce their AMIs. Add a CI check for available space in /boot after the image build, and verify that the check fails when the partition cannot hold another /boot/initramfs-* file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, cloud, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100