Amazon EKS optimized Ubuntu Linux AMIs - new instance family (m7a) fails to join cluster - bootstrap scripts lagging
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
High
|
Thomas Bechtold |
Bug Description
## Description
AWS released a new instance family m7a - https:/
This is not yet present in eni-max-pods.txt file
The bootstrap.sh file fails silently due to missing log function if the instance type is missing from the file.
## Steps to Reproduce
Launch an m7a instance with the EKS Ubuntu AMI in an EKS cluster.
It won't join the cluster and you'll get the following error on /var/log/
.....
/etc/eks/
Exited with error on line 420
It seems like the log function, introduced in this PR: https:/
## More context
Adding the log function to bootstrap.sh, it fails in another step:
# /etc/eks/
/etc/eks/
/etc/eks/
imds is a helpter script that was added in this PR: https:/
The script exists under /usr/local/
## What's the fix?
Merge latest EKS AMI bootstrap.sh: https:/
Changed in cloud-images: | |
status: | New → Confirmed |
assignee: | nobody → Thomas Bechtold (toabctl) |
importance: | Undecided → Medium |
importance: | Medium → High |
Changed in cloud-images: | |
status: | Confirmed → Fix Released |
tags: | added: eks |
Changed in cloud-images: | |
status: | In Progress → Fix Committed |
A little delayed, but this is available in serials 20230830 and newer. Please let us know if you see this again.