This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 1 succeeded
Started2022-10-04 06:27
Elapsed22m12s
Revisionmaster

No Test Failures!


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 224 lines ...
I1004 06:28:46.366876    6294 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I1004 06:28:46.366903    6294 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/8ec76b57-43ad-11ed-8c8e-f631763a04db"
I1004 06:28:46.374614    6294 app.go:128] ID for this run: "8ec76b57-43ad-11ed-8c8e-f631763a04db"
I1004 06:28:46.374933    6294 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-959c85e841-b5f09.test-cncf-aws.k8s.io/id_ed25519
I1004 06:28:46.381554    6294 dumplogs.go:45] /tmp/kops.1v7u0ikwb toolbox dump --name e2e-959c85e841-b5f09.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-959c85e841-b5f09.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I1004 06:28:46.381709    6294 local.go:42] ⚙️ /tmp/kops.1v7u0ikwb toolbox dump --name e2e-959c85e841-b5f09.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-959c85e841-b5f09.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W1004 06:28:46.910432    6294 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1004 06:28:46.910475    6294 down.go:48] /tmp/kops.1v7u0ikwb delete cluster --name e2e-959c85e841-b5f09.test-cncf-aws.k8s.io --yes
I1004 06:28:46.910486    6294 local.go:42] ⚙️ /tmp/kops.1v7u0ikwb delete cluster --name e2e-959c85e841-b5f09.test-cncf-aws.k8s.io --yes
I1004 06:28:46.931472    6317 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I1004 06:28:46.931563    6317 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-959c85e841-b5f09.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.23.4
++ local kops
+++ mktemp -t kops.XXXXXXXXX
++ kops=/tmp/kops.dvrPWHYXb
... skipping 10 lines ...
I1004 06:28:49.113772    6351 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I1004 06:28:49.113794    6351 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/8ec76b57-43ad-11ed-8c8e-f631763a04db"
I1004 06:28:49.144288    6351 app.go:128] ID for this run: "8ec76b57-43ad-11ed-8c8e-f631763a04db"
I1004 06:28:49.144631    6351 up.go:44] Cleaning up any leaked resources from previous cluster
I1004 06:28:49.144774    6351 dumplogs.go:45] /tmp/kops.dvrPWHYXb toolbox dump --name e2e-959c85e841-b5f09.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-959c85e841-b5f09.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I1004 06:28:49.144849    6351 local.go:42] ⚙️ /tmp/kops.dvrPWHYXb toolbox dump --name e2e-959c85e841-b5f09.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-959c85e841-b5f09.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W1004 06:28:49.608600    6351 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1004 06:28:49.608812    6351 down.go:48] /tmp/kops.dvrPWHYXb delete cluster --name e2e-959c85e841-b5f09.test-cncf-aws.k8s.io --yes
I1004 06:28:49.608884    6351 local.go:42] ⚙️ /tmp/kops.dvrPWHYXb delete cluster --name e2e-959c85e841-b5f09.test-cncf-aws.k8s.io --yes
I1004 06:28:49.631629    6374 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I1004 06:28:49.632635    6374 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-959c85e841-b5f09.test-cncf-aws.k8s.io" not found
I1004 06:28:50.116846    6351 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/10/04 06:28: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
I1004 06:28:50.132067    6351 http.go:37] curl https://ip.jsb.workers.dev
I1004 06:28:50.239563    6351 up.go:159] /tmp/kops.dvrPWHYXb create cluster --name e2e-959c85e841-b5f09.test-cncf-aws.k8s.io --cloud aws --kubernetes-version v1.22.1 --ssh-public-key /tmp/kops/e2e-959c85e841-b5f09.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --networking calico --admin-access 34.171.12.199/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-1a --master-size c5.large
I1004 06:28:50.239613    6351 local.go:42] ⚙️ /tmp/kops.dvrPWHYXb create cluster --name e2e-959c85e841-b5f09.test-cncf-aws.k8s.io --cloud aws --kubernetes-version v1.22.1 --ssh-public-key /tmp/kops/e2e-959c85e841-b5f09.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --networking calico --admin-access 34.171.12.199/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-1a --master-size c5.large
I1004 06:28:50.258768    6384 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I1004 06:28:50.258860    6384 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I1004 06:28:50.282153    6384 create_cluster.go:843] Using SSH public key: /tmp/kops/e2e-959c85e841-b5f09.test-cncf-aws.k8s.io/id_ed25519.pub
... skipping 555 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
W1004 06:29:40.441247    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:29:50.475568    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:30:00.515436    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:30:10.557214    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:30:20.600902    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:30:30.638098    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:30:40.688770    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:30:50.737095    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:31:00.777864    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:31:10.827939    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:31:20.867111    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:31:30.917830    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:31:40.956623    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:31:50.996542    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:32:01.033670    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:32:11.074263    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:32:21.106389    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:32:31.142329    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:32:41.179303    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:32:51.213935    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:33:01.270417    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:33:11.321259    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:33:21.359261    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:33:31.398891    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:33:41.439748    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:33:51.476470    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:34:01.514624    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W1004 06:34:11.565299    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 13 lines ...
Pod	kube-system/calico-node-nwdqf				system-node-critical pod "calico-node-nwdqf" is pending
Pod	kube-system/coredns-56dd667f7c-pkz29			system-cluster-critical pod "coredns-56dd667f7c-pkz29" is pending
Pod	kube-system/coredns-autoscaler-5c7694cfcc-qrr5z		system-cluster-critical pod "coredns-autoscaler-5c7694cfcc-qrr5z" is pending
Pod	kube-system/ebs-csi-node-lmsv4				system-node-critical pod "ebs-csi-node-lmsv4" is pending
Pod	kube-system/ebs-csi-node-wlt6c				system-node-critical pod "ebs-csi-node-wlt6c" is pending

