e2e-kops-aws-addon-resource-tracking #1596364116883148800
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 1 succeeded |
| Started | |
| Elapsed | 35m22s |
| Revision | master |
kubetest2 Down
... skipping 198 lines ... I1126 04:46:36.452261 6276 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/f142930b-6d44-11ed-a6da-22215f11743a" I1126 04:46:36.455629 6276 app.go:128] ID for this run: "f142930b-6d44-11ed-a6da-22215f11743a" I1126 04:46:36.455897 6276 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/id_ed25519 I1126 04:46:36.474140 6276 up.go:44] Cleaning up any leaked resources from previous cluster I1126 04:46:36.474240 6276 dumplogs.go:45] /tmp/kops.XwCtUUQ9a 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 I1126 04:46:36.474264 6276 local.go:42] ⚙️ /tmp/kops.XwCtUUQ9a 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 W1126 04:46:37.057724 6276 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I1126 04:46:37.057769 6276 down.go:48] /tmp/kops.XwCtUUQ9a delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1126 04:46:37.057789 6276 local.go:42] ⚙️ /tmp/kops.XwCtUUQ9a delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1126 04:46:37.073716 6297 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1126 04:46:37.073810 6297 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true error reading cluster configuration: Cluster.kops.k8s.io "e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io" not found I1126 04:46:37.600692 6276 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2022/11/26 04:46:37 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 I1126 04:46:37.619363 6276 http.go:37] curl https://ip.jsb.workers.dev I1126 04:46:37.742509 6276 up.go:167] /tmp/kops.XwCtUUQ9a 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 35.184.42.228/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large I1126 04:46:37.742549 6276 local.go:42] ⚙️ /tmp/kops.XwCtUUQ9a 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 35.184.42.228/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large I1126 04:46:37.757925 6308 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1126 04:46:37.758115 6308 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1126 04:46:37.805205 6308 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 W1126 04:47:29.959696 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:47:39.999560 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:47:50.039259 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:48:00.081311 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:48:10.134126 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:48:20.173872 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:48:30.222217 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:48:40.264172 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:48:50.303964 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:49:00.348938 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:49:10.402688 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:49:20.442393 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:49:30.479786 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:49:40.519435 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:49:50.554145 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:50:00.605150 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:50:10.651994 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:50:20.701149 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:50:30.749218 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:50:40.789343 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:50:50.841444 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:51:00.891557 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:51:10.925497 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:51:20.961259 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:51:30.993908 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W1126 04:51:41.040113 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 18 lines ... Pod kube-system/coredns-autoscaler-84d4cfd89c-fgc64 system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fgc64" is pending Pod kube-system/kube-proxy-ip-172-20-34-62.ap-southeast-2.compute.internal system-node-critical pod "kube-proxy-ip-172-20-34-62.ap-southeast-2.compute.internal" is pending Pod kube-system/kube-proxy-ip-172-20-36-160.ap-southeast-2.compute.internal system-node-critical pod "kube-proxy-ip-172-20-36-160.ap-southeast-2.compute.internal" is pending Pod kube-system/kube-proxy-ip-172-20-36-253.ap-southeast-2.compute.internal system-node-critical pod "kube-proxy-ip-172-20-36-253.ap-southeast-2.compute.internal" is pending Pod kube-system/kube-scheduler-ip-172-20-35-134.ap-southeast-2.compute.internal system-cluster-critical pod "kube-scheduler-ip-172-20-35-134.ap-southeast-2.compute.internal" is pending Validation Failed W1126 04:51:55.797766 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 10 lines ... Node ip-172-20-39-60.ap-southeast-2.compute.internal node "ip-172-20-39-60.ap-southeast-2.compute.internal" of role "node" is not ready Pod kube-system/aws-node-termination-handler-mbllr system-node-critical pod "aws-node-termination-handler-mbllr" is pending Pod kube-system/coredns-5dc785954d-5hjsx system-cluster-critical pod "coredns-5dc785954d-5hjsx" is pending Pod kube-system/coredns-autoscaler-84d4cfd89c-fgc64 system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fgc64" is pending Pod kube-system/kube-proxy-ip-172-20-39-60.ap-southeast-2.compute.internal system-node-critical pod "kube-proxy-ip-172-20-39-60.ap-southeast-2.compute.internal" is pending Validation Failed W1126 04:52:08.755904 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 6 lines ... ip-172-20-39-60.ap-southeast-2.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/etcd-manager-main-ip-172-20-35-134.ap-southeast-2.compute.internal system-cluster-critical pod "etcd-manager-main-ip-172-20-35-134.ap-southeast-2.compute.internal" is pending Validation Failed W1126 04:52:21.711200 6348 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-ap-southeast-2a Master c5.large 1 1 ap-southeast-2a nodes-ap-southeast-2a Node t3.medium 4 4 ap-southeast-2a ... skipping 974 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 1131 lines ... WARNING: ignoring DaemonSet-managed Pods: kube-system/aws-node-termination-handler-lctf2, kube-system/kops-controller-sdfwg evicting pod kube-system/dns-controller-7fc66c4dd4-gxwkg I1126 04:55:29.316179 6441 instancegroups.go:681] Waiting for 5s for pods to stabilize after draining. I1126 04:55:34.320217 6441 instancegroups.go:598] Stopping instance "i-063b3b8d7786dd2f7", node "ip-172-20-35-134.ap-southeast-2.compute.internal", in group "master-ap-southeast-2a.masters.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io" (this may take a while). I1126 04:55:34.694576 6441 instancegroups.go:443] waiting for 15s after terminating instance I1126 04:55:49.694855 6441 instancegroups.go:477] Validating the cluster. I1126 04:56:19.742702 6441 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.55.156.177:443: i/o timeout. I1126 04:57:19.783020 6441 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.55.156.177:443: i/o timeout. I1126 04:58:19.829809 6441 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.55.156.177:443: i/o timeout. I1126 04:59:19.878400 6441 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.55.156.177:443: i/o timeout. I1126 05:00:19.914741 6441 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.55.156.177:443: i/o timeout. I1126 05:01:19.956284 6441 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.55.156.177:443: i/o timeout. I1126 05:02:19.999026 6441 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.55.156.177:443: i/o timeout. I1126 05:03:20.038627 6441 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.55.156.177:443: i/o timeout. I1126 05:04:20.077386 6441 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.55.156.177:443: i/o timeout. I1126 05:05:20.113259 6441 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.55.156.177:443: i/o timeout. I1126 05:06:20.153623 6441 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.55.156.177:443: i/o timeout. I1126 05:07:20.189410 6441 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.55.156.177:443: i/o timeout. I1126 05:08:20.222922 6441 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.55.156.177:443: i/o timeout. I1126 05:09:20.265337 6441 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.55.156.177:443: i/o timeout. I1126 05:10:20.314623 6441 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.55.156.177:443: i/o timeout. I1126 05:11:20.351880 6441 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.55.156.177:443: i/o timeout. E1126 05:11:20.352110 6441 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.YTvFOoTR7 --down I1126 05:11:20.383534 6460 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true I1126 05:11:20.387181 6460 app.go:61] The files in RunDir shall not be part of Artifacts I1126 05:11:20.387220 6460 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts I1126 05:11:20.387247 6460 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/f142930b-6d44-11ed-a6da-22215f11743a" ... skipping 17 lines ... Warning: Permanently added '54.252.2.53' (ECDSA) to the list of known hosts. I1126 05:15:08.099171 6460 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.252.2.53 -- rm -rf /tmp/cluster-info I1126 05:15:08.099215 6460 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.252.2.53 -- rm -rf /tmp/cluster-info Warning: Permanently added '54.252.2.53' (ECDSA) to the list of known hosts. I1126 05:15:10.657242 6460 dumplogs.go:127] kubectl --request-timeout 5s get csinodes --all-namespaces --show-managed-fields -o yaml I1126 05:15:10.657278 6460 local.go:42] ⚙️ kubectl --request-timeout 5s get csinodes --all-namespaces --show-managed-fields -o yaml W1126 05:15:15.727210 6460 dumplogs.go:133] Failed to get csinodes: exit status 1 I1126 05:15:15.727358 6460 dumplogs.go:127] kubectl --request-timeout 5s get csidrivers --all-namespaces --show-managed-fields -o yaml I1126 05:15:15.727370 6460 local.go:42] ⚙️ kubectl --request-timeout 5s get csidrivers --all-namespaces --show-managed-fields -o yaml W1126 05:15:20.796606 6460 dumplogs.go:133] Failed to get csidrivers: exit status 1 I1126 05:15:20.796734 6460 dumplogs.go:127] kubectl --request-timeout 5s get storageclasses --all-namespaces --show-managed-fields -o yaml I1126 05:15:20.796745 6460 local.go:42] ⚙️ kubectl --request-timeout 5s get storageclasses --all-namespaces --show-managed-fields -o yaml W1126 05:15:25.869923 6460 dumplogs.go:133] Failed to get storageclasses: exit status 1 I1126 05:15:25.870132 6460 dumplogs.go:127] kubectl --request-timeout 5s get persistentvolumes --all-namespaces --show-managed-fields -o yaml I1126 05:15:25.870153 6460 local.go:42] ⚙️ kubectl --request-timeout 5s get persistentvolumes --all-namespaces --show-managed-fields -o yaml W1126 05:15:30.972747 6460 dumplogs.go:133] Failed to get persistentvolumes: exit status 1 I1126 05:15:30.972948 6460 dumplogs.go:127] kubectl --request-timeout 5s get mutatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml I1126 05:15:30.972960 6460 local.go:42] ⚙️ kubectl --request-timeout 5s get mutatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml W1126 05:15:36.039032 6460 dumplogs.go:133] Failed to get mutatingwebhookconfigurations: exit status 1 I1126 05:15:36.039160 6460 dumplogs.go:127] kubectl --request-timeout 5s get validatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml I1126 05:15:36.039170 6460 local.go:42] ⚙️ kubectl --request-timeout 5s get validatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml W1126 05:15:41.109120 6460 dumplogs.go:133] Failed to get validatingwebhookconfigurations: exit status 1 I1126 05:15:41.109204 6460 local.go:42] ⚙️ kubectl --request-timeout 5s get namespaces --no-headers -o custom-columns=name:.metadata.name W1126 05:15:46.180381 6460 down.go:34] Dumping cluster logs at the start of Down() failed: failed to get namespaces: exit status 1 I1126 05:15:46.180420 6460 down.go:48] /tmp/kops.YTvFOoTR7 delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1126 05:15:46.180436 6460 local.go:42] ⚙️ /tmp/kops.YTvFOoTR7 delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1126 05:15:46.214275 6592 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true I1126 05:15:46.214379 6592 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true I1126 05:15:47.509507 6592 delete_cluster.go:128] Looking for cloud resources to delete TYPE NAME ID ... skipping 473 lines ...