You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is caused because this AMI release has a lock on kernel-devel and kernel-headers, but not the kernel. That will be fixed in the next AMI release. We've added locking on kernel packages to prevent unintentional updates that could introduce instability; and because updating the kernel on a running node requires a reboot, which should generally only be done within a managed upgrade process that will avoid disruption to your workloads.
You can always get around the version locks by disregarding the plugin:
yum update --noplugins
But be aware that the kernel, containerd, nvidia-driver-latest-dkms, etc. that is installed may introduce instability and version skew across your nodes.
What happened:
yum update fails with:
**Steps to reproduce **:
What you expected to happen:
Any packages with updates besides those versionlocked to be installed
Anything else we need to know?:
Trying to build a new AMI for 1.22 based on amazon-eks-gpu-node-1.22-v20230203
Environment:
aws eks describe-cluster --name <name> --query cluster.platformVersion
):aws eks describe-cluster --name <name> --query cluster.version
):uname -a
): Linux ip-10-130-72-1.hbk.com 5.4.228-131.415.amzn2.x86_64 Template is missing source_ami_id in the variables section #1 SMP Tue Dec 20 12:51:02 UTC 2022 x86_64 x86_64 x86_64 GNU/Linuxcat /etc/eks/release
on a node):The text was updated successfully, but these errors were encountered: