-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't build rocky9 AMIs due to hardcoded rocky8 URL/9.4 lustre issues #6239
Comments
Thank you for taking a look at this @enrico-usai - for the record, before the 9.4 drivers were released I tried running with a patched cookbook that had the correct 9.3 URL, but that didn't work very well. Setting Anyway, the 9.4 builds work just fine now, so from my point of view this is resolved now |
Thanks @gbts for sharing your approach. |
This line in the rocky cookbook here: https://github.com/aws/aws-parallelcluster-cookbook/blob/16a081940c41cb3bb42cb2c1ddf8de3c059af788/cookbooks/aws-parallelcluster-platform/resources/install_packages/install_packages_rocky8.rb#L36 looks like a fallback for older kernel versions where the kernel headers are not available in the main repo. It instead tries to fetch
kernel-devel
directly from the rocky vault for the BaseOS repo. But sincekernel-devel
was moved to the AppStream repo in RHEL/Rocky 9, that URL will just hit a 404.Enabling
UpdateOsPackages
in the ImageBuilder template fixes it but now it will upgrade the instance to 9.4, which fails further down when trying to build the kernel module for lustre (presumably because there's no support for the 9.4 kernel yet). So currently all rocky9 builds seem to be failing.The text was updated successfully, but these errors were encountered: