This job view page is being replaced by Spyglass soon. Check out the new job view.
PRwongma7: Refactor pkg/cloud/metadata.go into pkg/cloud/metadata_*.go files
ResultABORTED
Tests 0 failed / 2 succeeded
Started2021-09-29 20:36
Elapsed12m51s
Revision78721e31df783ec1ecd5fb77fedf3df6041d3502
Refs 1074

No Test Failures!


Show 2 Passed Tests

Show 31 Skipped Tests

Error lines from build-log.txt

... skipping 463 lines ...

#8 [builder 2/4] WORKDIR /go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver
#8 ...

#6 [linux-amazon 2/3] RUN yum update -y &&     yum install ca-certificates e2fsprogs xfsprogs util-linux -y &&     yum clean all
#6 15.25   Installing : systemd-219-78.amzn2.0.15.x86_64                           28/32 
#6 15.58 Failed to get D-Bus connection: Operation not permitted
#6 16.77   Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           29/32 
#6 17.82   Installing : 1:dbus-1.10.24-7.amzn2.x86_64                              30/32 
#6 18.26   Installing : e2fsprogs-1.42.9-19.amzn2.x86_64                           31/32 
#6 19.86   Installing : xfsprogs-4.5.0-18.amzn2.0.1.x86_64                         32/32 
#6 20.92   Verifying  : cracklib-2.9.0-11.amzn2.0.2.x86_64                          1/32 
#6 21.24   Verifying  : gzip-1.5-10.amzn2.x86_64                                    2/32 
... skipping 207 lines ...
## Validating cluster test-cluster-4948.k8s.local
#
Using cluster from kubectl context: test-cluster-4948.k8s.local

Validating cluster test-cluster-4948.k8s.local

W0929 20:38:44.432741    6084 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0929 20:38:54.462717    6084 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0929 20:39:04.493988    6084 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0929 20:39:14.529754    6084 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0929 20:39:24.557794    6084 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0929 20:39:34.590662    6084 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0929 20:39:57.399619    6084 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)
W0929 20:40:08.574634    6084 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-4948-k8s-qcvhvu-955829476.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W0929 20:40:30.184425    6084 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)
W0929 20:40:51.973814    6084 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)
W0929 20:41:13.585051    6084 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	1	1	us-west-2a
nodes-us-west-2b	Node	c4.large	1	1	us-west-2b
nodes-us-west-2c	Node	c4.large	1	1	us-west-2c
... skipping 6 lines ...
KIND	NAME						MESSAGE
Machine	i-010ea34c0c12ef503				machine "i-010ea34c0c12ef503" has not yet joined cluster
Machine	i-03275c04a3d56fc1a				machine "i-03275c04a3d56fc1a" has not yet joined cluster
Machine	i-080d175217bb2fc9f				machine "i-080d175217bb2fc9f" has not yet joined cluster
Node	ip-172-20-52-81.us-west-2.compute.internal	node "ip-172-20-52-81.us-west-2.compute.internal" of role "master" is not ready

Validation Failed
W0929 20:41:29.839971    6084 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	1	1	us-west-2a
nodes-us-west-2b	Node	c4.large	1	1	us-west-2b
... skipping 10 lines ...
Machine	i-080d175217bb2fc9f				machine "i-080d175217bb2fc9f" has not yet joined cluster
Node	ip-172-20-52-81.us-west-2.compute.internal	node "ip-172-20-52-81.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-8f5559c9b-whzz8		system-cluster-critical pod "coredns-8f5559c9b-whzz8" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-xd8jb	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-xd8jb" is pending
Pod	kube-system/dns-controller-5d59c585d8-rq57k	system-cluster-critical pod "dns-controller-5d59c585d8-rq57k" is pending

Validation Failed
W0929 20:41:42.245303    6084 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	1	1	us-west-2a
nodes-us-west-2b	Node	c4.large	1	1	us-west-2b
... skipping 13 lines ...
Node	ip-172-20-52-81.us-west-2.compute.internal	master "ip-172-20-52-81.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-whzz8		system-cluster-critical pod "coredns-8f5559c9b-whzz8" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-xd8jb	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-xd8jb" is pending
Pod	kube-system/dns-controller-5d59c585d8-rq57k	system-cluster-critical pod "dns-controller-5d59c585d8-rq57k" is pending
Pod	kube-system/kops-controller-xtdjp		system-node-critical pod "kops-controller-xtdjp" is pending

Validation Failed
W0929 20:41:54.998291    6084 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	1	1	us-west-2a
nodes-us-west-2b	Node	c4.large	1	1	us-west-2b
... skipping 11 lines ...
Node	ip-172-20-52-81.us-west-2.compute.internal	master "ip-172-20-52-81.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-52-81.us-west-2.compute.internal	master "ip-172-20-52-81.us-west-2.compute.internal" is missing kube-controller-manager pod
Node	ip-172-20-52-81.us-west-2.compute.internal	master "ip-172-20-52-81.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-whzz8		system-cluster-critical pod "coredns-8f5559c9b-whzz8" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-xd8jb	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-xd8jb" is pending

