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
I can see that the Control Plane is updated to 1.21 version. However, the eks_updater script is still running. I initiated the process some 2 hours ago and the Control Plane is running now the specified version.
I could see that the script is stuck at the update AddOn stage. Below is the last message on the CW logs
The Addons Found = ['aws-load-balancer-controller-6db9694d6b-58gcd', 'aws-load-balancer-controller-6db9694d6b-pmpsb', 'aws-node-5t9x9', 'aws-node-rlkdt', 'aws-node-vr4df', 'coredns-765545c8b8-7zhsn', 'coredns-765545c8b8-jlr7w', 'kube-proxy-b9gtd', 'kube-proxy-kbjvf', 'kube-proxy-x4gzt', 'metrics-server-9f459d97b-wqrcn']
Here is what i see on my Command line from where i ran the Python Updater script.
The Cluster eksworkshop-eksctl is Still Updating to 1.21 ..... 00:11:54.12
The eksworkshop-eksctl Updated to 1.21
The Time Taken For the Cluster to Upgrade 00:12:20.41
The add-ons Update has been initiated....
The Addons Found = aws-load-balancer-controller-6db9694d6b-58gcd aws-load-balancer-controller-6db9694d6b-pmpsb aws-node-5t9x9 aws-node-rlkdt aws-node-vr4df coredns-765545c8b8-7zhsn coredns-765545c8b8-jlr7w kube-proxy-b9gtd kube-proxy-kbjvf kube-proxy-x4gzt metrics-server-9f459d97b-wqrcn
aws-node-5t9x9 Current Version = v1.7.5-eksbuild.1 Updating To = v1.9.3
Total Pods With aws-node = 3
old vpc cni Pod aws-node-5t9x9 new vpc cni aws-node-xq957
aws-node-rlkdt Current Version = v1.7.5-eksbuild.1 Updating To = v1.9.3
Total Pods With aws-node = 3
old vpc cni Pod aws-node-rlkdt new vpc cni aws-node-xq957
aws-node-vr4df Current Version = v1.7.5-eksbuild.1 Updating To = v1.9.3
Total Pods With aws-node = 3
old vpc cni Pod aws-node-vr4df new vpc cni aws-node-5v8dr
coredns-765545c8b8-7zhsn Current Version = v1.8.3-eksbuild.1 Updating To = v1.8.4-eksbuild.1
Total Pods With kube-dns = 3
old CoreDNs Pod coredns-765545c8b8-7zhsn new CoreDnsPod coredns-59d47d99dc-xxvs5
coredns-765545c8b8-jlr7w Current Version = v1.8.3-eksbuild.1 Updating To = v1.8.4-eksbuild.1
Exception in thread Thread-4:
Traceback (most recent call last):
File "/usr/lib64/python3.7/threading.py", line 926, in _bootstrap_inner
self.run()
File "/home/ec2-user/environment/K8s-Manifest/EKS-Playground/UpdateCluster/amazon-eks-one-click-cluster-upgrade/eksupdate/src/k8s_client.py", line 26, in run
x=addon_status(cluster_name=cluster_name,new_pod_name=new_pod_name,podName=podName,regionName=regionName,nameSpace=nameSpace)
File "/home/ec2-user/environment/K8s-Manifest/EKS-Playground/UpdateCluster/amazon-eks-one-click-cluster-upgrade/eksupdate/src/k8s_client.py", line 219, in addon_status
if response.status.container_statuses[0].ready and response.status.container_statuses[0].started:
TypeError: 'NoneType' object is not subscriptable
Total Pods With kube-dns = 3
old CoreDNs Pod coredns-765545c8b8-jlr7w new CoreDnsPod coredns-59d47d99dc-xxvs5
kube-proxy-b9gtd Current Version = v1.20.7-eksbuild.1 Updating To = v1.21.2-eksbuild.2
Exception in thread Thread-5:
Traceback (most recent call last):
File "/usr/lib64/python3.7/threading.py", line 926, in _bootstrap_inner
self.run()
File "/home/ec2-user/environment/K8s-Manifest/EKS-Playground/UpdateCluster/amazon-eks-one-click-cluster-upgrade/eksupdate/src/k8s_client.py", line 26, in run
x=addon_status(cluster_name=cluster_name,new_pod_name=new_pod_name,podName=podName,regionName=regionName,nameSpace=nameSpace)
File "/home/ec2-user/environment/K8s-Manifest/EKS-Playground/UpdateCluster/amazon-eks-one-click-cluster-upgrade/eksupdate/src/k8s_client.py", line 219, in addon_status
if response.status.container_statuses[0].ready and response.status.container_statuses[0].started:
TypeError: 'NoneType' object is not subscriptable
Total Pods With kube-proxy = 3
old KubProxy Pod kube-proxy-b9gtd new KubeProxyPod kube-proxy-jh955
kube-proxy-kbjvf Current Version = v1.20.7-eksbuild.1 Updating To = v1.21.2-eksbuild.2
Total Pods With kube-proxy = 3
old KubProxy Pod kube-proxy-kbjvf new KubeProxyPod kube-proxy-tkd98
kube-proxy-x4gzt Current Version = v1.20.7-eksbuild.1 Updating To = v1.21.2-eksbuild.2
Total Pods With kube-proxy = 3
old KubProxy Pod kube-proxy-x4gzt new KubeProxyPod kube-proxy-tkd98
I took the strace and lsof O/p of this process and seems like it is waiting on
I tried to update my EKS cluster using the given script. Below are the steps that I did on my Cloud9 Instance.
I can see that the Control Plane is updated to 1.21 version. However, the eks_updater script is still running. I initiated the process some 2 hours ago and the Control Plane is running now the specified version.
I could see that the script is stuck at the update AddOn stage. Below is the last message on the CW logs
The Addons Found = ['aws-load-balancer-controller-6db9694d6b-58gcd', 'aws-load-balancer-controller-6db9694d6b-pmpsb', 'aws-node-5t9x9', 'aws-node-rlkdt', 'aws-node-vr4df', 'coredns-765545c8b8-7zhsn', 'coredns-765545c8b8-jlr7w', 'kube-proxy-b9gtd', 'kube-proxy-kbjvf', 'kube-proxy-x4gzt', 'metrics-server-9f459d97b-wqrcn']
Here is what i see on my Command line from where i ran the Python Updater script.
I took the strace and lsof O/p of this process and seems like it is waiting on
Why is the update script stuck?
The text was updated successfully, but these errors were encountered: