-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
AMI 1.13 is failing with No networks found in /etc/cni/net.d #365
Comments
@safiqueahemad Hi, what CNI version is applied to the cluster?
To apply v1.5.3 to the cluster, try:
|
@mogren CNI v1.5.3 is already in place... see the output below: |
The next option to check is that the nodes have the permissions that the CNI needs to get IPs, that would be the managed policy AmazonEKS_CNI_Policy. If that one is present, do the Subnets have enough free IPs? How many ENIs are available in the account? |
@mogren ... Those (CNI policy, eni and subnet IPs) are I think looks correct... Cannot find a valid baseurl for repo: amzn2-core/2/x86_64
|
Look at that |
try this: #306 (comment) |
Closing, see #306 |
Same issue here, resolved by upgrading the CNI plugin. |
What happened:
Bringing up fresh cluster with control plan on 1.13. When spawn EKS worker node then they are failing with error below:
kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is n
04.339702 5701 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
What you expected to happen:
EKS node should join the cluster properly.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
us-east-1
t2.medium
aws eks describe-cluster --name <name> --query cluster.platformVersion
):platformVersion": "eks.5"
aws eks describe-cluster --name <name> --query cluster.version
):"version": "1.13"
1.13.7
uname -a
):Linux ip-10-190-21-242.ts-sandbox.cloud 4.14.146-119.123.amzn2.x86_64 Template is missing source_ami_id in the variables section #1 SMP Mon Sep 23 16:58:43 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
cat /etc/eks/release
on a node):BASE_AMI_ID="ami-077381babe7660807"
BUILD_TIME="Mon Oct 7 21:36:57 UTC 2019"
BUILD_KERNEL="4.14.138-114.102.amzn2.x86_64"
ARCH="x86_64"
The text was updated successfully, but these errors were encountered: