e2e-kops-aws-addon-resource-tracking #1594914317826789376
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 1 succeeded |
| Started | |
| Elapsed | 34m14s |
| Revision | master |
kubetest2 Down
... skipping 198 lines ... I1122 04:44:49.186778 6270 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/246c243a-6a20-11ed-bf7e-1e6522e3577b" I1122 04:44:49.190931 6270 app.go:128] ID for this run: "246c243a-6a20-11ed-bf7e-1e6522e3577b" I1122 04:44:49.191173 6270 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/id_ed25519 I1122 04:44:49.199347 6270 up.go:44] Cleaning up any leaked resources from previous cluster I1122 04:44:49.199472 6270 dumplogs.go:45] /tmp/kops.Vhs3mx6A0 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 04:44:49.199490 6270 local.go:42] ⚙️ /tmp/kops.Vhs3mx6A0 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 04:44:49.931744 6270 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I1122 04:44:49.931787 6270 down.go:48] /tmp/kops.Vhs3mx6A0 delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1122 04:44:49.931801 6270 local.go:42] ⚙️ /tmp/kops.Vhs3mx6A0 delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1122 04:44:49.947029 6294 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1122 04:44:49.947114 6294 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 04:44:50.461476 6270 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2022/11/22 04:44:50 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 04:44:50.476247 6270 http.go:37] curl https://ip.jsb.workers.dev I1122 04:44:50.589905 6270 up.go:167] /tmp/kops.Vhs3mx6A0 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.202.7.1/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-2a --master-size c5.large I1122 04:44:50.589957 6270 local.go:42] ⚙️ /tmp/kops.Vhs3mx6A0 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.202.7.1/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-2a --master-size c5.large I1122 04:44:50.606289 6304 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1122 04:44:50.606501 6304 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true I1122 04:44:50.656842 6304 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 04:45:40.879727 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:45:50.916848 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:46:00.952803 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:46:10.998923 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:46:21.030986 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:46:31.066309 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:46:41.104991 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:46:51.144565 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:47:01.177696 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:47:11.211408 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:47:21.260069 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:47:31.299045 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:47:41.334443 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:47:51.374967 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:48:01.417276 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:48:11.455538 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:48:21.489513 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:48:31.522709 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:48:41.555582 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:48:51.594431 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:49:01.629128 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:49:11.669617 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:49:21.705376 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:49:31.739068 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:49:41.774056 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:49:51.811619 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:50:01.848067 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:50:11.883542 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-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 W1122 04:50:21.915553 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-2a ... skipping 15 lines ... Pod kube-system/coredns-5dc785954d-ccqp9 system-cluster-critical pod "coredns-5dc785954d-ccqp9" is pending Pod kube-system/coredns-autoscaler-84d4cfd89c-7hfg6 system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-7hfg6" is pending Pod kube-system/kube-proxy-ip-172-20-35-214.eu-west-2.compute.internal system-node-critical pod "kube-proxy-ip-172-20-35-214.eu-west-2.compute.internal" is pending Pod kube-system/kube-proxy-ip-172-20-44-249.eu-west-2.compute.internal system-node-critical pod "kube-proxy-ip-172-20-44-249.eu-west-2.compute.internal" is pending Pod kube-system/kube-proxy-ip-172-20-62-182.eu-west-2.compute.internal system-node-critical pod "kube-proxy-ip-172-20-62-182.eu-west-2.compute.internal" is pending Validation Failed W1122 04:50:36.648115 6343 validate_cluster.go:221] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS master-eu-west-2a Master c5.large 1 1 eu-west-2a nodes-eu-west-2a Node t3.medium 4 4 eu-west-2a ... 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 294 lines ... for cmd in "${commands[@]}"; do ... continue fi + if ! validate-hash "${file}" "${hash}"; then - if [[ -n "${hash}" ]] && ! validate-hash "${file}" "${hash}"; then echo "== Hash validation of ${url} failed. Retrying. ==" rm -f "${file}" else - if [[ -n "${hash}" ]]; then + echo "== Downloaded ${url} (SHA256 = ${hash}) ==" - echo "== Downloaded ${url} (SHA1 = ${hash}) ==" - else ... skipping 1136 lines ... WARNING: ignoring DaemonSet-managed Pods: kube-system/aws-node-termination-handler-rmjbg, kube-system/kops-controller-s4g4z evicting pod kube-system/dns-controller-7fc66c4dd4-2z876 I1122 04:53:26.656017 6441 instancegroups.go:681] Waiting for 5s for pods to stabilize after draining. I1122 04:53:31.656239 6441 instancegroups.go:598] Stopping instance "i-03e8ddf4de75d97b6", node "ip-172-20-52-47.eu-west-2.compute.internal", in group "master-eu-west-2a.masters.e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io" (this may take a while). I1122 04:53:31.954734 6441 instancegroups.go:443] waiting for 15s after terminating instance I1122 04:53:46.955027 6441 instancegroups.go:477] Validating the cluster. I1122 04:54:16.997801 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 3.8.6.232:443: i/o timeout. I1122 04:55:17.038397 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 3.8.6.232:443: i/o timeout. I1122 04:56:17.101783 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 3.8.6.232:443: i/o timeout. I1122 04:57:17.147009 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 3.8.6.232:443: i/o timeout. I1122 04:58:17.207400 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 3.8.6.232:443: i/o timeout. I1122 04:59:17.266607 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 3.8.6.232:443: i/o timeout. I1122 05:00:17.307712 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 3.8.6.232:443: i/o timeout. I1122 05:01:17.362521 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 3.8.6.232:443: i/o timeout. I1122 05:02:17.411510 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 3.8.6.232:443: i/o timeout. I1122 05:03:17.447721 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 3.8.6.232:443: i/o timeout. I1122 05:04:17.494873 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 3.8.6.232:443: i/o timeout. I1122 05:05:17.541735 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 3.8.6.232:443: i/o timeout. I1122 05:06:17.602912 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 3.8.6.232:443: i/o timeout. I1122 05:07:17.650721 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 3.8.6.232:443: i/o timeout. I1122 05:08:17.697422 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 3.8.6.232:443: i/o timeout. I1122 05:09:17.752291 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 3.8.6.232:443: i/o timeout. E1122 05:09:17.752341 6441 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.zmDZRT68T --down I1122 05:09:17.786550 6461 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true I1122 05:09:17.787864 6461 app.go:61] The files in RunDir shall not be part of Artifacts I1122 05:09:17.787887 6461 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts I1122 05:09:17.787913 6461 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/246c243a-6a20-11ed-bf7e-1e6522e3577b" ... skipping 17 lines ... Warning: Permanently added '35.178.203.87' (ECDSA) to the list of known hosts. I1122 05:12:50.280335 6461 dumplogs.go:248] ssh -i /tmp/kops/e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io/id_ed25519 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ubuntu@35.178.203.87 -- rm -rf /tmp/cluster-info I1122 05:12:50.280387 6461 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.178.203.87 -- rm -rf /tmp/cluster-info Warning: Permanently added '35.178.203.87' (ECDSA) to the list of known hosts. I1122 05:12:51.835870 6461 dumplogs.go:126] kubectl --request-timeout 5s get csinodes --all-namespaces -o yaml I1122 05:12:51.835906 6461 local.go:42] ⚙️ kubectl --request-timeout 5s get csinodes --all-namespaces -o yaml W1122 05:12:56.907693 6461 dumplogs.go:132] Failed to get csinodes: exit status 1 I1122 05:12:56.907861 6461 dumplogs.go:126] kubectl --request-timeout 5s get csidrivers --all-namespaces -o yaml I1122 05:12:56.907874 6461 local.go:42] ⚙️ kubectl --request-timeout 5s get csidrivers --all-namespaces -o yaml W1122 05:13:01.979754 6461 dumplogs.go:132] Failed to get csidrivers: exit status 1 I1122 05:13:01.979886 6461 dumplogs.go:126] kubectl --request-timeout 5s get storageclasses --all-namespaces -o yaml I1122 05:13:01.979896 6461 local.go:42] ⚙️ kubectl --request-timeout 5s get storageclasses --all-namespaces -o yaml W1122 05:13:07.047050 6461 dumplogs.go:132] Failed to get storageclasses: exit status 1 I1122 05:13:07.047195 6461 dumplogs.go:126] kubectl --request-timeout 5s get persistentvolumes --all-namespaces -o yaml I1122 05:13:07.047207 6461 local.go:42] ⚙️ kubectl --request-timeout 5s get persistentvolumes --all-namespaces -o yaml W1122 05:13:12.118037 6461 dumplogs.go:132] Failed to get persistentvolumes: exit status 1 I1122 05:13:12.118175 6461 dumplogs.go:126] kubectl --request-timeout 5s get mutatingwebhookconfigurations --all-namespaces -o yaml I1122 05:13:12.118186 6461 local.go:42] ⚙️ kubectl --request-timeout 5s get mutatingwebhookconfigurations --all-namespaces -o yaml W1122 05:13:17.185461 6461 dumplogs.go:132] Failed to get mutatingwebhookconfigurations: exit status 1 I1122 05:13:17.185625 6461 dumplogs.go:126] kubectl --request-timeout 5s get validatingwebhookconfigurations --all-namespaces -o yaml I1122 05:13:17.185636 6461 local.go:42] ⚙️ kubectl --request-timeout 5s get validatingwebhookconfigurations --all-namespaces -o yaml W1122 05:13:22.257095 6461 dumplogs.go:132] Failed to get validatingwebhookconfigurations: exit status 1 I1122 05:13:22.257702 6461 local.go:42] ⚙️ kubectl --request-timeout 5s get namespaces --no-headers -o custom-columns=name:.metadata.name W1122 05:13:27.326679 6461 down.go:34] Dumping cluster logs at the start of Down() failed: failed to get namespaces: exit status 1 I1122 05:13:27.326713 6461 down.go:48] /tmp/kops.zmDZRT68T delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1122 05:13:27.326726 6461 local.go:42] ⚙️ /tmp/kops.zmDZRT68T delete cluster --name e2e-c0d41e2af2-13250.test-cncf-aws.k8s.io --yes I1122 05:13:27.364781 6601 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true I1122 05:13:27.365063 6601 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true I1122 05:13:28.337317 6601 delete_cluster.go:128] Looking for cloud resources to delete TYPE NAME ID ... skipping 541 lines ...