This job view page is being replaced by Spyglass soon. Check out the new job view.
PRtorredil: Driver v1.6.1 post-release
ResultABORTED
Tests 0 failed / 58 succeeded
Started2022-05-02 21:53
Elapsed22m49s
Revisionad9f05149d4d2e7b014af510ec1db64c406fc762
Refs 1225

No Test Failures!


Show 58 Passed Tests

Show 427 Skipped Tests

Error lines from build-log.txt

... skipping 419 lines ...
#8 12.46   Installing : 7:device-mapper-libs-1.02.170-6.amzn2.5.x86_64             23/32 
#8 12.53   Installing : cryptsetup-libs-1.7.4-4.amzn2.x86_64                       24/32 
#8 12.61   Installing : elfutils-libs-0.176-2.amzn2.x86_64                         25/32 
#8 12.70   Installing : systemd-libs-219-78.amzn2.0.16.x86_64                      26/32 
#8 12.76   Installing : 1:dbus-libs-1.10.24-7.amzn2.x86_64                         27/32 
#8 13.79   Installing : systemd-219-78.amzn2.0.16.x86_64                           28/32 
#8 14.17 Failed to get D-Bus connection: Operation not permitted
#8 14.20   Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           29/32 
#8 14.33   Installing : 1:dbus-1.10.24-7.amzn2.x86_64                              30/32 
#8 14.47   Installing : e2fsprogs-1.42.9-19.amzn2.x86_64                           31/32 
#8 14.67   Installing : xfsprogs-4.5.0-18.amzn2.0.1.x86_64                         32/32 
#8 14.74   Verifying  : libfdisk-2.30.2-2.amzn2.0.7.x86_64                          1/32 
#8 14.76   Verifying  : lz4-1.7.5-2.amzn2.0.1.x86_64                                2/32 
... skipping 219 lines ...
## Validating cluster test-cluster-16349.k8s.local
#
Using cluster from kubectl context: test-cluster-16349.k8s.local

Validating cluster test-cluster-16349.k8s.local

W0502 21:56:00.263226    6254 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0502 21:56:10.303644    6254 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0502 21:56:20.342801    6254 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0502 21:56:30.375661    6254 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0502 21:56:40.411958    6254 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0502 21:56:57.415632    6254 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0502 21:57:15.523710    6254 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0502 21:57:32.472207    6254 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-16349-k8-5fmlcg-1564779311.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0502 21:57:54.150276    6254 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)
W0502 21:58:15.836945    6254 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)
W0502 21:58:37.469122    6254 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
nodes-us-west-2c	Node	c5.large	1	1	us-west-2c
... skipping 6 lines ...
KIND	NAME						MESSAGE
Machine	i-0015835445dd31b1f				machine "i-0015835445dd31b1f" has not yet joined cluster
Machine	i-05ef6e17ce00b3fa8				machine "i-05ef6e17ce00b3fa8" has not yet joined cluster
Machine	i-0f5e73142df9bc97c				machine "i-0f5e73142df9bc97c" has not yet joined cluster
Node	ip-172-20-56-127.us-west-2.compute.internal	node "ip-172-20-56-127.us-west-2.compute.internal" of role "master" is not ready

Validation Failed
W0502 21:58:50.254728    6254 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 11 lines ...
Node	ip-172-20-56-127.us-west-2.compute.internal	master "ip-172-20-56-127.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-56-127.us-west-2.compute.internal	master "ip-172-20-56-127.us-west-2.compute.internal" is missing kube-controller-manager pod
Node	ip-172-20-56-127.us-west-2.compute.internal	master "ip-172-20-56-127.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-qgr5t		system-cluster-critical pod "coredns-8f5559c9b-qgr5t" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-qtqq7	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-qtqq7" is pending

Validation Failed
W0502 21:59:02.631612    6254 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 14 lines ...
Pod	kube-system/coredns-8f5559c9b-qgr5t						system-cluster-critical pod "coredns-8f5559c9b-qgr5t" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-qtqq7					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-qtqq7" is pending
Pod	kube-system/etcd-manager-events-ip-172-20-56-127.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-events-ip-172-20-56-127.us-west-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-56-127.us-west-2.compute.internal		system-node-critical pod "kube-proxy-ip-172-20-56-127.us-west-2.compute.internal" is pending
Pod	kube-system/kube-scheduler-ip-172-20-56-127.us-west-2.compute.internal		system-cluster-critical pod "kube-scheduler-ip-172-20-56-127.us-west-2.compute.internal" is pending

Validation Failed
W0502 21:59:14.764439    6254 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 11 lines ...
Node	ip-172-20-56-127.us-west-2.compute.internal				master "ip-172-20-56-127.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-56-127.us-west-2.compute.internal				master "ip-172-20-56-127.us-west-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-8f5559c9b-qgr5t					system-cluster-critical pod "coredns-8f5559c9b-qgr5t" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-qtqq7				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-qtqq7" is pending
Pod	kube-system/kube-apiserver-ip-172-20-56-127.us-west-2.compute.internal	system-cluster-critical pod "kube-apiserver-ip-172-20-56-127.us-west-2.compute.internal" is pending

Validation Failed
W0502 21:59:27.058694    6254 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 9 lines ...
Machine	i-05ef6e17ce00b3fa8								machine "i-05ef6e17ce00b3fa8" has not yet joined cluster
Machine	i-0f5e73142df9bc97c								machine "i-0f5e73142df9bc97c" has not yet joined cluster
Pod	kube-system/coredns-8f5559c9b-qgr5t						system-cluster-critical pod "coredns-8f5559c9b-qgr5t" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-qtqq7					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-qtqq7" is pending
Pod	kube-system/etcd-manager-main-ip-172-20-56-127.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-main-ip-172-20-56-127.us-west-2.compute.internal" is pending

Validation Failed
W0502 21:59:39.288583    6254 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 11 lines ...
Node	ip-172-20-101-110.us-west-2.compute.internal	node "ip-172-20-101-110.us-west-2.compute.internal" of role "node" is not ready
Node	ip-172-20-48-190.us-west-2.compute.internal	node "ip-172-20-48-190.us-west-2.compute.internal" of role "node" is not ready
Node	ip-172-20-83-2.us-west-2.compute.internal	node "ip-172-20-83-2.us-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-8f5559c9b-qgr5t		system-cluster-critical pod "coredns-8f5559c9b-qgr5t" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-qtqq7	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-qtqq7" is pending

Validation Failed
W0502 21:59:51.536341    6254 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 8 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-8f5559c9b-66c9x	system-cluster-critical pod "coredns-8f5559c9b-66c9x" is not ready (coredns)
Pod	kube-system/coredns-8f5559c9b-qgr5t	system-cluster-critical pod "coredns-8f5559c9b-qgr5t" is not ready (coredns)

Validation Failed
W0502 22:00:04.063612    6254 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	c5.large	1	1	us-west-2a
nodes-us-west-2b	Node	c5.large	1	1	us-west-2b
... skipping 49 lines ...