e2e-kops-aws-distro-ubuntu1804 #1619308896101339136
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 24m26s |
| Revision | master |
exit status 1
from junit_runner.xml
Filter through log files | View test history on testgrid
kubetest2 Down
... skipping 135 lines ... I0128 12:20:38.042698 5572 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt I0128 12:20:38.044888 5572 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.27.0-alpha.2+v1.27.0-alpha.1-278-g57e9fdd860/linux/amd64/kops I0128 12:20:38.700338 5572 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io/id_ed25519 I0128 12:20:38.715446 5572 up.go:44] Cleaning up any leaked resources from previous cluster I0128 12:20:38.715614 5572 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/da7f4307-9f05-11ed-9a0c-f25a29267a91/kops toolbox dump --name e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I0128 12:20:38.715637 5572 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/da7f4307-9f05-11ed-9a0c-f25a29267a91/kops toolbox dump --name e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu Error: Cluster.kops.k8s.io "e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io" not found W0128 12:20:39.249732 5572 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0128 12:20:39.249801 5572 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/da7f4307-9f05-11ed-9a0c-f25a29267a91/kops delete cluster --name e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io --yes I0128 12:20:39.249812 5572 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/da7f4307-9f05-11ed-9a0c-f25a29267a91/kops delete cluster --name e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io --yes Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io" not found I0128 12:20:39.808320 5572 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/01/28 12:20:39 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404 I0128 12:20:39.826650 5572 http.go:37] curl https://ip.jsb.workers.dev I0128 12:20:39.914443 5572 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/da7f4307-9f05-11ed-9a0c-f25a29267a91/kops create cluster --name e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.26.1 --ssh-public-key /tmp/kops/e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20230112 --channel=alpha --networking=cilium --container-runtime=containerd --discovery-store=s3://k8s-kops-prow/discovery --admin-access 34.121.205.196/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large I0128 12:20:39.914541 5572 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/da7f4307-9f05-11ed-9a0c-f25a29267a91/kops create cluster --name e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.26.1 --ssh-public-key /tmp/kops/e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20230112 --channel=alpha --networking=cilium --container-runtime=containerd --discovery-store=s3://k8s-kops-prow/discovery --admin-access 34.121.205.196/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large I0128 12:20:39.967712 5613 create_cluster.go:882] Using SSH public key: /tmp/kops/e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io/id_ed25519.pub I0128 12:20:40.467734 5613 new_cluster.go:1338] Cloud Provider ID: "aws" I0128 12:20:41.956102 5613 subnets.go:185] Assigned CIDR 172.20.32.0/19 to subnet ap-northeast-2a ... skipping 553 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:21:20.741562 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:21:30.788115 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:21:40.828606 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:21:50.875487 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:22:00.932869 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:22:10.983010 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:22:21.023560 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:22:31.065059 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:22:41.101776 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:22:51.161710 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:23:01.207653 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:23:11.250665 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:23:21.290734 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:23:31.329967 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:23:41.370178 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:23:51.410996 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:24:01.462363 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:24:11.501438 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:24:21.552039 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:24:31.587359 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:24:41.639802 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:24:51.687560 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:25:01.726424 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:25:11.767037 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:25:21.811165 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:25:31.853297 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:25:41.894880 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:25:51.930180 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:26:01.981513 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:26:12.028322 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0128 12:26:22.062671 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 11 lines ... Pod kube-system/coredns-559769c974-6f59d system-cluster-critical pod "coredns-559769c974-6f59d" is pending Pod kube-system/coredns-autoscaler-7cb5c5b969-mppsv system-cluster-critical pod "coredns-autoscaler-7cb5c5b969-mppsv" is pending Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is pending Pod kube-system/ebs-csi-controller-7d4dc6ccf4-h2j57 system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-h2j57" is pending Pod kube-system/ebs-csi-node-jm427 system-node-critical pod "ebs-csi-node-jm427" is pending Validation Failed W0128 12:26:36.140579 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 23 lines ... Pod kube-system/ebs-csi-node-bkh5l system-node-critical pod "ebs-csi-node-bkh5l" is pending Pod kube-system/ebs-csi-node-j8dbh system-node-critical pod "ebs-csi-node-j8dbh" is pending Pod kube-system/ebs-csi-node-jm427 system-node-critical pod "ebs-csi-node-jm427" is pending Pod kube-system/ebs-csi-node-kfcfc system-node-critical pod "ebs-csi-node-kfcfc" is pending Pod kube-system/ebs-csi-node-qqjqb system-node-critical pod "ebs-csi-node-qqjqb" is pending Validation Failed W0128 12:26:48.987134 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 18 lines ... Pod kube-system/ebs-csi-node-bkh5l system-node-critical pod "ebs-csi-node-bkh5l" is pending Pod kube-system/ebs-csi-node-j8dbh system-node-critical pod "ebs-csi-node-j8dbh" is pending Pod kube-system/ebs-csi-node-jm427 system-node-critical pod "ebs-csi-node-jm427" is pending Pod kube-system/ebs-csi-node-kfcfc system-node-critical pod "ebs-csi-node-kfcfc" is pending Pod kube-system/ebs-csi-node-qqjqb system-node-critical pod "ebs-csi-node-qqjqb" is pending Validation Failed W0128 12:27:02.035938 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 13 lines ... Pod kube-system/ebs-csi-controller-7d4dc6ccf4-h2j57 system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-h2j57" is pending Pod kube-system/ebs-csi-node-bkh5l system-node-critical pod "ebs-csi-node-bkh5l" is pending Pod kube-system/ebs-csi-node-j8dbh system-node-critical pod "ebs-csi-node-j8dbh" is pending Pod kube-system/ebs-csi-node-kfcfc system-node-critical pod "ebs-csi-node-kfcfc" is pending Pod kube-system/ebs-csi-node-qqjqb system-node-critical pod "ebs-csi-node-qqjqb" is pending Validation Failed W0128 12:27:14.942506 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 10 lines ... Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is pending Pod kube-system/ebs-csi-controller-7d4dc6ccf4-h2j57 system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-h2j57" is pending Pod kube-system/ebs-csi-node-bkh5l system-node-critical pod "ebs-csi-node-bkh5l" is pending Pod kube-system/ebs-csi-node-kfcfc system-node-critical pod "ebs-csi-node-kfcfc" is pending Pod kube-system/ebs-csi-node-qqjqb system-node-critical pod "ebs-csi-node-qqjqb" is pending Validation Failed W0128 12:27:27.762661 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:27:40.627360 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:27:53.436760 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:28:06.285842 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:28:19.124423 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:28:31.982656 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:28:44.739792 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:28:57.564542 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-bkh5l system-node-critical pod "ebs-csi-node-bkh5l" is not ready (ebs-plugin) Validation Failed W0128 12:29:10.484564 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Pod kube-system/ebs-csi-node-bkh5l system-node-critical pod "ebs-csi-node-bkh5l" is not ready (ebs-plugin) Validation Failed W0128 12:29:23.411095 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:29:36.311719 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:29:49.261482 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:30:02.284364 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:30:15.191960 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:30:28.608007 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:30:41.454394 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:30:54.279831 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:31:07.170882 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:31:19.964882 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:31:32.808289 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:31:46.083499 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:31:58.900345 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:32:11.796702 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:32:24.698476 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:32:37.520465 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:32:50.366823 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:33:03.309990 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:33:16.246741 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:33:29.194015 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:33:42.034160 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:33:54.888691 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:34:07.788634 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:34:21.290629 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:34:34.143771 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:34:46.987654 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:34:59.791836 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:35:12.566965 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:35:25.430460 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (ebs-plugin) Validation Failed W0128 12:35:38.229716 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Node i-06a3d5beb4620cc67 node "i-06a3d5beb4620cc67" of role "node" is not ready Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (csi-attacher,csi-provisioner,csi-resizer,ebs-plugin,liveness-probe) Validation Failed W0128 12:35:51.095369 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (csi-attacher,csi-provisioner,csi-resizer,ebs-plugin,liveness-probe) Validation Failed W0128 12:36:03.919840 5655 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2a ControlPlane c5.large 1 1 ap-northeast-2a nodes-ap-northeast-2a Node t3.medium 4 4 ap-northeast-2a ... skipping 6 lines ... i-0ec2454a97e5d4b21 control-plane True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-7d4dc6ccf4-dvhwp system-cluster-critical pod "ebs-csi-controller-7d4dc6ccf4-dvhwp" is not ready (csi-attacher,ebs-plugin) Validation Failed W0128 12:36:16.771033 5655 validate_cluster.go:232] (will retry): cluster not yet healthy Error: validation failed: wait time exceeded during validation I0128 12:36:26.784497 5572 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/da7f4307-9f05-11ed-9a0c-f25a29267a91/kops toolbox dump --name e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I0128 12:36:26.784757 5572 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/da7f4307-9f05-11ed-9a0c-f25a29267a91/kops toolbox dump --name e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu 2023/01/28 12:36:51 Dumping node i-06a3d5beb4620cc67 2023/01/28 12:37:10 error dumping node i-06a3d5beb4620cc67: error executing command "sudo journalctl --output=cat -u kubelet.service": wait: remote command exited without exit status or exit signal 2023/01/28 12:37:10 error dumping node i-06a3d5beb4620cc67: error executing command "sudo journalctl --output=cat -u containerd.service": error creating ssh session: EOF 2023/01/28 12:37:10 error dumping node i-06a3d5beb4620cc67: error executing command "sudo journalctl --output=cat -u kops-configuration.service": error creating ssh session: EOF 2023/01/28 12:37:10 error dumping node i-06a3d5beb4620cc67: error executing command "sudo iptables -t nat --list-rules": error creating ssh session: EOF 2023/01/28 12:37:10 error dumping node i-06a3d5beb4620cc67: error executing command "sudo iptables -t filter --list-rules": error creating ssh session: EOF 2023/01/28 12:37:10 error dumping node i-06a3d5beb4620cc67: error reading /var/log: error listing "/var/log": error creating ssh session: EOF 2023/01/28 12:37:10 error dumping node i-06a3d5beb4620cc67: error executing command "if command -v kubectl &> /dev/null; then kubectl logs -n kube-system --all-containers -l \"k8s-app=external-dns\"; fi": error creating ssh session: EOF 2023/01/28 12:37:10 error dumping node i-06a3d5beb4620cc67: error executing command "if command -v kubectl &> /dev/null; then kubectl logs -n kube-system --all-containers -l \"k8s-app=dns-controller\"; fi": error creating ssh session: EOF 2023/01/28 12:37:10 error dumping node i-06a3d5beb4620cc67: error executing command "cat /etc/hosts": error creating ssh session: EOF 2023/01/28 12:37:10 error dumping node i-06a3d5beb4620cc67: error executing command "sysctl -a": error creating ssh session: EOF 2023/01/28 12:37:10 error closing connection: close tcp 10.60.161.31:34876->3.36.122.218:22: use of closed network connection 2023/01/28 12:37:10 Dumping node i-0b1d95a1c8b298670 2023/01/28 12:37:18 Dumping node i-0c005599ee0426e3b 2023/01/28 12:37:27 Dumping node i-0ebaa1673f398a3f1 2023/01/28 12:37:36 Dumping node i-0ec2454a97e5d4b21 I0128 12:37:48.221136 5572 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/da7f4307-9f05-11ed-9a0c-f25a29267a91/kops get cluster --name e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io -o yaml I0128 12:37:48.221305 5572 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/da7f4307-9f05-11ed-9a0c-f25a29267a91/kops get cluster --name e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io -o yaml ... skipping 535 lines ... route-table:rtb-0af04982d3c2baf2e ok vpc:vpc-0b742d7f82675c061 ok dhcp-options:dopt-053ab5e0364f712cf ok Deleted kubectl config for e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-aws-distro-ubuntu1804.test-cncf-aws.k8s.io" Error: exit status 1 + EXIT_VALUE=1 + set +o xtrace