This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-16 07:49
Elapsed19m7s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 129 lines ...
I0916 07:50:34.181235    4083 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.23.0-alpha.2+v1.23.0-alpha.1-140-g5a6b55d7ba/linux/amd64/kops
I0916 07:50:34.940418    4083 up.go:43] Cleaning up any leaked resources from previous cluster
I0916 07:50:34.940483    4083 dumplogs.go:38] /logs/artifacts/8f182365-16c2-11ec-a0c8-aafcb65c973d/kops toolbox dump --name e2e-4745673676-fbf9c.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0916 07:50:34.956672    4101 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 07:50:34.956810    4101 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0916 07:50:34.956815    4101 featureflag.go:166] FeatureFlag "AWSIPv6"=true
Error: Cluster.kops.k8s.io "e2e-4745673676-fbf9c.test-cncf-aws.k8s.io" not found
W0916 07:50:35.698970    4083 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0916 07:50:35.699019    4083 down.go:48] /logs/artifacts/8f182365-16c2-11ec-a0c8-aafcb65c973d/kops delete cluster --name e2e-4745673676-fbf9c.test-cncf-aws.k8s.io --yes
I0916 07:50:35.718529    4111 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 07:50:35.718650    4111 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0916 07:50:35.718670    4111 featureflag.go:166] FeatureFlag "AWSIPv6"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-4745673676-fbf9c.test-cncf-aws.k8s.io" not found
I0916 07:50:36.191822    4083 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/16 07:50:36 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
I0916 07:50:36.198954    4083 http.go:37] curl https://ip.jsb.workers.dev
I0916 07:50:36.281077    4083 up.go:144] /logs/artifacts/8f182365-16c2-11ec-a0c8-aafcb65c973d/kops create cluster --name e2e-4745673676-fbf9c.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.2.36+25e52d91775db4 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20210907 --channel=alpha --networking=calico --container-runtime=containerd --ipv6 --api-loadbalancer-type=public --api-loadbalancer-class=network --set=cluster.spec.api.loadBalancer.useForInternalApi=true --set=cluster.spec.cloudControllerManager.cloudProvider=aws --set=cluster.spec.nonMasqueradeCIDR=fd00:10:96::/64 --admin-access 34.123.225.205/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large
I0916 07:50:36.298507    4121 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 07:50:36.298689    4121 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0916 07:50:36.298725    4121 featureflag.go:166] FeatureFlag "AWSIPv6"=true
I0916 07:50:36.322280    4121 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
... skipping 35 lines ...
I0916 07:50:53.910652    4083 up.go:181] /logs/artifacts/8f182365-16c2-11ec-a0c8-aafcb65c973d/kops validate cluster --name e2e-4745673676-fbf9c.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0916 07:50:53.954372    4143 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 07:50:53.954479    4143 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0916 07:50:53.954485    4143 featureflag.go:166] FeatureFlag "AWSIPv6"=true
Validating cluster e2e-4745673676-fbf9c.test-cncf-aws.k8s.io

W0916 07:50:55.023212    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:51:05.056589    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:51:15.091331    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:51:25.155700    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:51:35.217663    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:51:45.263267    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:51:55.304378    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:52:05.331097    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:52:15.363103    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:52:25.500814    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:52:35.546500    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:52:45.575242    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:52:55.604913    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:53:05.636212    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:53:15.652753    4143 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 07:53:55.684733    4143 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 3.13.104.157:443: i/o timeout
W0916 07:54:35.715029    4143 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 3.13.104.157:443: i/o timeout
W0916 07:54:45.774338    4143 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-4745673676-fbf9c.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp [2600:1f16:eb3:ba01:9ca9:69a0:1418:afab]:443: connect: network is unreachable
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
... skipping 15 lines ...
Pod	kube-system/coredns-5dc785954d-qfgpl		system-cluster-critical pod "coredns-5dc785954d-qfgpl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-htgwf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-htgwf" is pending
Pod	kube-system/ebs-csi-node-4nxbx			system-node-critical pod "ebs-csi-node-4nxbx" is pending
Pod	kube-system/ebs-csi-node-hhnjl			system-node-critical pod "ebs-csi-node-hhnjl" is pending
Pod	kube-system/ebs-csi-node-tgkp6			system-node-critical pod "ebs-csi-node-tgkp6" is pending