Validation Failed
W1004 06:34:25.241936    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 14 lines ...
Pod	kube-system/coredns-56dd667f7c-pkz29			system-cluster-critical pod "coredns-56dd667f7c-pkz29" is pending
Pod	kube-system/coredns-autoscaler-5c7694cfcc-qrr5z		system-cluster-critical pod "coredns-autoscaler-5c7694cfcc-qrr5z" is pending
Pod	kube-system/ebs-csi-node-dw98t				system-node-critical pod "ebs-csi-node-dw98t" is pending
Pod	kube-system/ebs-csi-node-lmsv4				system-node-critical pod "ebs-csi-node-lmsv4" is pending
Pod	kube-system/ebs-csi-node-wlt6c				system-node-critical pod "ebs-csi-node-wlt6c" is pending

Validation Failed
W1004 06:34:38.049368    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/coredns-autoscaler-5c7694cfcc-qrr5z				system-cluster-critical pod "coredns-autoscaler-5c7694cfcc-qrr5z" is pending
Pod	kube-system/ebs-csi-node-dw98t						system-node-critical pod "ebs-csi-node-dw98t" is pending
Pod	kube-system/ebs-csi-node-lmsv4						system-node-critical pod "ebs-csi-node-lmsv4" is pending
Pod	kube-system/ebs-csi-node-wlt6c						system-node-critical pod "ebs-csi-node-wlt6c" is pending
Pod	kube-system/kube-proxy-ip-172-20-45-119.ap-northeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-45-119.ap-northeast-1.compute.internal" is pending

Validation Failed
W1004 06:34:50.635572    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Machine	i-0a0e4be18856b93c8							machine "i-0a0e4be18856b93c8" has not yet joined cluster
Pod	kube-system/ebs-csi-node-dw98t						system-node-critical pod "ebs-csi-node-dw98t" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-153.ap-northeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-153.ap-northeast-1.compute.internal" is pending

Validation Failed
W1004 06:35:03.312906    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Machine	i-0a0e4be18856b93c8							machine "i-0a0e4be18856b93c8" has not yet joined cluster
Pod	kube-system/ebs-csi-node-dw98t						system-node-critical pod "ebs-csi-node-dw98t" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-72.ap-northeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-72.ap-northeast-1.compute.internal" is pending

Validation Failed
W1004 06:35:15.823632    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:35:28.330057    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:35:40.833132    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:35:53.352747    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:36:05.890951    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:36:18.414015    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:36:30.933645    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:36:43.472890    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:36:56.071552    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:37:08.739192    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:37:21.305604    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:37:33.771637    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:37:46.369592    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:37:58.881722    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:38:11.438122    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:38:24.443008    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:38:37.007300    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:38:49.540153    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:39:02.080976    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:39:14.643758    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:39:27.212516    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:39:39.703847    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:39:52.292434    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:40:04.932722    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:40:17.485391    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:40:30.162373    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:40:42.670645    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:40:55.144907    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:41:07.671492    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:41:20.279192    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:41:32.793078    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:41:45.430981    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:41:58.055923    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:42:10.639093    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:42:23.586225    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:42:36.138729    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:42:48.710415    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:43:01.266625    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:43:13.852453    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:43:26.346078    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:43:38.858586    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:43:51.502683    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:44:04.104563    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:44:16.600989    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:44:29.083883    6423 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 5 lines ...
ip-172-20-45-119.ap-northeast-1.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0a0e4be18856b93c8	machine "i-0a0e4be18856b93c8" has not yet joined cluster

Validation Failed
W1004 06:44:41.580672    6423 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-959c85e841-b5f09.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.dvrPWHYXb --down
I1004 06:44:51.635607    6440 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I1004 06:44:51.637048    6440 app.go:61] The files in RunDir shall not be part of Artifacts
I1004 06:44:51.637070    6440 app.go:62] pass rundir-in-artifacts flag True for RunDir to be part of Artifacts
I1004 06:44:51.637112    6440 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/8ec76b57-43ad-11ed-8c8e-f631763a04db"
... skipping 446 lines ...