e2e-kops-grid-calico-flatcar-k22-docker #1525540490919809024
Recent runs || View in Spyglass
ERROR: (gcloud.auth.activate-service-account) There was a problem refreshing your current auth tokens: ('invalid_grant: Invalid JWT Signature.', {'error': 'invalid_grant', 'error_description': 'Invalid JWT Signature.'}) Please run: $ gcloud auth login to obtain new credentials. ... skipping 160 lines ... I0514 18:17:45.342472 5698 common.go:152] Using cluster name: I0514 18:17:45.342512 5698 http.go:37] curl https://storage.googleapis.com/kubernetes-release/release/stable-1.22.txt I0514 18:17:45.403515 5698 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt I0514 18:17:45.405408 5698 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.24.0-alpha.5+v1.24.0-alpha.4-38-gcccfc0e954/linux/amd64/kops I0514 18:17:45.988401 5698 up.go:44] Cleaning up any leaked resources from previous cluster I0514 18:17:45.988497 5698 dumplogs.go:45] /logs/artifacts/eeab4ecf-d3b1-11ec-b161-3e13eb6fa348/kops toolbox dump --name e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user core W0514 18:17:46.462164 5698 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0514 18:17:46.462219 5698 down.go:48] /logs/artifacts/eeab4ecf-d3b1-11ec-b161-3e13eb6fa348/kops delete cluster --name e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io --yes I0514 18:17:46.481808 5731 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true I0514 18:17:46.481912 5731 featureflag.go:164] FeatureFlag "AlphaAllowGCE"=true Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io" not found I0514 18:17:46.918906 5698 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2022/05/14 18:17:46 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 I0514 18:17:46.926933 5698 http.go:37] curl https://ip.jsb.workers.dev I0514 18:17:47.041727 5698 up.go:156] /logs/artifacts/eeab4ecf-d3b1-11ec-b161-3e13eb6fa348/kops create cluster --name e2e-e2e-kops-grid-calico-flatcar-k22-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-calico-flatcar-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=075585003325/Flatcar-stable-3139.2.1-hvm --channel=alpha --networking=calico --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 I0514 18:17:47.061259 5741 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true I0514 18:17:47.061348 5741 featureflag.go:164] FeatureFlag "AlphaAllowGCE"=true I0514 18:17:47.087816 5741 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub I0514 18:17:47.550580 5741 new_cluster.go:1168] Cloud Provider ID = aws ... skipping 531 lines ... I0514 18:18:23.165851 5698 up.go:240] /logs/artifacts/eeab4ecf-d3b1-11ec-b161-3e13eb6fa348/kops validate cluster --name e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io --count 10 --wait 20m0s I0514 18:18:23.186541 5799 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true I0514 18:18:23.186631 5799 featureflag.go:164] FeatureFlag "AlphaAllowGCE"=true Validating cluster e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io W0514 18:18:24.272450 5799 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host W0514 18:18:34.307753 5799 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-grid-calico-flatcar-k22-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 W0514 18:18:44.359365 5799 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 W0514 18:18:54.398326 5799 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 W0514 18:19:04.429793 5799 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 W0514 18:19:14.467112 5799 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 W0514 18:19:24.513418 5799 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 W0514 18:19:34.542422 5799 validate_cluster.go:232] (will retry): cluster not yet healthy W0514 18:19:44.574541 5799 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-grid-calico-flatcar-k22-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 W0514 18:19:54.621634 5799 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 W0514 18:20:04.656962 5799 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 W0514 18:20:14.696802 5799 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 W0514 18:20:24.739099 5799 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 W0514 18:20:34.775030 5799 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 W0514 18:20:44.817253 5799 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 W0514 18:20:54.851140 5799 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 W0514 18:21:04.884626 5799 validate_cluster.go:232] (will retry): cluster not yet healthy W0514 18:21:14.918151 5799 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-grid-calico-flatcar-k22-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 W0514 18:21:24.953499 5799 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 W0514 18:21:34.987625 5799 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 W0514 18:21:45.021746 5799 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 W0514 18:21:55.052625 5799 validate_cluster.go:232] (will retry): cluster not yet healthy W0514 18:22:05.105426 5799 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp: lookup api.e2e-e2e-kops-grid-calico-flatcar-k22-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 ... skipping 14 lines ... Pod kube-system/coredns-autoscaler-6fccfff6b-pnmfj system-cluster-critical pod "coredns-autoscaler-6fccfff6b-pnmfj" is pending Pod kube-system/ebs-csi-node-8bpkj system-node-critical pod "ebs-csi-node-8bpkj" is pending Pod kube-system/ebs-csi-node-dw7xd system-node-critical pod "ebs-csi-node-dw7xd" is pending Pod kube-system/ebs-csi-node-jktzl system-node-critical pod "ebs-csi-node-jktzl" is pending Pod kube-system/ebs-csi-node-zgt9f system-node-critical pod "ebs-csi-node-zgt9f" is pending Validation Failed W0514 18:22:17.180884 5799 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/coredns-autoscaler-6fccfff6b-pnmfj system-cluster-critical pod "coredns-autoscaler-6fccfff6b-pnmfj" is pending Pod kube-system/ebs-csi-node-8bpkj system-node-critical pod "ebs-csi-node-8bpkj" is pending Pod kube-system/ebs-csi-node-dw7xd system-node-critical pod "ebs-csi-node-dw7xd" is pending Pod kube-system/ebs-csi-node-jktzl system-node-critical pod "ebs-csi-node-jktzl" is pending Pod kube-system/ebs-csi-node-zgt9f system-node-critical pod "ebs-csi-node-zgt9f" is pending Validation Failed W0514 18:22:29.214846 5799 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-9989cc795-4w5qn system-cluster-critical pod "coredns-9989cc795-4w5qn" is pending Pod kube-system/ebs-csi-node-8bpkj system-node-critical pod "ebs-csi-node-8bpkj" is pending Pod kube-system/kube-proxy-ip-172-20-54-161.us-west-2.compute.internal system-node-critical pod "kube-proxy-ip-172-20-54-161.us-west-2.compute.internal" is pending Validation Failed W0514 18:22:40.567315 5799 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-56-15.us-west-2.compute.internal node True ip-172-20-57-25.us-west-2.compute.internal node True ip-172-20-60-111.us-west-2.compute.internal master True Your cluster e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io is ready I0514 18:24:35.548068 5698 up.go:102] cluster reported as up F0514 18:24:37.494950 5809 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, 0xc00052bb20, 0x1, {0x180d557?, 0x1?}, 0xc000100000?, 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}, 0xc00079ff70?, {0x12943f8, 0x1f}, {0xc000574620, 0x1, ...}) ... skipping 455 lines ... route-table:rtb-0ef9128fcd92d7f47 ok vpc:vpc-0263e90d51828e267 ok dhcp-options:dopt-0f646dcbef7cf2bee ok Deleted kubectl config for e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io" Error: exit status 255 + EXIT_VALUE=1 + set +o xtrace