e2e-kops-aws-external-dns #1593007277936218112
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 2 succeeded |
| Started | |
| Elapsed | 11m57s |
| 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 ... I1116 22:26:53.143608 6082 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt I1116 22:26:53.145736 6082 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.26.0-alpha.2+v1.26.0-alpha.1-344-g6f2ded7fb2/linux/amd64/kops I1116 22:26:53.930927 6082 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 I1116 22:26:53.943165 6082 up.go:44] Cleaning up any leaked resources from previous cluster I1116 22:26:53.943265 6082 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/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 I1116 22:26:53.943310 6082 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/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 W1116 22:26:54.465446 6082 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I1116 22:26:54.465501 6082 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/kops delete cluster --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io --yes I1116 22:26:54.465520 6082 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/kops delete cluster --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io --yes I1116 22:26:54.500457 6117 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 I1116 22:26:54.982316 6082 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2022/11/16 22:26:54 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 22:26:54.997681 6082 http.go:37] curl https://ip.jsb.workers.dev I1116 22:26:55.102471 6082 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/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.26+43b7a253539a77 --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.238.19.183/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c6g.large I1116 22:26:55.102521 6082 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/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.26+43b7a253539a77 --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.238.19.183/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c6g.large I1116 22:26:55.135841 6128 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true I1116 22:26:55.154105 6128 create_cluster.go:836] Using SSH public key: /tmp/kops/e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io/id_ed25519.pub I1116 22:26:55.642636 6128 new_cluster.go:1294] Cloud Provider ID = aws ... skipping 561 lines ... I1116 22:27:35.836804 6082 up.go:251] /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/kops validate cluster --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io --count 10 --wait 15m0s I1116 22:27:35.836895 6082 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/kops validate cluster --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io --count 10 --wait 15m0s I1116 22:27:35.876947 6169 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true Validating cluster e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io W1116 22:27:36.966184 6169 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-aws-external-dns.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-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:27:47.018028 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:27:57.050307 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:28:07.099295 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:28:17.148240 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:28:27.199132 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:28:37.247197 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:28:47.286358 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:28:57.336194 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:29:07.370515 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:29:17.406731 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:29:27.447196 6169 validate_cluster.go:232] (will retry): cluster not yet healthy W1116 22:29:37.474745 6169 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-aws-external-dns.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-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:29:47.515997 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:29:57.568908 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:30:07.602039 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:30:17.645319 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:30:27.702855 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:30:37.741311 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:30:47.781280 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:30:57.826596 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:31:07.871313 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:31:17.915866 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:31:27.959678 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:31:37.995933 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:31:48.036159 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-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 W1116 22:31:58.082610 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-1a ... skipping 11 lines ... Pod kube-system/coredns-5697fdb75c-htrxp system-cluster-critical pod "coredns-5697fdb75c-htrxp" is pending Pod kube-system/coredns-autoscaler-5c8bfbc6f6-59gbw system-cluster-critical pod "coredns-autoscaler-5c8bfbc6f6-59gbw" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-24qx6 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-24qx6" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-gvpsl system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-gvpsl" is pending Pod kube-system/ebs-csi-node-q88c2 system-node-critical pod "ebs-csi-node-q88c2" is pending Validation Failed W1116 22:32:09.683732 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-1a ... skipping 11 lines ... Pod kube-system/coredns-5697fdb75c-htrxp system-cluster-critical pod "coredns-5697fdb75c-htrxp" is pending Pod kube-system/coredns-autoscaler-5c8bfbc6f6-59gbw system-cluster-critical pod "coredns-autoscaler-5c8bfbc6f6-59gbw" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-24qx6 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-24qx6" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-gvpsl system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-gvpsl" is pending Pod kube-system/ebs-csi-node-q88c2 system-node-critical pod "ebs-csi-node-q88c2" is pending Validation Failed W1116 22:32:20.867532 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-1a ... skipping 11 lines ... Pod kube-system/coredns-5697fdb75c-htrxp system-cluster-critical pod "coredns-5697fdb75c-htrxp" is pending Pod kube-system/coredns-autoscaler-5c8bfbc6f6-59gbw system-cluster-critical pod "coredns-autoscaler-5c8bfbc6f6-59gbw" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-24qx6 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-24qx6" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-gvpsl system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-gvpsl" is pending Pod kube-system/ebs-csi-node-q88c2 system-node-critical pod "ebs-csi-node-q88c2" is pending Validation Failed W1116 22:32:32.146971 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-1a ... skipping 10 lines ... Pod kube-system/coredns-5697fdb75c-htrxp system-cluster-critical pod "coredns-5697fdb75c-htrxp" is pending Pod kube-system/coredns-autoscaler-5c8bfbc6f6-59gbw system-cluster-critical pod "coredns-autoscaler-5c8bfbc6f6-59gbw" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-24qx6 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-24qx6" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-gvpsl system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-gvpsl" is pending Pod kube-system/ebs-csi-node-q88c2 system-node-critical pod "ebs-csi-node-q88c2" is pending Validation Failed W1116 22:32:43.333407 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-1a ... skipping 12 lines ... Pod kube-system/coredns-5697fdb75c-htrxp system-cluster-critical pod "coredns-5697fdb75c-htrxp" is pending Pod kube-system/coredns-autoscaler-5c8bfbc6f6-59gbw system-cluster-critical pod "coredns-autoscaler-5c8bfbc6f6-59gbw" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-24qx6 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-24qx6" is pending Pod kube-system/ebs-csi-controller-6c9c7d7748-gvpsl system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-gvpsl" is pending Pod kube-system/ebs-csi-node-r6dps system-node-critical pod "ebs-csi-node-r6dps" is pending Validation Failed W1116 22:32:54.512788 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-1a ... skipping 20 lines ... Pod kube-system/ebs-csi-controller-6c9c7d7748-gvpsl system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-gvpsl" is pending Pod kube-system/ebs-csi-node-678wt system-node-critical pod "ebs-csi-node-678wt" is pending Pod kube-system/ebs-csi-node-bdvrf system-node-critical pod "ebs-csi-node-bdvrf" is pending Pod kube-system/ebs-csi-node-f7bfm system-node-critical pod "ebs-csi-node-f7bfm" is pending Pod kube-system/ebs-csi-node-r6dps system-node-critical pod "ebs-csi-node-r6dps" is pending Validation Failed W1116 22:33:05.639671 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-1a ... skipping 17 lines ... Pod kube-system/ebs-csi-controller-6c9c7d7748-gvpsl system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-gvpsl" is pending Pod kube-system/ebs-csi-node-678wt system-node-critical pod "ebs-csi-node-678wt" is pending Pod kube-system/ebs-csi-node-bdvrf system-node-critical pod "ebs-csi-node-bdvrf" is pending Pod kube-system/ebs-csi-node-f7bfm system-node-critical pod "ebs-csi-node-f7bfm" is pending Pod kube-system/ebs-csi-node-r6dps system-node-critical pod "ebs-csi-node-r6dps" is pending Validation Failed W1116 22:33:16.783142 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-1a ... skipping 13 lines ... Pod kube-system/ebs-csi-controller-6c9c7d7748-gvpsl system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-gvpsl" is pending Pod kube-system/ebs-csi-node-678wt system-node-critical pod "ebs-csi-node-678wt" is pending Pod kube-system/ebs-csi-node-bdvrf system-node-critical pod "ebs-csi-node-bdvrf" is pending Pod kube-system/ebs-csi-node-f7bfm system-node-critical pod "ebs-csi-node-f7bfm" is pending Pod kube-system/ebs-csi-node-r6dps system-node-critical pod "ebs-csi-node-r6dps" is pending Validation Failed W1116 22:33:27.992364 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-1a ... skipping 7 lines ... VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-controller-6c9c7d7748-24qx6 system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-24qx6" is not ready (ebs-plugin) Pod kube-system/ebs-csi-controller-6c9c7d7748-gvpsl system-cluster-critical pod "ebs-csi-controller-6c9c7d7748-gvpsl" is not ready (ebs-plugin) Validation Failed W1116 22:33:39.134934 6169 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-west-1a Master c6g.large 1 1 us-west-1a nodes-us-west-1a Node t4g.medium 4 4 us-west-1a ... skipping 141 lines ... i-0e71f575f64f08b61 master True Your cluster e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io is ready I1116 22:35:31.293899 6082 up.go:105] cluster reported as up I1116 22:35:31.293980 6082 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 I1116 22:35:31.316577 6179 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true F1116 22:35:33.834477 6179 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 22:35:33.838929 6082 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/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 I1116 22:35:33.838988 6082 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/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 I1116 22:36:06.461622 6082 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/kops get cluster --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io -o yaml I1116 22:36:06.461675 6082 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/kops get cluster --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io -o yaml I1116 22:36:07.015509 6082 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/kops get instancegroups --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io -o yaml I1116 22:36:07.015557 6082 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/85c07073-65fd-11ed-8638-926075b70450/kops get instancegroups --name e2e-e2e-kops-aws-external-dns.test-cncf-aws.k8s.io -o yaml ... skipping 265 lines ... route-table:rtb-0b0516d984928c4e9 ok vpc:vpc-039f04b1948a65a83 ok dhcp-options:dopt-0428f17ecdb9a7f26 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