e2e-kops-grid-cilium-amzn2-k22-ko23-docker #1524988532899188736
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 9m14s |
| Revision | master |
... skipping 153 lines ... I0513 05:44:25.673922 5671 common.go:152] Using cluster name: I0513 05:44:25.673997 5671 http.go:37] curl https://storage.googleapis.com/kubernetes-release/release/stable-1.22.txt I0513 05:44:25.729103 5671 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.23/latest-ci-updown-green.txt I0513 05:44:25.754687 5671 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.23.3+v1.23.2-2-g459c375b0b/linux/amd64/kops I0513 05:44:26.489112 5671 up.go:44] Cleaning up any leaked resources from previous cluster I0513 05:44:26.489389 5671 dumplogs.go:45] /logs/artifacts/88b7776f-d27f-11ec-b40b-862e9d6d5e5e/kops toolbox dump --name e2e-e2e-kops-grid-cilium-amzn2-k22-ko23-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-amzn2-k22-ko23-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user W0513 05:44:26.976900 5671 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0513 05:44:26.976949 5671 down.go:48] /logs/artifacts/88b7776f-d27f-11ec-b40b-862e9d6d5e5e/kops delete cluster --name e2e-e2e-kops-grid-cilium-amzn2-k22-ko23-docker.test-cncf-aws.k8s.io --yes I0513 05:44:26.996377 5704 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true I0513 05:44:26.996466 5704 featureflag.go:162] FeatureFlag "AlphaAllowGCE"=true Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-amzn2-k22-ko23-docker.test-cncf-aws.k8s.io" not found I0513 05:44:27.463027 5671 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2022/05/13 05:44:27 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 I0513 05:44:27.474940 5671 http.go:37] curl https://ip.jsb.workers.dev I0513 05:44:27.564266 5671 up.go:156] /logs/artifacts/88b7776f-d27f-11ec-b40b-862e9d6d5e5e/kops create cluster --name e2e-e2e-kops-grid-cilium-amzn2-k22-ko23-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.9 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-amzn2-k22-ko23-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=amazon/amzn2-ami-kernel-5.10-hvm-2.0.20220426.0-x86_64-gp2 --channel=alpha --networking=cilium --container-runtime=docker --admin-access 34.134.227.164/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-2a --master-size c5.large I0513 05:44:27.583863 5714 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true I0513 05:44:27.583968 5714 featureflag.go:162] FeatureFlag "AlphaAllowGCE"=true I0513 05:44:27.607919 5714 create_cluster.go:843] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-amzn2-k22-ko23-docker.test-cncf-aws.k8s.io/id_ed25519.pub I0513 05:44:28.194499 5714 new_cluster.go:1102] Cloud Provider ID = aws ... skipping 519 lines ... I0513 05:44:58.802417 5671 up.go:240] /logs/artifacts/88b7776f-d27f-11ec-b40b-862e9d6d5e5e/kops validate cluster --name e2e-e2e-kops-grid-cilium-amzn2-k22-ko23-docker.test-cncf-aws.k8s.io --count 10 --wait 15m0s I0513 05:44:58.822046 5754 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true I0513 05:44:58.822145 5754 featureflag.go:162] FeatureFlag "AlphaAllowGCE"=true Validating cluster e2e-e2e-kops-grid-cilium-amzn2-k22-ko23-docker.test-cncf-aws.k8s.io W0513 05:44:59.889524 5754 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-grid-cilium-amzn2-k22-ko23-docker.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:45:09.934862 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:45:19.967826 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:45:30.004360 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:45:40.054006 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:45:50.094343 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:46:00.130352 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:46:10.184912 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:46:20.237608 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:46:30.270396 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:46:40.308842 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:46:50.348440 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:47:00.383163 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:47:10.420076 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:47:20.454584 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:47:30.491076 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:47:40.526945 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:47:50.562609 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:48:00.600552 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-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 master 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 W0513 05:48:10.634123 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 22 lines ... Pod kube-system/ebs-csi-node-2x788 system-node-critical pod "ebs-csi-node-2x788" is pending Pod kube-system/ebs-csi-node-dpqcd system-node-critical pod "ebs-csi-node-dpqcd" is pending Pod kube-system/ebs-csi-node-krkm7 system-node-critical pod "ebs-csi-node-krkm7" is pending Pod kube-system/ebs-csi-node-p6fqq system-node-critical pod "ebs-csi-node-p6fqq" is pending Pod kube-system/ebs-csi-node-tmhqw system-node-critical pod "ebs-csi-node-tmhqw" is pending Validation Failed W0513 05:48:22.642006 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 19 lines ... Pod kube-system/ebs-csi-node-2x788 system-node-critical pod "ebs-csi-node-2x788" is pending Pod kube-system/ebs-csi-node-dpqcd system-node-critical pod "ebs-csi-node-dpqcd" is pending Pod kube-system/ebs-csi-node-krkm7 system-node-critical pod "ebs-csi-node-krkm7" is pending Pod kube-system/ebs-csi-node-p6fqq system-node-critical pod "ebs-csi-node-p6fqq" is pending Pod kube-system/ebs-csi-node-tmhqw system-node-critical pod "ebs-csi-node-tmhqw" is pending Validation Failed W0513 05:48:34.116668 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 15 lines ... Pod kube-system/ebs-csi-node-2x788 system-node-critical pod "ebs-csi-node-2x788" is pending Pod kube-system/ebs-csi-node-dpqcd system-node-critical pod "ebs-csi-node-dpqcd" is pending Pod kube-system/ebs-csi-node-krkm7 system-node-critical pod "ebs-csi-node-krkm7" is pending Pod kube-system/ebs-csi-node-p6fqq system-node-critical pod "ebs-csi-node-p6fqq" is pending Pod kube-system/ebs-csi-node-tmhqw system-node-critical pod "ebs-csi-node-tmhqw" is pending Validation Failed W0513 05:48:45.544986 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 12 lines ... Pod kube-system/ebs-csi-controller-766997979d-bzlz7 system-cluster-critical pod "ebs-csi-controller-766997979d-bzlz7" is pending Pod kube-system/ebs-csi-node-2x788 system-node-critical pod "ebs-csi-node-2x788" is pending Pod kube-system/ebs-csi-node-krkm7 system-node-critical pod "ebs-csi-node-krkm7" is pending Pod kube-system/ebs-csi-node-p6fqq system-node-critical pod "ebs-csi-node-p6fqq" is pending Pod kube-system/ebs-csi-node-tmhqw system-node-critical pod "ebs-csi-node-tmhqw" is pending Validation Failed W0513 05:48:57.536514 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 8 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-56dd667f7c-59tdh system-cluster-critical pod "coredns-56dd667f7c-59tdh" is not ready (coredns) Pod kube-system/ebs-csi-node-2x788 system-node-critical pod "ebs-csi-node-2x788" is pending Pod kube-system/ebs-csi-node-tmhqw system-node-critical pod "ebs-csi-node-tmhqw" is pending Validation Failed W0513 05:49:09.072740 5754 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-2a Master c5.large 1 1 us-west-2a nodes-us-west-2a Node t3.medium 4 4 us-west-2a ... skipping 139 lines ... ip-172-20-50-178.us-west-2.compute.internal node True ip-172-20-54-122.us-west-2.compute.internal master True ip-172-20-54-167.us-west-2.compute.internal node True Your cluster e2e-e2e-kops-grid-cilium-amzn2-k22-ko23-docker.test-cncf-aws.k8s.io is ready I0513 05:51:03.914601 5671 up.go:102] cluster reported as up F0513 05:51:05.427137 5767 tester.go:454] failed to run ginkgo tester: failed to get kubectl package from published releases: failed to get latest release name: exit status 1 goroutine 1 [running]: k8s.io/klog/v2.stacks(0x1) /home/prow/go/pkg/mod/k8s.io/klog/v2@v2.60.1/klog.go:860 +0x8a k8s.io/klog/v2.(*loggingT).output(0x1dc2280, 0x3, 0x0, 0xc000572000, 0x1, {0x180d557?, 0x1?}, 0x1dc2aa0?, 0x0) /home/prow/go/pkg/mod/k8s.io/klog/v2@v2.60.1/klog.go:825 +0x686 k8s.io/klog/v2.(*loggingT).printfDepth(0x1dc2280, 0x1dc2aa0?, 0x0, {0x0, 0x0}, 0xc0005bff70?, {0x12943f8, 0x1f}, {0xc00054c0b0, 0x1, ...}) ... skipping 177 lines ... route-table:rtb-0cfcf03ce1f25d92d ok vpc:vpc-02d2eec6f2ec3cc82 ok dhcp-options:dopt-05df8d9d215b48b9c ok Deleted kubectl config for e2e-e2e-kops-grid-cilium-amzn2-k22-ko23-docker.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-grid-cilium-amzn2-k22-ko23-docker.test-cncf-aws.k8s.io" Error: exit status 255 + EXIT_VALUE=1 + set +o xtrace