e2e-kops-aws-addon-resource-tracking #1595155913264599040
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 1 succeeded |
| Started | |
| Elapsed | 36m1s |
| Revision | master |
kubetest2 Down
... skipping 198 lines ... I1122 20:46:22.010982 6421 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/41309afb-6aa6-11ed-bf7e-1e6522e3577b" I1122 20:46:22.017051 6421 app.go:128] ID for this run: "41309afb-6aa6-11ed-bf7e-1e6522e3577b" I1122 20:46:22.017465 6421 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/id_ed25519 I1122 20:46:22.032781 6421 up.go:44] Cleaning up any leaked resources from previous cluster I1122 20:46:22.033021 6421 dumplogs.go:45] /tmp/kops.iWYoRFEP9 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 I1122 20:46:22.033086 6421 local.go:42] ⚙️ /tmp/kops.iWYoRFEP9 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 W1122 20:46:22.729507 6421 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I1122 20:46:22.729568 6421 down.go:48] /tmp/kops.iWYoRFEP9 delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1122 20:46:22.729611 6421 local.go:42] ⚙️ /tmp/kops.iWYoRFEP9 delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1122 20:46:22.765664 6441 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1122 20:46:22.765951 6441 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true error reading cluster configuration: Cluster.kops.k8s.io "e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io" not found I1122 20:46:23.448495 6421 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2022/11/22 20:46:23 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 I1122 20:46:23.467437 6421 http.go:37] curl https://ip.jsb.workers.dev I1122 20:46:23.616801 6421 up.go:167] /tmp/kops.iWYoRFEP9 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.69.195.104/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-central-1a --master-size c5.large I1122 20:46:23.616848 6421 local.go:42] ⚙️ /tmp/kops.iWYoRFEP9 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.69.195.104/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-central-1a --master-size c5.large I1122 20:46:23.667902 6456 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1122 20:46:23.668547 6456 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1122 20:46:23.772566 6456 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 W1122 20:47:10.557805 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:47:20.600564 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:47:30.634626 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:47:40.672338 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:47:50.724635 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:48:00.761199 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:48:10.800796 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:48:20.853814 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:48:30.893201 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:48:40.936377 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:48:50.976638 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:49:01.029137 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:49:11.074702 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:49:21.109375 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:49:31.148146 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:49:41.188788 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:49:51.228233 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:50:01.270858 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:50:11.322651 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:50:21.369824 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:50:31.408791 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:50:41.449010 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:50:51.487429 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:51:01.536869 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:51:11.572515 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:51:21.612800 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:51:31.651632 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:51:41.685294 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:51:51.721887 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:52:01.757742 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:52:11.804385 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-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 W1122 20:52:21.842598 6499 validate_cluster.go:221] (will retry): cluster not yet healthy W1122 20:53:01.881769 6499 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-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a NODE STATUS ... skipping 20 lines ... ip-172-20-57-211.eu-central-1.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/coredns-5dc785954d-89nqq system-cluster-critical pod "coredns-5dc785954d-89nqq" is not ready (coredns) Validation Failed W1122 20:53:26.874642 6499 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-central-1a Master c5.large 1 1 eu-central-1a nodes-eu-central-1a Node t3.medium 4 4 eu-central-1a ... skipping 965 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 287 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-fvmmp, kube-system/kops-controller-s4z8r evicting pod kube-system/dns-controller-7fc66c4dd4-ltdkl I1122 20:56:11.641023 6597 instancegroups.go:681] Waiting for 5s for pods to stabilize after draining. I1122 20:56:16.641331 6597 instancegroups.go:598] Stopping instance "i-0bb3fb4436b21098d", node "ip-172-20-38-68.eu-central-1.compute.internal", in group "master-eu-central-1a.masters.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io" (this may take a while). I1122 20:56:16.944723 6597 instancegroups.go:443] waiting for 15s after terminating instance I1122 20:56:31.945024 6597 instancegroups.go:477] Validating the cluster. I1122 20:57:01.991958 6597 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 3.64.228.1:443: i/o timeout. I1122 20:58:02.040681 6597 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 3.64.228.1:443: i/o timeout. I1122 20:59:02.087707 6597 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 3.64.228.1:443: i/o timeout. I1122 21:00:02.132080 6597 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 3.64.228.1:443: i/o timeout. I1122 21:01:02.176998 6597 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 3.64.228.1:443: i/o timeout. I1122 21:02:02.221982 6597 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 3.64.228.1:443: i/o timeout. I1122 21:03:02.270901 6597 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 3.64.228.1:443: i/o timeout. I1122 21:04:02.310209 6597 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 3.64.228.1:443: i/o timeout. I1122 21:05:02.363214 6597 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 3.64.228.1:443: i/o timeout. I1122 21:06:02.420830 6597 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 3.64.228.1:443: i/o timeout. I1122 21:07:02.464065 6597 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 3.64.228.1:443: i/o timeout. I1122 21:08:02.518743 6597 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 3.64.228.1:443: i/o timeout. I1122 21:09:02.560052 6597 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 3.64.228.1:443: i/o timeout. I1122 21:10:02.605624 6597 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 3.64.228.1:443: i/o timeout. I1122 21:11:02.663917 6597 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 3.64.228.1:443: i/o timeout. I1122 21:12:02.713801 6597 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 3.64.228.1:443: i/o timeout. E1122 21:12:02.713863 6597 instancegroups.go:482] Cluster did not validate within 15m0s Error: master 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.x3ynRMqbL --down I1122 21:12:02.769890 6616 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true I1122 21:12:02.774141 6616 app.go:61] The files in RunDir shall not be part of Artifacts I1122 21:12:02.774187 6616 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts I1122 21:12:02.774237 6616 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/41309afb-6aa6-11ed-bf7e-1e6522e3577b" ... skipping 17 lines ... Warning: Permanently added '35.158.96.109' (ECDSA) to the list of known hosts. I1122 21:15:07.433938 6616 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@35.158.96.109 -- rm -rf /tmp/cluster-info I1122 21:15:07.434007 6616 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@35.158.96.109 -- rm -rf /tmp/cluster-info Warning: Permanently added '35.158.96.109' (ECDSA) to the list of known hosts. I1122 21:15:09.154098 6616 dumplogs.go:127] kubectl --request-timeout 5s get csinodes --all-namespaces --show-managed-fields -o yaml I1122 21:15:09.154139 6616 local.go:42] ⚙️ kubectl --request-timeout 5s get csinodes --all-namespaces --show-managed-fields -o yaml W1122 21:15:14.244981 6616 dumplogs.go:133] Failed to get csinodes: exit status 1 I1122 21:15:14.245179 6616 dumplogs.go:127] kubectl --request-timeout 5s get csidrivers --all-namespaces --show-managed-fields -o yaml I1122 21:15:14.245192 6616 local.go:42] ⚙️ kubectl --request-timeout 5s get csidrivers --all-namespaces --show-managed-fields -o yaml W1122 21:15:19.327030 6616 dumplogs.go:133] Failed to get csidrivers: exit status 1 I1122 21:15:19.327164 6616 dumplogs.go:127] kubectl --request-timeout 5s get storageclasses --all-namespaces --show-managed-fields -o yaml I1122 21:15:19.327174 6616 local.go:42] ⚙️ kubectl --request-timeout 5s get storageclasses --all-namespaces --show-managed-fields -o yaml W1122 21:15:24.416883 6616 dumplogs.go:133] Failed to get storageclasses: exit status 1 I1122 21:15:24.417117 6616 dumplogs.go:127] kubectl --request-timeout 5s get persistentvolumes --all-namespaces --show-managed-fields -o yaml I1122 21:15:24.417130 6616 local.go:42] ⚙️ kubectl --request-timeout 5s get persistentvolumes --all-namespaces --show-managed-fields -o yaml W1122 21:15:29.504445 6616 dumplogs.go:133] Failed to get persistentvolumes: exit status 1 I1122 21:15:29.504754 6616 dumplogs.go:127] kubectl --request-timeout 5s get mutatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml I1122 21:15:29.504770 6616 local.go:42] ⚙️ kubectl --request-timeout 5s get mutatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml W1122 21:15:34.593044 6616 dumplogs.go:133] Failed to get mutatingwebhookconfigurations: exit status 1 I1122 21:15:34.593231 6616 dumplogs.go:127] kubectl --request-timeout 5s get validatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml I1122 21:15:34.593248 6616 local.go:42] ⚙️ kubectl --request-timeout 5s get validatingwebhookconfigurations --all-namespaces --show-managed-fields -o yaml W1122 21:15:39.675294 6616 dumplogs.go:133] Failed to get validatingwebhookconfigurations: exit status 1 I1122 21:15:39.675365 6616 local.go:42] ⚙️ kubectl --request-timeout 5s get namespaces --no-headers -o custom-columns=name:.metadata.name W1122 21:15:44.765380 6616 down.go:34] Dumping cluster logs at the start of Down() failed: failed to get namespaces: exit status 1 I1122 21:15:44.765434 6616 down.go:48] /tmp/kops.x3ynRMqbL delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1122 21:15:44.765461 6616 local.go:42] ⚙️ /tmp/kops.x3ynRMqbL delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1122 21:15:44.817581 6752 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true I1122 21:15:44.817711 6752 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true I1122 21:15:45.834126 6752 delete_cluster.go:128] Looking for cloud resources to delete TYPE NAME ID ... skipping 529 lines ...