e2e-kops-aws-addon-resource-tracking #1596243319686434816
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 1 succeeded |
| Started | |
| Elapsed | 30m57s |
| Revision | master |
kubetest2 Down
... skipping 198 lines ... I1125 20:45:43.750673 6290 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/e2f23692-6d01-11ed-a6da-22215f11743a" I1125 20:45:43.758506 6290 app.go:128] ID for this run: "e2f23692-6d01-11ed-a6da-22215f11743a" I1125 20:45:43.758917 6290 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/id_ed25519 I1125 20:45:43.772681 6290 up.go:44] Cleaning up any leaked resources from previous cluster I1125 20:45:43.772791 6290 dumplogs.go:45] /tmp/kops.fz5ryoGGu 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 20:45:43.772805 6290 local.go:42] ⚙️ /tmp/kops.fz5ryoGGu 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 20:45:44.339579 6290 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I1125 20:45:44.339630 6290 down.go:48] /tmp/kops.fz5ryoGGu delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1125 20:45:44.339645 6290 local.go:42] ⚙️ /tmp/kops.fz5ryoGGu delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1125 20:45:44.356413 6311 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1125 20:45:44.356507 6311 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 20:45:44.869327 6290 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2022/11/25 20:45:44 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 20:45:44.886602 6290 http.go:37] curl https://ip.jsb.workers.dev I1125 20:45:45.007580 6290 up.go:167] /tmp/kops.fz5ryoGGu 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.66.59.90/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large I1125 20:45:45.007638 6290 local.go:42] ⚙️ /tmp/kops.fz5ryoGGu 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.66.59.90/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large I1125 20:45:45.023813 6321 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1125 20:45:45.023906 6321 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1125 20:45:45.068201 6321 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 20:46:26.393992 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:46:36.428502 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:46:46.464581 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:46:56.502908 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:47:06.539550 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:47:16.581937 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:47:26.621846 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:47:36.662543 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:47:46.701843 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:47:56.742322 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:48:06.790750 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:48:16.839333 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:48:26.875253 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:48:36.926655 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:48:46.967208 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:48:57.001854 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:49:07.044977 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:49:17.084934 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:49:27.134351 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:49:37.171996 6364 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-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 W1125 20:49:47.222678 6364 validate_cluster.go:221] (will retry): cluster not yet healthy W1125 20:50:27.268920 6364 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-us-east-2a Master c5.large 1 1 us-east-2a nodes-us-east-2a Node t3.medium 4 4 us-east-2a NODE STATUS ... 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 1133 lines ... WARNING: ignoring DaemonSet-managed Pods: kube-system/aws-node-termination-handler-bvgpf, kube-system/kops-controller-cp96b evicting pod kube-system/dns-controller-7fc66c4dd4-bgzcz I1125 20:52:42.717756 6461 instancegroups.go:681] Waiting for 5s for pods to stabilize after draining. I1125 20:52:47.718044 6461 instancegroups.go:598] Stopping instance "i-0674d9969dfdb67fc", node "ip-172-20-62-56.us-east-2.compute.internal", in group "master-us-east-2a.masters.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io" (this may take a while). I1125 20:52:47.929260 6461 instancegroups.go:443] waiting for 15s after terminating instance I1125 20:53:02.934770 6461 instancegroups.go:477] Validating the cluster. I1125 20:53:32.969841 6461 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 18.219.103.190:443: i/o timeout. I1125 20:54:33.029520 6461 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 18.219.103.190:443: i/o timeout. I1125 20:55:33.118501 6461 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 18.219.103.190:443: i/o timeout. I1125 20:56:33.160880 6461 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 18.219.103.190:443: i/o timeout. I1125 20:57:33.199661 6461 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 18.219.103.190:443: i/o timeout. I1125 20:58:33.255057 6461 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 18.219.103.190:443: i/o timeout. I1125 20:59:33.298044 6461 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 18.219.103.190:443: i/o timeout. I1125 21:00:33.347255 6461 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 18.219.103.190:443: i/o timeout. I1125 21:01:33.393048 6461 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 18.219.103.190:443: i/o timeout. I1125 21:02:33.442026 6461 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 18.219.103.190:443: i/o timeout. I1125 21:03:33.481329 6461 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 18.219.103.190:443: i/o timeout. I1125 21:04:33.537919 6461 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 18.219.103.190:443: i/o timeout. I1125 21:05:33.580010 6461 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 18.219.103.190:443: i/o timeout. I1125 21:06:33.641381 6461 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 18.219.103.190:443: i/o timeout. I1125 21:07:33.688961 6461 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 18.219.103.190:443: i/o timeout. I1125 21:08:33.736026 6461 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 18.219.103.190:443: i/o timeout. E1125 21:08:33.736073 6461 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.yjJaGQiQp --down I1125 21:08:33.769152 6478 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true I1125 21:08:33.770341 6478 app.go:61] The files in RunDir shall not be part of Artifacts I1125 21:08:33.770368 6478 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts I1125 21:08:33.770397 6478 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/e2f23692-6d01-11ed-a6da-22215f11743a" ... skipping 17 lines ... Warning: Permanently added '3.22.71.132' (ECDSA) to the list of known hosts. I1125 21:10:55.316038 6478 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@3.22.71.132 -- rm -rf /tmp/cluster-info I1125 21:10:55.316103 6478 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@3.22.71.132 -- rm -rf /tmp/cluster-info Warning: Permanently added '3.22.71.132' (ECDSA) to the list of known hosts. I1125 21:10:56.085521 6478 dumplogs.go:127] kubectl --request-timeout 5s get csinodes --all-namespaces --show-managed-fields -o yaml I1125 21:10:56.085557 6478 local.go:42] ⚙️ kubectl --request-timeout 5s get csinodes --all-namespaces --show-managed-fields -o yaml W1125 21:11:01.160535 6478 dumplogs.go:133] Failed to get csinodes: exit status 1 I1125 21:11:01.160741 6478 dumplogs.go:127] kubectl --request-timeout 5s get csidrivers --all-namespaces --show-managed-fields -o yaml I1125 21:11:01.160752 6478 local.go:42] ⚙️ kubectl --request-timeout 5s get csidrivers --all-namespaces --show-managed-fields -o yaml W1125 21:11:06.228668 6478 dumplogs.go:133] Failed to get csidrivers: exit status 1 I1125 21:11:06.228846 6478 dumplogs.go:127] kubectl --request-timeout 5s get storageclasses --all-namespaces --show-managed-fields -o yaml I1125 21:11:06.228865 6478 local.go:42] ⚙️ kubectl --request-timeout 5s get storageclasses --all-namespaces --show-managed-fields -o yaml W1125 21:11:11.301799 6478 dumplogs.go:133] Failed to get storageclasses: exit status 1 I1125 21:11:11.302037 6478 dumplogs.go:127] kubectl --request-timeout 5s get persistentvolumes --all-namespaces --show-managed-fields -o yaml I1125 21:11:11.302061 6478 local.go:42] ⚙️ kubectl --request-timeout 5s get persistentvolumes --all-namespaces --show-managed-fields -o yaml W1125 21:11:16.371693 6478 dumplogs.go:133] Failed to get persistentvolumes: exit status 1 I1125 21:11:16.371883 6478 dumplogs.go:127] kubectl --request-timeout 5s get mutatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml I1125 21:11:16.371920 6478 local.go:42] ⚙️ kubectl --request-timeout 5s get mutatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml W1125 21:11:21.441039 6478 dumplogs.go:133] Failed to get mutatingwebhookconfigurations: exit status 1 I1125 21:11:21.441299 6478 dumplogs.go:127] kubectl --request-timeout 5s get validatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml I1125 21:11:21.441321 6478 local.go:42] ⚙️ kubectl --request-timeout 5s get validatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml W1125 21:11:26.510808 6478 dumplogs.go:133] Failed to get validatingwebhookconfigurations: exit status 1 I1125 21:11:26.510855 6478 local.go:42] ⚙️ kubectl --request-timeout 5s get namespaces --no-headers -o custom-columns=name:.metadata.name W1125 21:11:31.580523 6478 down.go:34] Dumping cluster logs at the start of Down() failed: failed to get namespaces: exit status 1 I1125 21:11:31.580560 6478 down.go:48] /tmp/kops.yjJaGQiQp delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1125 21:11:31.580571 6478 local.go:42] ⚙️ /tmp/kops.yjJaGQiQp delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1125 21:11:31.614199 6612 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true I1125 21:11:31.614306 6612 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true I1125 21:11:32.295406 6612 delete_cluster.go:128] Looking for cloud resources to delete TYPE NAME ID ... skipping 529 lines ...