Validation Failed
W0929 20:42:07.335994    6084 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	1	1	us-west-2a
nodes-us-west-2b	Node	c4.large	1	1	us-west-2b
... skipping 12 lines ...
Node	ip-172-20-52-81.us-west-2.compute.internal					master "ip-172-20-52-81.us-west-2.compute.internal" is missing kube-controller-manager pod
Node	ip-172-20-52-81.us-west-2.compute.internal					master "ip-172-20-52-81.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-whzz8						system-cluster-critical pod "coredns-8f5559c9b-whzz8" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-xd8jb					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-xd8jb" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-52-81.us-west-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-52-81.us-west-2.compute.internal" is pending

Validation Failed
W0929 20:42:19.596159    6084 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	1	1	us-west-2a
nodes-us-west-2b	Node	c4.large	1	1	us-west-2b
... skipping 10 lines ...
Machine	i-080d175217bb2fc9f							machine "i-080d175217bb2fc9f" has not yet joined cluster
Node	ip-172-20-52-81.us-west-2.compute.internal				master "ip-172-20-52-81.us-west-2.compute.internal" is missing kube-apiserver pod
Pod	kube-system/coredns-8f5559c9b-whzz8					system-cluster-critical pod "coredns-8f5559c9b-whzz8" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-xd8jb				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-xd8jb" is pending
Pod	kube-system/kube-apiserver-ip-172-20-52-81.us-west-2.compute.internal	system-cluster-critical pod "kube-apiserver-ip-172-20-52-81.us-west-2.compute.internal" is pending

Validation Failed
W0929 20:42:31.892744    6084 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	1	1	us-west-2a
nodes-us-west-2b	Node	c4.large	1	1	us-west-2b
... skipping 8 lines ...
Machine	i-010ea34c0c12ef503				machine "i-010ea34c0c12ef503" has not yet joined cluster
Machine	i-03275c04a3d56fc1a				machine "i-03275c04a3d56fc1a" has not yet joined cluster
Machine	i-080d175217bb2fc9f				machine "i-080d175217bb2fc9f" has not yet joined cluster
Pod	kube-system/coredns-8f5559c9b-whzz8		system-cluster-critical pod "coredns-8f5559c9b-whzz8" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-xd8jb	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-xd8jb" is pending

Validation Failed
W0929 20:42:44.174655    6084 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	1	1	us-west-2a
nodes-us-west-2b	Node	c4.large	1	1	us-west-2b
... skipping 11 lines ...
Node	ip-172-20-110-98.us-west-2.compute.internal	node "ip-172-20-110-98.us-west-2.compute.internal" of role "node" is not ready
Node	ip-172-20-36-31.us-west-2.compute.internal	node "ip-172-20-36-31.us-west-2.compute.internal" of role "node" is not ready
Node	ip-172-20-70-224.us-west-2.compute.internal	node "ip-172-20-70-224.us-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-8f5559c9b-whzz8		system-cluster-critical pod "coredns-8f5559c9b-whzz8" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-xd8jb	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-xd8jb" is pending

Validation Failed
W0929 20:42:56.379537    6084 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	1	1	us-west-2a
nodes-us-west-2b	Node	c4.large	1	1	us-west-2b
... skipping 7 lines ...
ip-172-20-70-224.us-west-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-8f5559c9b-l5hv7	system-cluster-critical pod "coredns-8f5559c9b-l5hv7" is pending

Validation Failed
W0929 20:43:08.551499    6084 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	1	1	us-west-2a
nodes-us-west-2b	Node	c4.large	1	1	us-west-2b
... skipping 71 lines ...
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/dynamic_provisioning.go:535
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Sep 29 20:44:56.073: INFO: Waiting up to 15m0s for pod "ebs-volume-tester-ntlcn" in namespace "ebs-2010" to be "Succeeded or Failed"
Sep 29 20:44:56.140: INFO: Pod "ebs-volume-tester-ntlcn": Phase="Pending", Reason="", readiness=false. Elapsed: 66.714196ms
Sep 29 20:44:58.206: INFO: Pod "ebs-volume-tester-ntlcn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.133570659s
Sep 29 20:45:00.273: INFO: Pod "ebs-volume-tester-ntlcn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.200306781s
Sep 29 20:45:02.340: INFO: Pod "ebs-volume-tester-ntlcn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.26749485s
Sep 29 20:45:04.410: INFO: Pod "ebs-volume-tester-ntlcn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.33728339s
Sep 29 20:45:06.478: INFO: Pod "ebs-volume-tester-ntlcn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.405111728s
Sep 29 20:45:08.545: INFO: Pod "ebs-volume-tester-ntlcn": Phase="Pending", Reason="", readiness=false. Elapsed: 12.472217467s
Sep 29 20:45:10.612: INFO: Pod "ebs-volume-tester-ntlcn": Phase="Pending", Reason="", readiness=false. Elapsed: 14.538898901s
Sep 29 20:45:12.678: INFO: Pod "ebs-volume-tester-ntlcn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.605528724s
STEP: Saw pod success
Sep 29 20:45:12.679: INFO: Pod "ebs-volume-tester-ntlcn" satisfied condition "Succeeded or Failed"
STEP: validating provisioned PVs
STEP: waiting for PVC to be in phase "Bound"
Sep 29 20:45:12.679: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-zs99t] to have phase Bound
Sep 29 20:45:12.747: INFO: PersistentVolumeClaim pvc-zs99t found and phase=Bound (68.130478ms)
STEP: checking the PVC
STEP: validating provisioned PV
... skipping 29 lines ...