This job view page is being replaced by Spyglass soon. Check out the new job view.
PRmichalschott: Better control over log verbosity.
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-07-13 09:10
Elapsed10m43s
Revisioncb59f1453b9514b15e0d7123edfc93531b67f879
Refs 969

No Test Failures!


Error lines from build-log.txt

... skipping 299 lines ...
  Installing : 7:device-mapper-libs-1.02.146-4.amzn2.0.2.x86_64           23/32 
  Installing : cryptsetup-libs-1.7.4-4.amzn2.x86_64                       24/32 
  Installing : elfutils-libs-0.176-2.amzn2.x86_64                         25/32 
  Installing : systemd-libs-219-78.amzn2.0.14.x86_64                      26/32 
  Installing : 1:dbus-libs-1.10.24-7.amzn2.x86_64                         27/32 
  Installing : systemd-219-78.amzn2.0.14.x86_64                           28/32 
Failed to get D-Bus connection: Operation not permitted
  Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           29/32 
  Installing : 1:dbus-1.10.24-7.amzn2.x86_64                              30/32 
  Installing : e2fsprogs-1.42.9-19.amzn2.x86_64                           31/32 
  Installing : xfsprogs-4.5.0-18.amzn2.0.1.x86_64                         32/32 
  Verifying  : gzip-1.5-10.amzn2.x86_64                                    1/32 
  Verifying  : elfutils-default-yama-scope-0.176-2.amzn2.noarch            2/32 
... skipping 461 lines ...
## Validating cluster test-cluster-18810.k8s.local
#
Using cluster from kubectl context: test-cluster-18810.k8s.local

Validating cluster test-cluster-18810.k8s.local

W0713 09:14:34.900622    9315 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 09:14:44.938097    9315 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 09:14:54.974043    9315 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 09:15:05.020383    9315 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 09:15:15.057804    9315 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 09:15:25.094021    9315 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 09:15:35.128965    9315 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 09:15:45.238918    9315 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 09:16:05.820810    9315 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-18810-k8-99pspk-779610584.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0713 09:16:27.509572    9315 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)
W0713 09:16:49.174041    9315 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)
W0713 09:17:10.890045    9315 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)
W0713 09:17:32.636237    9315 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)
W0713 09:17:54.388598    9315 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)
W0713 09:18:16.065314    9315 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-047a88a207577e62b				machine "i-047a88a207577e62b" has not yet joined cluster
Machine	i-0604ca674f02e3d3d				machine "i-0604ca674f02e3d3d" has not yet joined cluster
Machine	i-09863d838f660b8ad				machine "i-09863d838f660b8ad" has not yet joined cluster
Node	ip-172-20-61-90.us-west-2.compute.internal	node "ip-172-20-61-90.us-west-2.compute.internal" of role "master" is not ready

Validation Failed
W0713 09:18:39.387418    9315 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 9 lines ...
Node	ip-172-20-61-90.us-west-2.compute.internal	node "ip-172-20-61-90.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-8f5559c9b-bnzgm		system-cluster-critical pod "coredns-8f5559c9b-bnzgm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-b7qc5	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-b7qc5" is pending
Pod	kube-system/dns-controller-5d59c585d8-xtgbr	system-cluster-critical pod "dns-controller-5d59c585d8-xtgbr" is pending
Pod	kube-system/kops-controller-8gts9		system-node-critical pod "kops-controller-8gts9" is pending

Validation Failed
W0713 09:18:50.816468    9315 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-61-90.us-west-2.compute.internal	master "ip-172-20-61-90.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-bnzgm		system-cluster-critical pod "coredns-8f5559c9b-bnzgm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-b7qc5	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-b7qc5" is pending
Pod	kube-system/dns-controller-5d59c585d8-xtgbr	system-cluster-critical pod "dns-controller-5d59c585d8-xtgbr" is pending
Pod	kube-system/kops-controller-8gts9		system-node-critical pod "kops-controller-8gts9" is pending

Validation Failed
W0713 09:19:02.256975    9315 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 9 lines ...
Node	ip-172-20-61-90.us-west-2.compute.internal					master "ip-172-20-61-90.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-61-90.us-west-2.compute.internal					master "ip-172-20-61-90.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-bnzgm						system-cluster-critical pod "coredns-8f5559c9b-bnzgm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-b7qc5					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-b7qc5" is pending
Pod	kube-system/etcd-manager-main-ip-172-20-61-90.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-main-ip-172-20-61-90.us-west-2.compute.internal" is pending

Validation Failed
W0713 09:19:13.749360    9315 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-0604ca674f02e3d3d				machine "i-0604ca674f02e3d3d" has not yet joined cluster
Machine	i-09863d838f660b8ad				machine "i-09863d838f660b8ad" has not yet joined cluster
Node	ip-172-20-61-90.us-west-2.compute.internal	master "ip-172-20-61-90.us-west-2.compute.internal" is missing kube-apiserver pod
Pod	kube-system/coredns-8f5559c9b-bnzgm		system-cluster-critical pod "coredns-8f5559c9b-bnzgm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-b7qc5	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-b7qc5" is pending

Validation Failed
W0713 09:19:25.113237    9315 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-047a88a207577e62b				machine "i-047a88a207577e62b" has not yet joined cluster
Machine	i-0604ca674f02e3d3d				machine "i-0604ca674f02e3d3d" has not yet joined cluster
Machine	i-09863d838f660b8ad				machine "i-09863d838f660b8ad" has not yet joined cluster
Pod	kube-system/coredns-8f5559c9b-bnzgm		system-cluster-critical pod "coredns-8f5559c9b-bnzgm" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-b7qc5	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-b7qc5" is pending

Validation Failed
W0713 09:19:36.479750    9315 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 ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-35-231.us-west-2.compute.internal	node "ip-172-20-35-231.us-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-8f5559c9b-7hkkk		system-cluster-critical pod "coredns-8f5559c9b-7hkkk" is pending
Pod	kube-system/coredns-8f5559c9b-bnzgm		system-cluster-critical pod "coredns-8f5559c9b-bnzgm" is pending

Validation Failed
W0713 09:19:47.942095    9315 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 5 lines ...
ip-172-20-61-90.us-west-2.compute.internal	master	True

Your cluster test-cluster-18810.k8s.local is ready
###
## Installing snapshot controller and CRDs
#
{"component":"entrypoint","file":"prow/entrypoint/run.go:169","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2021-07-13T09:19:59Z"}
++ early_exit_handler
++ '[' -n 186 ']'
++ kill -TERM 186
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 5 lines ...