e2e-kops-aws-external-dns #1593128150231945216
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 2 succeeded |
| Started | |
| Elapsed | 14m11s |
| Revision | master |
exit status 255
from junit_runner.xml
Filter through log files | View test history on testgrid
kubetest2 Down
kubetest2 Up
... skipping 169 lines ... I1117 06:27:41.743150 6113 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt I1117 06:27:41.745823 6113 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.26.0-alpha.2+v1.26.0-alpha.1-348-gc592a02bb4/linux/amd64/kops I1117 06:27:42.535736 6113 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io/id_ed25519 I1117 06:27:42.543472 6113 up.go:44] Cleaning up any leaked resources from previous cluster I1117 06:27:42.543591 6113 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/9ebce868-6640-11ed-a804-ce2adf6da13d/kops toolbox dump --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I1117 06:27:42.543648 6113 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/9ebce868-6640-11ed-a804-ce2adf6da13d/kops toolbox dump --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu W1117 06:27:43.116113 6113 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I1117 06:27:43.116160 6113 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/9ebce868-6640-11ed-a804-ce2adf6da13d/kops delete cluster --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io --yes I1117 06:27:43.116173 6113 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/9ebce868-6640-11ed-a804-ce2adf6da13d/kops delete cluster --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io --yes I1117 06:27:43.149750 6147 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io" not found I1117 06:27:43.609195 6113 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2022/11/17 06:27:43 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 I1117 06:27:43.623697 6113 http.go:37] curl https://ip.jsb.workers.dev I1117 06:27:43.719731 6113 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/9ebce868-6640-11ed-a804-ce2adf6da13d/kops create cluster --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.27.0-alpha.0.28+3f823c0daa0021 --ssh-public-key /tmp/kops/e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-arm64-server-20221101.1 --channel=alpha --networking=cilium --container-runtime=containerd --override=cluster.spec.externalDNS.provider=external-dns --discovery-store=s3://k8s-kops-prow/discovery --admin-access 35.224.130.54/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones sa-east-1a --master-size c6g.large I1117 06:27:43.719772 6113 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/9ebce868-6640-11ed-a804-ce2adf6da13d/kops create cluster --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.27.0-alpha.0.28+3f823c0daa0021 --ssh-public-key /tmp/kops/e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-arm64-server-20221101.1 --channel=alpha --networking=cilium --container-runtime=containerd --override=cluster.spec.externalDNS.provider=external-dns --discovery-store=s3://k8s-kops-prow/discovery --admin-access 35.224.130.54/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones sa-east-1a --master-size c6g.large I1117 06:27:43.756423 6157 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true I1117 06:27:43.778533 6157 create_cluster.go:836] Using SSH public key: /tmp/kops/e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io/id_ed25519.pub I1117 06:27:44.256171 6157 new_cluster.go:1294] Cloud Provider ID = aws ... skipping 571 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:28:33.059848 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:28:43.097532 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:28:53.140000 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:29:03.187187 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:29:13.227793 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:29:23.266278 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:29:33.303028 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:29:43.341464 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:29:53.389811 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:30:03.430613 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:30:13.479339 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:30:23.524636 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:30:33.561837 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:30:43.616601 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:30:53.654985 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:31:03.699368 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:31:13.736168 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:31:23.771145 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:31:33.811068 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:31:43.849025 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:31:53.891540 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:32:03.942389 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:32:13.981047 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:32:24.025926 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:32:34.077584 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:32:44.115371 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:32:54.151724 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The external-dns 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, external-dns to launch, and DNS to propagate. The protokube container and external-dns 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 W1117 06:33:04.198772 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a ... skipping 11 lines ... Pod kube-system/coredns-5697fdb75c-k4r5s system-cluster-critical pod "coredns-5697fdb75c-k4r5s" is pending Pod kube-system/coredns-autoscaler-5c8bfbc6f6-dwlps system-cluster-critical pod "coredns-autoscaler-5c8bfbc6f6-dwlps" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-2psjz system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-2psjz" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-z85p5 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-z85p5" is pending Pod kube-system/ebs-csi-node-xhn7g system-node-critical pod "ebs-csi-node-xhn7g" is pending Validation Failed W1117 06:33:17.603691 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a ... skipping 11 lines ... Pod kube-system/coredns-5697fdb75c-k4r5s system-cluster-critical pod "coredns-5697fdb75c-k4r5s" is pending Pod kube-system/coredns-autoscaler-5c8bfbc6f6-dwlps system-cluster-critical pod "coredns-autoscaler-5c8bfbc6f6-dwlps" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-2psjz system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-2psjz" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-z85p5 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-z85p5" is pending Pod kube-system/ebs-csi-node-xhn7g system-node-critical pod "ebs-csi-node-xhn7g" is pending Validation Failed W1117 06:33:30.017853 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a ... skipping 11 lines ... Pod kube-system/coredns-5697fdb75c-k4r5s system-cluster-critical pod "coredns-5697fdb75c-k4r5s" is pending Pod kube-system/coredns-autoscaler-5c8bfbc6f6-dwlps system-cluster-critical pod "coredns-autoscaler-5c8bfbc6f6-dwlps" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-2psjz system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-2psjz" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-z85p5 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-z85p5" is pending Pod kube-system/ebs-csi-node-xhn7g system-node-critical pod "ebs-csi-node-xhn7g" is pending Validation Failed W1117 06:33:42.447092 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a ... skipping 10 lines ... Pod kube-system/coredns-5697fdb75c-k4r5s system-cluster-critical pod "coredns-5697fdb75c-k4r5s" is pending Pod kube-system/coredns-autoscaler-5c8bfbc6f6-dwlps system-cluster-critical pod "coredns-autoscaler-5c8bfbc6f6-dwlps" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-2psjz system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-2psjz" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-z85p5 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-z85p5" is pending Pod kube-system/ebs-csi-node-xhn7g system-node-critical pod "ebs-csi-node-xhn7g" is pending Validation Failed W1117 06:33:54.858091 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a ... skipping 9 lines ... Machine i-0d6de33d272d5593d machine "i-0d6de33d272d5593d" has not yet joined cluster Pod kube-system/coredns-5697fdb75c-k4r5s system-cluster-critical pod "coredns-5697fdb75c-k4r5s" is pending Pod kube-system/coredns-autoscaler-5c8bfbc6f6-dwlps system-cluster-critical pod "coredns-autoscaler-5c8bfbc6f6-dwlps" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-2psjz system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-2psjz" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-z85p5 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-z85p5" is pending Validation Failed W1117 06:34:07.240528 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a ... skipping 9 lines ... Machine i-0d6de33d272d5593d machine "i-0d6de33d272d5593d" has not yet joined cluster Pod kube-system/coredns-5697fdb75c-k4r5s system-cluster-critical pod "coredns-5697fdb75c-k4r5s" is pending Pod kube-system/coredns-autoscaler-5c8bfbc6f6-dwlps system-cluster-critical pod "coredns-autoscaler-5c8bfbc6f6-dwlps" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-2psjz system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-2psjz" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-z85p5 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-z85p5" is pending Validation Failed W1117 06:34:19.565866 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a ... skipping 21 lines ... Pod kube-system/ebs-csi-controller-6c9c7d7748-z85p5 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-z85p5" is pending Pod kube-system/ebs-csi-node-4llx6 system-node-critical pod "ebs-csi-node-4llx6" is pending Pod kube-system/ebs-csi-node-92bjg system-node-critical pod "ebs-csi-node-92bjg" is pending Pod kube-system/ebs-csi-node-kt4tr system-node-critical pod "ebs-csi-node-kt4tr" is pending Pod kube-system/ebs-csi-node-zj69t system-node-critical pod "ebs-csi-node-zj69t" is pending Validation Failed W1117 06:34:31.986059 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a ... skipping 17 lines ... Pod kube-system/ebs-csi-controller-6c9c7d7748-z85p5 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-z85p5" is pending Pod kube-system/ebs-csi-node-4llx6 system-node-critical pod "ebs-csi-node-4llx6" is pending Pod kube-system/ebs-csi-node-92bjg system-node-critical pod "ebs-csi-node-92bjg" is pending Pod kube-system/ebs-csi-node-kt4tr system-node-critical pod "ebs-csi-node-kt4tr" is pending Pod kube-system/ebs-csi-node-zj69t system-node-critical pod "ebs-csi-node-zj69t" is pending Validation Failed W1117 06:34:44.411582 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a ... skipping 13 lines ... Pod kube-system/ebs-csi-controller-6c9c7d7748-z85p5 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-z85p5" is pending Pod kube-system/ebs-csi-node-4llx6 system-node-critical pod "ebs-csi-node-4llx6" is pending Pod kube-system/ebs-csi-node-92bjg system-node-critical pod "ebs-csi-node-92bjg" is pending Pod kube-system/ebs-csi-node-kt4tr system-node-critical pod "ebs-csi-node-kt4tr" is pending Pod kube-system/ebs-csi-node-zj69t system-node-critical pod "ebs-csi-node-zj69t" is pending Validation Failed W1117 06:34:56.975443 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a ... skipping 12 lines ... Pod kube-system/ebs-csi-controller-6c9c7d7748-z85p5 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-z85p5" is pending Pod kube-system/ebs-csi-node-4llx6 system-node-critical pod "ebs-csi-node-4llx6" is pending Pod kube-system/ebs-csi-node-92bjg system-node-critical pod "ebs-csi-node-92bjg" is pending Pod kube-system/ebs-csi-node-kt4tr system-node-critical pod "ebs-csi-node-kt4tr" is pending Pod kube-system/ebs-csi-node-zj69t system-node-critical pod "ebs-csi-node-zj69t" is pending Validation Failed W1117 06:35:09.617020 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a ... skipping 8 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-6c9c7d7748-2psjz system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-2psjz" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-z85p5 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-z85p5" is pending Pod kube-system/ebs-csi-node-zj69t system-node-critical pod "ebs-csi-node-zj69t" is pending Validation Failed W1117 06:35:22.141864 6199 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-sa-east-1a Master c6g.large 1 1 sa-east-1a nodes-sa-east-1a Node t4g.medium 4 4 sa-east-1a ... skipping 141 lines ... i-0d6de33d272d5593d node True Your cluster e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io is ready I1117 06:37:27.153047 6113 up.go:105] cluster reported as up I1117 06:37:27.153226 6113 local.go:42] ⚙️ /home/prow/go/bin/kubetest2-tester-kops --ginkgo-args=--debug --test-args=-test.timeout=60m -num-nodes=0 --test-package-bucket=k8s-release-dev --test-package-dir=ci --test-package-marker=latest.txt --parallel=25 I1117 06:37:27.195193 6209 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true F1117 06:37:30.835910 6209 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 I1117 06:37:30.843619 6113 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/9ebce868-6640-11ed-a804-ce2adf6da13d/kops toolbox dump --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I1117 06:37:30.843729 6113 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/9ebce868-6640-11ed-a804-ce2adf6da13d/kops toolbox dump --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I1117 06:38:27.188510 6113 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/9ebce868-6640-11ed-a804-ce2adf6da13d/kops get cluster --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io -o yaml I1117 06:38:27.188593 6113 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/9ebce868-6640-11ed-a804-ce2adf6da13d/kops get cluster --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io -o yaml I1117 06:38:27.780643 6113 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/9ebce868-6640-11ed-a804-ce2adf6da13d/kops get instancegroups --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io -o yaml I1117 06:38:27.780737 6113 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/9ebce868-6640-11ed-a804-ce2adf6da13d/kops get instancegroups --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io -o yaml ... skipping 293 lines ... route-table:rtb-053b3ece9614c879e ok vpc:vpc-01186c4f44a824344 ok dhcp-options:dopt-0cc91464aadd78b42 ok Deleted kubectl config for e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io" Error: exit status 255 + EXIT_VALUE=1 + set +o xtrace