Skip to content
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

Encountering Permission Error and AWS command not found Building AMI #1554

Open
voidteatime opened this issue Jan 3, 2024 · 1 comment
Open

Comments

@voidteatime
Copy link

What happened:
Encountered errors on generate-version-info.sh when verifying kubelet and aws binary versions.
image
AWS command not found:
image

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.

Environment:

  • AWS Region: ap-southeast-1
  • Instance Type(s): m5.large
  • EKS Platform version (use aws eks describe-cluster --name <name> --query cluster.platformVersion): eks.6
  • Kubernetes version (use aws eks describe-cluster --name <name> --query cluster.version): 1.28
  • AMI Version: v20240103
  • Kernel (e.g. uname -a): 4.18.0-513.9.1.el8_9.x86_64
  • Release information (run cat /etc/eks/release on a node):
@voidteatime
Copy link
Author

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:
image

commits from 967fb36 were causing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant