This job view page is being replaced by Spyglass soon. Check out the new job view.
PRvdhanan: instance metadata issue fix
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-04-27 22:13
Elapsed9m41s
Revision72d1dd9f9a54566547fa298070b43527f3fd5f60
Refs 855

No Test Failures!


Error lines from build-log.txt

... skipping 787 lines ...
## Validating cluster test-cluster-15488.k8s.local
#
Using cluster from kubectl context: test-cluster-15488.k8s.local

Validating cluster test-cluster-15488.k8s.local

W0427 22:18:29.087613    9296 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-15488-k8-grojcq-852260479.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-15488-k8-grojcq-852260479.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0427 22:18:39.122026    9296 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-15488-k8-grojcq-852260479.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-15488-k8-grojcq-852260479.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0427 22:18:49.154994    9296 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-15488-k8-grojcq-852260479.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-15488-k8-grojcq-852260479.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0427 22:18:59.201580    9296 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-15488-k8-grojcq-852260479.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-15488-k8-grojcq-852260479.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0427 22:19:20.900107    9296 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0427 22:19:42.545968    9296 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0427 22:20:04.171915    9296 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0427 22:20:25.790978    9296 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0427 22:20:47.431358    9296 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0427 22:21:09.604283    9296 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
W0427 22:21:31.224278    9296 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: an error on the server ("") has prevented the request from succeeding (get nodes)
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

NODE STATUS
... skipping 4 lines ...
KIND	NAME						MESSAGE
Machine	i-095e509db862918cd				machine "i-095e509db862918cd" has not yet joined cluster
Machine	i-09e37c87b5d32fe05				machine "i-09e37c87b5d32fe05" has not yet joined cluster
Machine	i-09f33a6689e01e36b				machine "i-09f33a6689e01e36b" has not yet joined cluster
Node	ip-172-20-62-59.us-west-2.compute.internal	master "ip-172-20-62-59.us-west-2.compute.internal" is not ready

Validation Failed
W0427 22:21:42.880420    9296 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 4 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-095e509db862918cd	machine "i-095e509db862918cd" has not yet joined cluster
Machine	i-09e37c87b5d32fe05	machine "i-09e37c87b5d32fe05" has not yet joined cluster
Machine	i-09f33a6689e01e36b	machine "i-09f33a6689e01e36b" has not yet joined cluster

Validation Failed
W0427 22:21:54.098221    9296 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 4 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-095e509db862918cd	machine "i-095e509db862918cd" has not yet joined cluster
Machine	i-09e37c87b5d32fe05	machine "i-09e37c87b5d32fe05" has not yet joined cluster
Machine	i-09f33a6689e01e36b	machine "i-09f33a6689e01e36b" has not yet joined cluster

Validation Failed
W0427 22:22:05.161223    9296 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 4 lines ...
VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-095e509db862918cd	machine "i-095e509db862918cd" has not yet joined cluster
Machine	i-09e37c87b5d32fe05	machine "i-09e37c87b5d32fe05" has not yet joined cluster
Machine	i-09f33a6689e01e36b	machine "i-09f33a6689e01e36b" has not yet joined cluster

Validation Failed
W0427 22:22:16.291604    9296 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 7 lines ...
Machine	i-09e37c87b5d32fe05				machine "i-09e37c87b5d32fe05" has not yet joined cluster
Machine	i-09f33a6689e01e36b				machine "i-09f33a6689e01e36b" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-ng5cz		system-cluster-critical pod "coredns-5489b75945-ng5cz" is pending
Pod	kube-system/dns-controller-cd496f988-kv5ps	system-cluster-critical pod "dns-controller-cd496f988-kv5ps" is pending
Pod	kube-system/kops-controller-r62tm		system-node-critical pod "kops-controller-r62tm" is pending

Validation Failed
W0427 22:22:27.409306    9296 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 6 lines ...
Machine	i-095e509db862918cd				machine "i-095e509db862918cd" has not yet joined cluster
Machine	i-09e37c87b5d32fe05				machine "i-09e37c87b5d32fe05" has not yet joined cluster
Machine	i-09f33a6689e01e36b				machine "i-09f33a6689e01e36b" has not yet joined cluster
Pod	kube-system/coredns-5489b75945-ng5cz		system-cluster-critical pod "coredns-5489b75945-ng5cz" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-mms46	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-mms46" is pending

Validation Failed
W0427 22:22:38.591433    9296 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 11 lines ...
Node	ip-172-20-43-31.us-west-2.compute.internal				node "ip-172-20-43-31.us-west-2.compute.internal" is not ready
Pod	kube-system/coredns-5489b75945-ng5cz					system-cluster-critical pod "coredns-5489b75945-ng5cz" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-mms46				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-mms46" is pending
Pod	kube-system/kube-proxy-ip-172-20-38-37.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-38-37.us-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-40-237.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-40-237.us-west-2.compute.internal" is pending

Validation Failed
W0427 22:22:49.770920    9296 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 6 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5489b75945-l5xp5	system-cluster-critical pod "coredns-5489b75945-l5xp5" is not ready (coredns)
Pod	kube-system/coredns-5489b75945-ng5cz	system-cluster-critical pod "coredns-5489b75945-ng5cz" is pending

Validation Failed
W0427 22:23:00.998606    9296 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	t3.medium	1	1	us-west-2a
nodes-us-west-2a	Node	c4.large	3	3	us-west-2a

... skipping 6 lines ...

Your cluster test-cluster-15488.k8s.local is ready
###
## Deploying driver
#
Release "aws-ebs-csi-driver" does not exist. Installing it now.
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(DaemonSet.spec.template.spec.containers[0].env[1]): unknown field "fieldRef" in io.k8s.api.core.v1.EnvVar
make: *** [Makefile:104: test-e2e-external] Error 1
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...