This job view page is being replaced by Spyglass soon. Check out the new job view.
PRwongma7: Search for nvme device path even if non-nvme exists
ResultABORTED
Tests 0 failed / 2 succeeded
Started2021-10-08 00:46
Elapsed14m10s
Revision9ea0250d52c44657dcc712492a135551afbab562
Refs 1082

No Test Failures!


Show 2 Passed Tests

Show 31 Skipped Tests

Error lines from build-log.txt

... skipping 438 lines ...
#7 extracting sha256:76ce7ff85fa6acfe5336c6e254a5668a56c9d1828f3070d137884cc80cb5bf45 9.1s
#7 ...

#6 [linux-amazon 2/3] RUN yum update -y &&     yum install ca-certificates e2fsprogs xfsprogs util-linux -y &&     yum clean all
#6 28.76   Installing : 1:dbus-libs-1.10.24-7.amzn2.x86_64                         27/32 
#6 30.75   Installing : systemd-219-78.amzn2.0.15.x86_64                           28/32 
#6 31.74 Failed to get D-Bus connection: Operation not permitted
#6 31.86   Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           29/32 
#6 32.30   Installing : 1:dbus-1.10.24-7.amzn2.x86_64                              30/32 
#6 32.70   Installing : e2fsprogs-1.42.9-19.amzn2.x86_64                           31/32 
#6 33.22   Installing : xfsprogs-4.5.0-18.amzn2.0.1.x86_64                         32/32 
#6 33.91   Verifying  : cracklib-2.9.0-11.amzn2.0.2.x86_64                          1/32 
#6 33.96   Verifying  : gzip-1.5-10.amzn2.x86_64                                    2/32 
... skipping 210 lines ...
## Validating cluster test-cluster-18370.k8s.local
#
Using cluster from kubectl context: test-cluster-18370.k8s.local

Validating cluster test-cluster-18370.k8s.local

W1008 00:50:55.206792    6159 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18370-k8-34klcv-1611126998.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18370-k8-34klcv-1611126998.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1008 00:51:05.255699    6159 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18370-k8-34klcv-1611126998.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18370-k8-34klcv-1611126998.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1008 00:51:15.311682    6159 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18370-k8-34klcv-1611126998.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18370-k8-34klcv-1611126998.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1008 00:51:25.359193    6159 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18370-k8-34klcv-1611126998.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18370-k8-34klcv-1611126998.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1008 00:51:38.902792    6159 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18370-k8-34klcv-1611126998.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18370-k8-34klcv-1611126998.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1008 00:51:53.614710    6159 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18370-k8-34klcv-1611126998.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18370-k8-34klcv-1611126998.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1008 00:52:15.338882    6159 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)
W1008 00:52:37.052611    6159 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)
W1008 00:52:58.800876    6159 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)
W1008 00:53:20.472728    6159 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 9 lines ...
Machine	i-095740d9705a53f84				machine "i-095740d9705a53f84" has not yet joined cluster
Node	ip-172-20-58-40.us-west-2.compute.internal	node "ip-172-20-58-40.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-8f5559c9b-v9jx9		system-cluster-critical pod "coredns-8f5559c9b-v9jx9" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-jqgzc	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-jqgzc" is pending
Pod	kube-system/dns-controller-5d59c585d8-5w99x	system-cluster-critical pod "dns-controller-5d59c585d8-5w99x" is pending

Validation Failed
W1008 00:53:37.908825    6159 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 13 lines ...
Node	ip-172-20-58-40.us-west-2.compute.internal	master "ip-172-20-58-40.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-v9jx9		system-cluster-critical pod "coredns-8f5559c9b-v9jx9" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-jqgzc	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-jqgzc" is pending
Pod	kube-system/dns-controller-5d59c585d8-5w99x	system-cluster-critical pod "dns-controller-5d59c585d8-5w99x" is pending
Pod	kube-system/kops-controller-q5jkt		system-node-critical pod "kops-controller-q5jkt" is pending

Validation Failed
W1008 00:53:50.172195    6159 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 10 lines ...
Machine	i-095740d9705a53f84				machine "i-095740d9705a53f84" has not yet joined cluster
Node	ip-172-20-58-40.us-west-2.compute.internal	master "ip-172-20-58-40.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-58-40.us-west-2.compute.internal	master "ip-172-20-58-40.us-west-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-8f5559c9b-v9jx9		system-cluster-critical pod "coredns-8f5559c9b-v9jx9" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-jqgzc	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-jqgzc" is pending

Validation Failed
W1008 00:54:02.434618    6159 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-58-40.us-west-2.compute.internal					master "ip-172-20-58-40.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-58-40.us-west-2.compute.internal					master "ip-172-20-58-40.us-west-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-8f5559c9b-v9jx9						system-cluster-critical pod "coredns-8f5559c9b-v9jx9" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-jqgzc					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-jqgzc" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-58-40.us-west-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-58-40.us-west-2.compute.internal" is pending

Validation Failed
W1008 00:54:14.827394    6159 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-039f520dfc2a25246				machine "i-039f520dfc2a25246" has not yet joined cluster
Machine	i-095740d9705a53f84				machine "i-095740d9705a53f84" has not yet joined cluster
Node	ip-172-20-58-40.us-west-2.compute.internal	master "ip-172-20-58-40.us-west-2.compute.internal" is missing kube-apiserver pod
Pod	kube-system/coredns-8f5559c9b-v9jx9		system-cluster-critical pod "coredns-8f5559c9b-v9jx9" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-jqgzc	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-jqgzc" is pending

Validation Failed
W1008 00:54:27.189146    6159 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 ...
Machine	i-037d3d52d4fcae1eb				machine "i-037d3d52d4fcae1eb" has not yet joined cluster
Machine	i-039f520dfc2a25246				machine "i-039f520dfc2a25246" has not yet joined cluster
Machine	i-095740d9705a53f84				machine "i-095740d9705a53f84" has not yet joined cluster
Pod	kube-system/coredns-8f5559c9b-v9jx9		system-cluster-critical pod "coredns-8f5559c9b-v9jx9" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-jqgzc	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-jqgzc" is pending

Validation Failed
W1008 00:54:39.719870    6159 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 10 lines ...
KIND	NAME						MESSAGE
Node	ip-172-20-67-8.us-west-2.compute.internal	node "ip-172-20-67-8.us-west-2.compute.internal" of role "node" is not ready
Node	ip-172-20-98-46.us-west-2.compute.internal	node "ip-172-20-98-46.us-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-8f5559c9b-v9jx9		system-cluster-critical pod "coredns-8f5559c9b-v9jx9" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-jqgzc	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-jqgzc" is pending

Validation Failed
W1008 00:54:51.970624    6159 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-44wtn	system-cluster-critical pod "coredns-8f5559c9b-44wtn" is not ready (coredns)
Pod	kube-system/coredns-8f5559c9b-v9jx9	system-cluster-critical pod "coredns-8f5559c9b-v9jx9" is not ready (coredns)

Validation Failed
W1008 00:55:04.263755    6159 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 56 lines ...