Validation Failed
W0916 07:55:12.444678    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 16 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-htgwf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-htgwf" is pending
Pod	kube-system/ebs-csi-node-4nxbx			system-node-critical pod "ebs-csi-node-4nxbx" is pending
Pod	kube-system/ebs-csi-node-7gcnr			system-node-critical pod "ebs-csi-node-7gcnr" is pending
Pod	kube-system/ebs-csi-node-hhnjl			system-node-critical pod "ebs-csi-node-hhnjl" is pending
Pod	kube-system/ebs-csi-node-tgkp6			system-node-critical pod "ebs-csi-node-tgkp6" is pending

Validation Failed
W0916 07:55:23.383089    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 13 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-htgwf	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-htgwf" is pending
Pod	kube-system/ebs-csi-node-4nxbx			system-node-critical pod "ebs-csi-node-4nxbx" is pending
Pod	kube-system/ebs-csi-node-7gcnr			system-node-critical pod "ebs-csi-node-7gcnr" is pending
Pod	kube-system/ebs-csi-node-hhnjl			system-node-critical pod "ebs-csi-node-hhnjl" is pending
Pod	kube-system/ebs-csi-node-tgkp6			system-node-critical pod "ebs-csi-node-tgkp6" is pending

Validation Failed
W0916 07:55:34.455603    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-qfgpl	system-cluster-critical pod "coredns-5dc785954d-qfgpl" is pending
Pod	kube-system/ebs-csi-node-4nxbx		system-node-critical pod "ebs-csi-node-4nxbx" is pending
Pod	kube-system/ebs-csi-node-7gcnr		system-node-critical pod "ebs-csi-node-7gcnr" is pending
Pod	kube-system/ebs-csi-node-tgkp6		system-node-critical pod "ebs-csi-node-tgkp6" is pending

Validation Failed
W0916 07:55:45.346784    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 9 lines ...
KIND	NAME									MESSAGE
Pod	kube-system/ebs-csi-node-4nxbx						system-node-critical pod "ebs-csi-node-4nxbx" is pending
Pod	kube-system/ebs-csi-node-7gcnr						system-node-critical pod "ebs-csi-node-7gcnr" is pending
Pod	kube-system/ebs-csi-node-tgkp6						system-node-critical pod "ebs-csi-node-tgkp6" is pending
Pod	kube-system/kube-proxy-ip-172-20-36-153.us-east-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-36-153.us-east-2.compute.internal" is pending

Validation Failed
W0916 07:55:56.258671    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 81 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:57:02.034929    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:57:12.914579    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:57:23.957178    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:57:34.909510    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:57:45.842980    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:57:56.769943    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:58:07.822920    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 51 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:58:51.484362    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:59:02.479244    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:59:13.364635    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:59:24.293274    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:59:35.186373    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:59:46.102685    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 07:59:57.060310    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:00:07.958073    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:00:18.907704    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:00:29.839708    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:00:40.817709    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:00:51.863829    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:01:02.951796    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:01:13.927447    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:01:24.872902    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:01:35.796614    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 51 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:02:20.941682    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:02:32.886651    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:02:43.787297    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:02:54.815083    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:03:06.022314    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:03:16.989826    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:03:28.063527    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:03:39.257451    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:03:50.223321    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:04:01.149701    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:04:12.018979    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:04:23.143671    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:04:34.017996    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:04:44.994801    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:04:55.830927    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:05:07.180166    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:05:18.088332    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:05:29.090897    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:05:39.981490    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 6 lines ...
ip-172-20-55-41.us-east-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-46-172.us-east-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 08:05:50.982525    4143 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0916 08:06:00.987307    4083 dumplogs.go:38] /logs/artifacts/8f182365-16c2-11ec-a0c8-aafcb65c973d/kops toolbox dump --name e2e-4745673676-fbf9c.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0916 08:06:01.031578    4156 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 08:06:01.031789    4156 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0916 08:06:01.031824    4156 featureflag.go:166] FeatureFlag "AWSIPv6"=true
2021/09/16 08:06:07 Dumping node ip-172-20-36-153.us-east-2.compute.internal
2021/09/16 08:06:10 Dumping node ip-172-20-42-14.us-east-2.compute.internal
... skipping 1530 lines ...
route-table:rtb-0252c054f7d9b06a6	ok
vpc:vpc-062a53c9e4272d5e8	ok
dhcp-options:dopt-05050d9ccf275703b	ok
Deleted kubectl config for e2e-4745673676-fbf9c.test-cncf-aws.k8s.io

Deleted cluster: "e2e-4745673676-fbf9c.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace