Ubuntu AMI (ami-06114b38b9273f7c2) failed to join cluster in UAE region due to 403 on pause container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
High
|
Thomas Bechtold |
Bug Description
Customer is working on a POC to test EKS in the me-central-1 region and they shared EC2 instances based of the Ubuntu EKS Optimized AMI failed to join cluster when using managed node groups.
I've been able to repeat and identify the issue with the following steps:
1. Created a new EKS cluster in me-central-1 with the following cluster configuration:
---
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
name: uae-poc-test
region: me-central-1
managedNodeGroups:
- name: custom-ng-2
minSize: 1
maxSize: 4
amiFamily: Ubuntu2004
2. The CloudFormation stack rolls back due to Ubuntu node unable to join cluster. It used this AMI: ami-06114b38b92
3. Looking the Cloud init logs we can see the following 403 error on the pause container:
Cloud-init v. 22.4.2-
eksctl: running /etc/eks/bootstrap
Aliasing EKS k8s snap commands
Added:
- kubelet-eks.kubelet as kubelet
Added:
- kubectl-eks.kubectl as kubectl
Stopping k8s daemons until configured
Stopped.
Cluster "kubernetes" set.
Container runtime is containerd
Attempt 5 of 5
ctr: failed to resolve reference "602401143452.
Based on the Amazon container image registries (https:/
---
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
name: uae-poc-test
region: me-central-1
managedNodeGroups:
- name: custom-ng-3
ami: ami-06114b38b92
minSize: 1
maxSize: 4
overrideBoo
#!/bin/bash
/
affects: | compiz-plugins-main (Ubuntu) → cloud-images |
Changed in cloud-images: | |
status: | New → Confirmed |
assignee: | nobody → Thomas Bechtold (toabctl) |
importance: | Undecided → High |
status: | Confirmed → In Progress |
tags: | added: eks |
tags: | removed: eks |
Images with the serial 20230118 do fix that problem. Please let us know if you still have problems.