Almalinux-8 Hardened image(HI's) and source image are unable to upgrade kernel due to under sized partition

Converging a molecule scenario containing an almalinux-8 image results in the following when there a kernel update available.

In the past ticket was submitted to almalinux foundation who provide the source almalinux image that we build the alma HI’s on top of. They resolved the issue by expanding the partition size.
Is this issue also present on the almalinux-8 daily images?

error:-
fatal: [molecule-almalinux-8]: FAILED! => {“changed”: false, “failures”: , “msg”: “Unknown Error occurred: Transaction test error:\n installing package kernel-core-4.18.0-553.5.1.el8_10.x86_64 needs 52MB on the / filesystem\n installing package kernel-modules-4.18.0-553.5.1.el8_10.x86_64 needs 126MB on the / filesystem\n installing package kernel-4.18.0-553.5.1.el8_10.x86_64 needs 170MB on the / filesystem\n installing package kernel-tools-4.18.0-553.5.1.el8_10.x86_64 needs 214MB on the / filesystem\n installing package python3-perf-4.18.0-553.5.1.el8_10.x86_64 needs 257MB on the / filesystem\n installing package libxml2-2.9.7-18.el8_10.1.x86_64 needs 259MB on the / filesystem\n\nError Summary\n-------------\nDisk Requirements:\n At least 259MB more space needed on the / filesystem.\n”, “rc”: 1, “results”: }

Looking forward to your help soon.

May I ask which AlmaLinux OS 8 image you are experiencing this issue with?

Sorry for the late response…

VM was built with the current kernel version - 4.18.0-553.5.1.el8_10Linux molecule-almalinux-8 4.18.0-553.5.1.el8_10.x86_64 #1 SMP Wed Jun 5 09:12:13 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux

"FYI messing around with alma8 on aws just now.
It updates fine if we add “diskspacecheck=0” to /etc/yum.conf

Hi Ikhn,

Did you find anything on this issue from your side? Would love to hear in case you got anything in regard to this issue.

Looking forward to your response soon.

Thanks

Hi @singhind,

It still is not clear to me which AlmaLinux OS image you are experiencing the issue.

Could you check this page tell me which image you are having issue please?