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
What happened:
Encountered errors on generate-version-info.sh when verifying kubelet and aws binary versions.
AWS command not found:
What you expected to happen:
Can complete the generate-version-info.sh without any issues for kubelet and aws cli version checking
How to reproduce it (as minimally and precisely as possible):
I tried using RHEL 8.8 or the latest AML2, edited the variables to use containerd 1.6.* (for some reason 1.7.* isn't available for AML2)
cloned the latest repo and did make 1.28. Error was encountered on generate-version-info.sh
Anything else we need to know?:
The base image was AML2 CIS Level 2 hardened.
After investigating, inside the install-worker.sh script, the chmod +x command does not work properly.
Changed this to chmod 755 and it works for the permission issue.
No workaround yet for the missing AWS command error. Have checked manually the instance and awscli v2 is indeed installed using ec2-user.
Adding more information here, I have a copy of the repo from last week of october, seems like the problems with generate-version-info.sh were allowed to continue before:
What happened:
Encountered errors on
generate-version-info.sh
when verifying kubelet and aws binary versions.AWS command not found:
What you expected to happen:
Can complete the
generate-version-info.sh
without any issues for kubelet and aws cli version checkingHow to reproduce it (as minimally and precisely as possible):
I tried using RHEL 8.8 or the latest AML2, edited the variables to use containerd 1.6.* (for some reason 1.7.* isn't available for AML2)
cloned the latest repo and did
make 1.28
. Error was encountered on generate-version-info.shAnything else we need to know?:
The base image was AML2 CIS Level 2 hardened.
After investigating, inside the
install-worker.sh
script, thechmod +x
command does not work properly.Changed this to
chmod 755
and it works for the permission issue.No workaround yet for the missing AWS command error. Have checked manually the instance and awscli v2 is indeed installed using ec2-user.
Environment:
aws eks describe-cluster --name <name> --query cluster.platformVersion
): eks.6aws eks describe-cluster --name <name> --query cluster.version
): 1.28uname -a
): 4.18.0-513.9.1.el8_9.x86_64cat /etc/eks/release
on a node):The text was updated successfully, but these errors were encountered: