This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2022-06-09 21:01
Elapsed19m59s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 195 lines ...
+ KOPS_B=/tmp/kops.58kUewIPG
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io --kops-root=/home/prow/go/src/k8s.io/kops --admin-access= --env=KOPS_FEATURE_FLAGS=SpecOverrideFlag --down --kops-binary-path=/tmp/kops.58kUewIPG
I0609 21:02:45.660548    5872 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0609 21:02:45.661329    5872 app.go:61] RunDir for this run: "/logs/artifacts/48f0e4b7-e837-11ec-a6a4-92b1b368bc04"
I0609 21:02:45.669778    5872 app.go:120] ID for this run: "48f0e4b7-e837-11ec-a6a4-92b1b368bc04"
I0609 21:02:45.678080    5872 dumplogs.go:45] /tmp/kops.58kUewIPG toolbox dump --name e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0609 21:02:46.162272    5872 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0609 21:02:46.162318    5872 down.go:48] /tmp/kops.58kUewIPG delete cluster --name e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io --yes
I0609 21:02:46.183355    5893 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0609 21:02:46.183456    5893 featureflag.go:164] FeatureFlag "AlphaAllowGCE"=true
I0609 21:02:46.183462    5893 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io" not found
Error: exit status 1
+ echo 'kubetest2 down failed'
kubetest2 down failed
+ [[ v == \v ]]
+ KOPS_BASE_URL=
++ kops-download-release v1.24.0-beta.1
++ local kops
+++ mktemp -t kops.XXXXXXXXX
++ kops=/tmp/kops.acXSnQmL6
... skipping 7 lines ...
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io --kops-root=/home/prow/go/src/k8s.io/kops --admin-access= --env=KOPS_FEATURE_FLAGS=SpecOverrideFlag --up --kops-binary-path=/tmp/kops.acXSnQmL6 --kubernetes-version=v1.24.0 '--create-args=--networking calico'
I0609 21:02:51.537605    5928 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0609 21:02:51.538529    5928 app.go:61] RunDir for this run: "/logs/artifacts/48f0e4b7-e837-11ec-a6a4-92b1b368bc04"
I0609 21:02:51.678837    5928 app.go:120] ID for this run: "48f0e4b7-e837-11ec-a6a4-92b1b368bc04"
I0609 21:02:51.678910    5928 up.go:44] Cleaning up any leaked resources from previous cluster
I0609 21:02:51.679005    5928 dumplogs.go:45] /tmp/kops.acXSnQmL6 toolbox dump --name e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0609 21:02:52.141796    5928 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0609 21:02:52.141848    5928 down.go:48] /tmp/kops.acXSnQmL6 delete cluster --name e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io --yes
I0609 21:02:52.162100    5950 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0609 21:02:52.162198    5950 featureflag.go:164] FeatureFlag "AlphaAllowGCE"=true
I0609 21:02:52.162208    5950 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io" not found
I0609 21:02:52.641855    5928 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/06/09 21:02:52 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
I0609 21:02:52.650348    5928 http.go:37] curl https://ip.jsb.workers.dev
I0609 21:02:52.768904    5928 up.go:156] /tmp/kops.acXSnQmL6 create cluster --name e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io --cloud aws --kubernetes-version v1.24.0 --ssh-public-key /tmp/kops/e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --networking calico --admin-access 34.68.192.45/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones sa-east-1a --master-size c5.large
I0609 21:02:52.788749    5961 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0609 21:02:52.788941    5961 featureflag.go:164] FeatureFlag "AlphaAllowGCE"=true
I0609 21:02:52.788978    5961 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0609 21:02:52.816453    5961 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io/id_ed25519.pub
... skipping 513 lines ...
I0609 21:03:37.191170    5928 up.go:240] /tmp/kops.acXSnQmL6 validate cluster --name e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0609 21:03:37.211078    6000 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0609 21:03:37.211163    6000 featureflag.go:164] FeatureFlag "AlphaAllowGCE"=true
I0609 21:03:37.211168    6000 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io

W0609 21:03:38.605807    6000 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:03:48.642850    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:03:58.689263    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:04:08.729089    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:04:18.771689    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:04:28.806215    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:04:38.846081    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
W0609 21:04:48.887388    6000 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:04:58.921608    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:05:08.969630    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:05:19.007331    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:05:29.042835    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:05:39.081368    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:05:49.121622    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:05:59.161724    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:06:09.197461    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:06:19.234771    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:06:29.271181    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:06:39.306796    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:06:49.346662    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:06:59.388308    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:07:09.423027    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:07:19.460168    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:07:29.496665    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:07:39.539778    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W0609 21:07:49.574241    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 17 lines ...
Pod	kube-system/coredns-autoscaler-865477f6c7-rr4bc	system-cluster-critical pod "coredns-autoscaler-865477f6c7-rr4bc" is pending
Pod	kube-system/ebs-csi-controller-5cbf5f55b5-dbfr7	system-cluster-critical pod "ebs-csi-controller-5cbf5f55b5-dbfr7" is pending
Pod	kube-system/ebs-csi-node-4zxxv			system-node-critical pod "ebs-csi-node-4zxxv" is pending
Pod	kube-system/ebs-csi-node-99gsf			system-node-critical pod "ebs-csi-node-99gsf" is pending
Pod	kube-system/ebs-csi-node-pcn8q			system-node-critical pod "ebs-csi-node-pcn8q" is pending

Validation Failed
W0609 21:08:03.032570    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 13 lines ...
Pod	kube-system/coredns-6b5499ccb9-njrtw		system-cluster-critical pod "coredns-6b5499ccb9-njrtw" is pending
Pod	kube-system/coredns-autoscaler-865477f6c7-rr4bc	system-cluster-critical pod "coredns-autoscaler-865477f6c7-rr4bc" is pending
Pod	kube-system/ebs-csi-node-4zxxv			system-node-critical pod "ebs-csi-node-4zxxv" is pending
Pod	kube-system/ebs-csi-node-99gsf			system-node-critical pod "ebs-csi-node-99gsf" is pending
Pod	kube-system/ebs-csi-node-pcn8q			system-node-critical pod "ebs-csi-node-pcn8q" is pending

Validation Failed
W0609 21:08:15.645662    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 11 lines ...
Pod	kube-system/coredns-6b5499ccb9-njrtw		system-cluster-critical pod "coredns-6b5499ccb9-njrtw" is pending
Pod	kube-system/coredns-autoscaler-865477f6c7-rr4bc	system-cluster-critical pod "coredns-autoscaler-865477f6c7-rr4bc" is pending
Pod	kube-system/ebs-csi-node-4zxxv			system-node-critical pod "ebs-csi-node-4zxxv" is pending
Pod	kube-system/ebs-csi-node-99gsf			system-node-critical pod "ebs-csi-node-99gsf" is pending
Pod	kube-system/ebs-csi-node-pcn8q			system-node-critical pod "ebs-csi-node-pcn8q" is pending

Validation Failed
W0609 21:08:28.105016    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-04c65a54c3fd539c6				machine "i-04c65a54c3fd539c6" has not yet joined cluster
Pod	kube-system/calico-node-w6d2t			system-node-critical pod "calico-node-w6d2t" is not ready (calico-node)
Pod	kube-system/coredns-6b5499ccb9-njrtw		system-cluster-critical pod "coredns-6b5499ccb9-njrtw" is pending
Pod	kube-system/coredns-autoscaler-865477f6c7-rr4bc	system-cluster-critical pod "coredns-autoscaler-865477f6c7-rr4bc" is pending
Pod	kube-system/ebs-csi-node-pcn8q			system-node-critical pod "ebs-csi-node-pcn8q" is pending

Validation Failed
W0609 21:08:40.564367    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 8 lines ...
KIND	NAME						MESSAGE
Machine	i-04c65a54c3fd539c6				machine "i-04c65a54c3fd539c6" has not yet joined cluster
Pod	kube-system/coredns-6b5499ccb9-njrtw		system-cluster-critical pod "coredns-6b5499ccb9-njrtw" is pending
Pod	kube-system/coredns-autoscaler-865477f6c7-rr4bc	system-cluster-critical pod "coredns-autoscaler-865477f6c7-rr4bc" is pending
Pod	kube-system/ebs-csi-node-pcn8q			system-node-critical pod "ebs-csi-node-pcn8q" is pending

Validation Failed
W0609 21:08:53.015171    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Machine	i-04c65a54c3fd539c6				machine "i-04c65a54c3fd539c6" has not yet joined cluster
Pod	kube-system/ebs-csi-node-pcn8q			system-node-critical pod "ebs-csi-node-pcn8q" is pending
Pod	kube-system/kube-proxy-i-06caf5120266266f9	system-node-critical pod "kube-proxy-i-06caf5120266266f9" is pending

Validation Failed
W0609 21:09:05.659198    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:09:18.125690    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:09:30.531467    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:09:42.976203    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:09:55.408399    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:10:08.002585    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:10:20.477386    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:10:32.901040    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:10:45.371772    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:10:57.791877    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:11:10.212804    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:11:22.674615    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:11:35.717325    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:11:48.172288    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:12:01.213865    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:12:13.623204    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:12:26.079079    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:12:38.605948    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:12:51.073903    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:13:03.601567    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:13:16.112152    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:13:28.629040    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:13:41.084540    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:13:53.635026    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:14:06.225751    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:14:18.794764    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:14:31.197238    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:14:43.599562    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:14:56.058342    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:15:08.564583    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:15:21.151500    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:15:33.546499    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:15:46.096556    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:15:59.029081    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:16:11.482595    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:16:23.944416    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:16:36.365711    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:16:48.937593    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:17:01.463947    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:17:14.033179    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:17:26.489164    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:17:38.926409    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:17:51.353926    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:18:03.862416    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:18:16.268479    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 5 lines ...
i-0de1d51facdcd80f5	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-04c65a54c3fd539c6	machine "i-04c65a54c3fd539c6" has not yet joined cluster

Validation Failed
W0609 21:18:28.779532    6000 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
Error: exit status 1
+ kops-finish
+ kubetest2 kops -v=2 --cloud-provider=aws --cluster-name=e2e-6655bc81b8-79a58.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.acXSnQmL6 --down
I0609 21:18:38.822720    6020 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0609 21:18:38.823695    6020 app.go:61] RunDir for this run: "/logs/artifacts/48f0e4b7-e837-11ec-a6a4-92b1b368bc04"
I0609 21:18:38.827069    6020 app.go:120] ID for this run: "48f0e4b7-e837-11ec-a6a4-92b1b368bc04"
I0609 21:18:38.827165    6020 dumplogs.go:45] /tmp/kops.acXSnQmL6 toolbox dump --name e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-6655bc81b8-79a58.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
... skipping 207 lines ...