e2e-kops-aws-addon-resource-tracking #1596001725355921408
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 1 succeeded |
| Started | |
| Elapsed | 34m38s |
| Revision | master |
kubetest2 Down
... skipping 198 lines ... I1125 04:46:59.600002 6409 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/c6530656-6c7b-11ed-a6da-22215f11743a" I1125 04:46:59.603919 6409 app.go:128] ID for this run: "c6530656-6c7b-11ed-a6da-22215f11743a" I1125 04:46:59.604487 6409 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/id_ed25519 I1125 04:46:59.645298 6409 up.go:44] Cleaning up any leaked resources from previous cluster I1125 04:46:59.645417 6409 dumplogs.go:45] /tmp/kops.e50bnsKzl toolbox dump --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu I1125 04:46:59.645445 6409 local.go:42] ⚙️ /tmp/kops.e50bnsKzl toolbox dump --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu W1125 04:47:00.306512 6409 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I1125 04:47:00.306589 6409 down.go:48] /tmp/kops.e50bnsKzl delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1125 04:47:00.306611 6409 local.go:42] ⚙️ /tmp/kops.e50bnsKzl delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1125 04:47:00.343595 6433 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1125 04:47:00.345771 6433 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true error reading cluster configuration: Cluster.kops.k8s.io "e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io" not found I1125 04:47:00.977423 6409 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2022/11/25 04:47:00 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 I1125 04:47:00.994224 6409 http.go:37] curl https://ip.jsb.workers.dev I1125 04:47:01.127077 6409 up.go:167] /tmp/kops.e50bnsKzl create cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /tmp/kops/e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --override=cluster.spec.nodeTerminationHandler.enabled=true --admin-access 34.134.251.70/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large I1125 04:47:01.127112 6409 local.go:42] ⚙️ /tmp/kops.e50bnsKzl create cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --cloud aws --kubernetes-version 1.21.0 --ssh-public-key /tmp/kops/e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --override=cluster.spec.nodeTerminationHandler.enabled=true --admin-access 34.134.251.70/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large I1125 04:47:01.159903 6443 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1125 04:47:01.159999 6443 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1125 04:47:01.248931 6443 create_cluster.go:728] Using SSH public key: /tmp/kops/e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/id_ed25519.pub ... skipping 492 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 W1125 04:47:54.858425 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:48:04.891263 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:48:14.938881 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:48:24.978900 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:48:35.027762 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:48:45.074797 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:48:55.126993 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:49:05.168229 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:49:15.202297 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:49:25.244867 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:49:35.284146 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:49:45.325603 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:49:55.365435 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:50:05.411415 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:50:15.447062 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:50:25.496139 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:50:35.540890 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:50:45.585418 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:50:55.621532 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:51:05.661199 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:51:15.701102 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:51:25.739276 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:51:35.774826 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-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 W1125 04:51:45.811844 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-1a ... skipping 14 lines ... Pod kube-system/aws-node-termination-handler-97ddh system-node-critical pod "aws-node-termination-handler-97ddh" is pending Pod kube-system/aws-node-termination-handler-k26kp system-node-critical pod "aws-node-termination-handler-k26kp" is pending Pod kube-system/coredns-5dc785954d-6fdd6 system-cluster-critical pod "coredns-5dc785954d-6fdd6" is pending Pod kube-system/coredns-autoscaler-84d4cfd89c-wrcxz system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wrcxz" is pending Pod kube-system/kube-proxy-ip-172-20-37-30.ap-southeast-1.compute.internal system-node-critical pod "kube-proxy-ip-172-20-37-30.ap-southeast-1.compute.internal" is pending Validation Failed W1125 04:52:00.585811 6487 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-1a Master c5.large 1 1 ap-southeast-1a nodes-ap-southeast-1a Node t3.medium 4 4 ap-southeast-1a ... skipping 973 lines ... for cmd in "${commands[@]}"; do ... continue fi + if ! validate-hash "${file}" "${hash}"; then - if [[ -n "${hash}" ]] && ! validate-hash "${file}" "${hash}"; then echo "== Hash validation of ${url} failed. Retrying. ==" rm -f "${file}" else - if [[ -n "${hash}" ]]; then + echo "== Downloaded ${url} (SHA256 = ${hash}) ==" - echo "== Downloaded ${url} (SHA1 = ${hash}) ==" - else ... skipping 294 lines ... for cmd in "${commands[@]}"; do ... continue fi + if ! validate-hash "${file}" "${hash}"; then - if [[ -n "${hash}" ]] && ! validate-hash "${file}" "${hash}"; then echo "== Hash validation of ${url} failed. Retrying. ==" rm -f "${file}" else - if [[ -n "${hash}" ]]; then + echo "== Downloaded ${url} (SHA256 = ${hash}) ==" - echo "== Downloaded ${url} (SHA1 = ${hash}) ==" - else ... skipping 1136 lines ... WARNING: ignoring DaemonSet-managed Pods: kube-system/aws-node-termination-handler-qmnlj, kube-system/kops-controller-nvzf2 evicting pod kube-system/dns-controller-7fc66c4dd4-sngp7 I1125 04:55:02.087308 6585 instancegroups.go:681] Waiting for 5s for pods to stabilize after draining. I1125 04:55:07.087549 6585 instancegroups.go:598] Stopping instance "i-091591e23ae8c2cf7", node "ip-172-20-43-197.ap-southeast-1.compute.internal", in group "master-ap-southeast-1a.masters.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io" (this may take a while). I1125 04:55:07.482198 6585 instancegroups.go:443] waiting for 15s after terminating instance I1125 04:55:22.482603 6585 instancegroups.go:477] Validating the cluster. I1125 04:55:52.531432 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 04:56:52.564803 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 04:57:52.608520 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 04:58:52.642412 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 04:59:52.760398 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 05:00:52.797546 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 05:01:52.840274 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 05:02:52.879207 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 05:03:52.930743 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 05:04:52.969725 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 05:05:53.017317 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 05:06:53.056276 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 05:07:53.100738 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 05:08:53.135709 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 05:09:53.184659 6585 instancegroups.go:523] Cluster did not validate, will retry in "30s": error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. I1125 05:10:53.220165 6585 instancegroups.go:520] Cluster did not validate within deadline: error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.212.49.219:443: i/o timeout. E1125 05:10:53.220216 6585 instancegroups.go:482] Cluster did not validate within 15m0s Error: control-plane node not healthy after update, stopping rolling-update: "error validating cluster after terminating instance: cluster did not validate within a duration of \"15m0s\"" + kops-finish + kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --kops-root=/home/prow/go/src/k8s.io/kops --admin-access= --env=KOPS_FEATURE_FLAGS=SpecOverrideFlag --kops-binary-path=/tmp/kops.BKbYnq9Pf --down I1125 05:10:53.260913 6604 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true I1125 05:10:53.263755 6604 app.go:61] The files in RunDir shall not be part of Artifacts I1125 05:10:53.263887 6604 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts I1125 05:10:53.263956 6604 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/c6530656-6c7b-11ed-a6da-22215f11743a" ... skipping 17 lines ... Warning: Permanently added '54.179.220.12' (ECDSA) to the list of known hosts. I1125 05:14:49.672604 6604 dumplogs.go:257] ssh -i /tmp/kops/e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/id_ed25519 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ubuntu@54.179.220.12 -- rm -rf /tmp/cluster-info I1125 05:14:49.672758 6604 local.go:42] ⚙️ ssh -i /tmp/kops/e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/id_ed25519 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ubuntu@54.179.220.12 -- rm -rf /tmp/cluster-info Warning: Permanently added '54.179.220.12' (ECDSA) to the list of known hosts. I1125 05:14:52.470057 6604 dumplogs.go:127] kubectl --request-timeout 5s get csinodes --all-namespaces --show-managed-fields -o yaml I1125 05:14:52.470121 6604 local.go:42] ⚙️ kubectl --request-timeout 5s get csinodes --all-namespaces --show-managed-fields -o yaml W1125 05:14:57.544982 6604 dumplogs.go:133] Failed to get csinodes: exit status 1 I1125 05:14:57.545128 6604 dumplogs.go:127] kubectl --request-timeout 5s get csidrivers --all-namespaces --show-managed-fields -o yaml I1125 05:14:57.545137 6604 local.go:42] ⚙️ kubectl --request-timeout 5s get csidrivers --all-namespaces --show-managed-fields -o yaml W1125 05:15:02.617423 6604 dumplogs.go:133] Failed to get csidrivers: exit status 1 I1125 05:15:02.617533 6604 dumplogs.go:127] kubectl --request-timeout 5s get storageclasses --all-namespaces --show-managed-fields -o yaml I1125 05:15:02.617542 6604 local.go:42] ⚙️ kubectl --request-timeout 5s get storageclasses --all-namespaces --show-managed-fields -o yaml W1125 05:15:07.687642 6604 dumplogs.go:133] Failed to get storageclasses: exit status 1 I1125 05:15:07.688493 6604 dumplogs.go:127] kubectl --request-timeout 5s get persistentvolumes --all-namespaces --show-managed-fields -o yaml I1125 05:15:07.688528 6604 local.go:42] ⚙️ kubectl --request-timeout 5s get persistentvolumes --all-namespaces --show-managed-fields -o yaml W1125 05:15:12.760736 6604 dumplogs.go:133] Failed to get persistentvolumes: exit status 1 I1125 05:15:12.760881 6604 dumplogs.go:127] kubectl --request-timeout 5s get mutatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml I1125 05:15:12.760896 6604 local.go:42] ⚙️ kubectl --request-timeout 5s get mutatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml W1125 05:15:17.828709 6604 dumplogs.go:133] Failed to get mutatingwebhookconfigurations: exit status 1 I1125 05:15:17.828849 6604 dumplogs.go:127] kubectl --request-timeout 5s get validatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml I1125 05:15:17.828878 6604 local.go:42] ⚙️ kubectl --request-timeout 5s get validatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml W1125 05:15:22.901145 6604 dumplogs.go:133] Failed to get validatingwebhookconfigurations: exit status 1 I1125 05:15:22.901186 6604 local.go:42] ⚙️ kubectl --request-timeout 5s get namespaces --no-headers -o custom-columns=name:.metadata.name W1125 05:15:27.971781 6604 down.go:34] Dumping cluster logs at the start of Down() failed: failed to get namespaces: exit status 1 I1125 05:15:27.971810 6604 down.go:48] /tmp/kops.BKbYnq9Pf delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1125 05:15:27.971820 6604 local.go:42] ⚙️ /tmp/kops.BKbYnq9Pf delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1125 05:15:28.007832 6738 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true I1125 05:15:28.007930 6738 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true I1125 05:15:29.421361 6738 delete_cluster.go:128] Looking for cloud resources to delete TYPE NAME ID ... skipping 505 lines ...