e2e-kops-grid-kopeio-rhel8-k23-docker #1592929766283939840
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 2 succeeded |
| Started | |
| Elapsed | 13m28s |
| Revision | master |
exit status 255
from junit_runner.xml
Filter through log files | View test history on testgrid
kubetest2 Down
kubetest2 Up
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 171 lines ... I1116 17:20:25.348272 6301 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt I1116 17:20:25.350962 6301 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.26.0-alpha.2+v1.26.0-alpha.1-338-g6311f1b60c/linux/amd64/kops I1116 17:20:27.130541 6301 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io/id_ed25519 I1116 17:20:27.161142 6301 up.go:44] Cleaning up any leaked resources from previous cluster I1116 17:20:27.161438 6301 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/7eaec06a-65d2-11ed-8638-926075b70450/kops toolbox dump --name e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I1116 17:20:27.161585 6301 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/7eaec06a-65d2-11ed-8638-926075b70450/kops toolbox dump --name e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user W1116 17:20:27.767722 6301 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I1116 17:20:27.767839 6301 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/7eaec06a-65d2-11ed-8638-926075b70450/kops delete cluster --name e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io --yes I1116 17:20:27.767860 6301 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/7eaec06a-65d2-11ed-8638-926075b70450/kops delete cluster --name e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io --yes I1116 17:20:27.843957 6332 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io" not found I1116 17:20:28.351626 6301 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2022/11/16 17:20:28 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 I1116 17:20:28.367612 6301 http.go:37] curl https://ip.jsb.workers.dev I1116 17:20:28.493242 6301 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/7eaec06a-65d2-11ed-8638-926075b70450/kops create cluster --name e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.23.14 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=309956199498/RHEL-8.7.0_HVM-20221101-x86_64-0-Hourly2-GP2 --channel=alpha --networking=kopeio --container-runtime=docker --admin-access 35.232.226.60/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c5.large I1116 17:20:28.493316 6301 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/7eaec06a-65d2-11ed-8638-926075b70450/kops create cluster --name e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.23.14 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=309956199498/RHEL-8.7.0_HVM-20221101-x86_64-0-Hourly2-GP2 --channel=alpha --networking=kopeio --container-runtime=docker --admin-access 35.232.226.60/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c5.large I1116 17:20:28.555519 6342 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true I1116 17:20:28.598821 6342 create_cluster.go:836] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io/id_ed25519.pub I1116 17:20:29.194028 6342 new_cluster.go:1294] Cloud Provider ID = aws ... skipping 534 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 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 W1116 17:21:12.032801 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:21:22.075911 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:21:32.117677 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:21:42.211732 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:21:52.270323 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:22:02.320418 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:22:12.359894 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:22:22.419629 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:22:32.465492 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:22:42.513040 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:22:52.554822 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:23:02.595517 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:23:12.638510 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:23:22.685727 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:23:32.740868 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:23:42.778851 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:23:52.827190 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:24:02.869523 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:24:12.913327 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:24:22.968369 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:24:33.009198 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:24:43.057202 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:24:53.101267 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:25:03.154547 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:25:13.192675 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:25:23.236031 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:25:33.279718 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:25:43.319393 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:25:53.366369 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a 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 W1116 17:26:03.419608 6380 validate_cluster.go:232] (will retry): cluster not yet healthy W1116 17:26:43.457467 6380 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a NODE STATUS ... skipping 5 lines ... ip-172-20-55-234.us-west-1.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-node-fknsl system-node-critical pod "ebs-csi-node-fknsl" is not ready (ebs-plugin) Validation Failed W1116 17:26:55.157830 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a ... skipping 6 lines ... ip-172-20-55-234.us-west-1.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/kube-proxy-ip-172-20-50-19.us-west-1.compute.internal system-node-critical pod "kube-proxy-ip-172-20-50-19.us-west-1.compute.internal" is pending Validation Failed W1116 17:27:06.427876 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a ... skipping 6 lines ... ip-172-20-55-234.us-west-1.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/kube-proxy-ip-172-20-41-223.us-west-1.compute.internal system-node-critical pod "kube-proxy-ip-172-20-41-223.us-west-1.compute.internal" is pending Validation Failed W1116 17:27:17.622199 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a ... skipping 6 lines ... ip-172-20-55-234.us-west-1.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/kube-proxy-ip-172-20-43-174.us-west-1.compute.internal system-node-critical pod "kube-proxy-ip-172-20-43-174.us-west-1.compute.internal" is pending Validation Failed W1116 17:27:28.814073 6380 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c5.large 1 1 us-west-1a nodes-us-west-1a Node t3.medium 4 4 us-west-1a ... skipping 141 lines ... ip-172-20-55-234.us-west-1.compute.internal node True Your cluster e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io is ready I1116 17:29:20.950063 6301 up.go:105] cluster reported as up I1116 17:29:20.950122 6301 local.go:42] ⚙️ /home/prow/go/bin/kubetest2-tester-kops --ginkgo-args=--debug --test-args=-test.timeout=60m -num-nodes=0 --test-package-marker=stable-1.23.txt --parallel=25 I1116 17:29:20.970478 6390 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true F1116 17:29:23.775236 6390 tester.go:477] failed to run ginkgo tester: failed to get kubectl package from published releases: failed to get latest release name: exit status 1 I1116 17:29:23.777804 6301 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/7eaec06a-65d2-11ed-8638-926075b70450/kops toolbox dump --name e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I1116 17:29:23.777843 6301 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/7eaec06a-65d2-11ed-8638-926075b70450/kops toolbox dump --name e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I1116 17:29:57.704647 6301 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/7eaec06a-65d2-11ed-8638-926075b70450/kops get cluster --name e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io -o yaml I1116 17:29:57.704683 6301 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/7eaec06a-65d2-11ed-8638-926075b70450/kops get cluster --name e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io -o yaml I1116 17:29:58.216018 6301 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/7eaec06a-65d2-11ed-8638-926075b70450/kops get instancegroups --name e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io -o yaml I1116 17:29:58.216068 6301 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/7eaec06a-65d2-11ed-8638-926075b70450/kops get instancegroups --name e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io -o yaml ... skipping 238 lines ... route-table:rtb-090102c33c9408f13 ok vpc:vpc-0cfc243b7646b9604 ok dhcp-options:dopt-0246a697410bb3042 ok Deleted kubectl config for e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-grid-kopeio-rhel8-k23-docker.test-cncf-aws.k8s.io" Error: exit status 255 + EXIT_VALUE=1 + set +o xtrace