This job view page is being replaced by Spyglass soon. Check out the new job view.
PRwongma7: Reorder isMounted for readability
ResultABORTED
Tests 0 failed / 2 succeeded
Started2021-10-11 23:48
Elapsed12m2s
Revision76848a6c001d5de9dd6b8870039644db53a89193
Refs 1087

No Test Failures!


Show 2 Passed Tests

Show 31 Skipped Tests

Error lines from build-log.txt

... skipping 473 lines ...
#5 25.30   Installing : 7:device-mapper-libs-1.02.170-6.amzn2.5.x86_64             23/32 
#5 25.37   Installing : cryptsetup-libs-1.7.4-4.amzn2.x86_64                       24/32 
#5 25.45   Installing : elfutils-libs-0.176-2.amzn2.x86_64                         25/32 
#5 25.53   Installing : systemd-libs-219-78.amzn2.0.15.x86_64                      26/32 
#5 25.58   Installing : 1:dbus-libs-1.10.24-7.amzn2.x86_64                         27/32 
#5 26.89   Installing : systemd-219-78.amzn2.0.15.x86_64                           28/32 
#5 27.43 Failed to get D-Bus connection: Operation not permitted
#5 27.46   Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           29/32 
#5 27.62   Installing : 1:dbus-1.10.24-7.amzn2.x86_64                              30/32 
#5 27.80   Installing : e2fsprogs-1.42.9-19.amzn2.x86_64                           31/32 
#5 28.04   Installing : xfsprogs-4.5.0-18.amzn2.0.1.x86_64                         32/32 
#5 28.12   Verifying  : cracklib-2.9.0-11.amzn2.0.2.x86_64                          1/32 
#5 28.14   Verifying  : gzip-1.5-10.amzn2.x86_64                                    2/32 
... skipping 192 lines ...
## Validating cluster test-cluster-14764.k8s.local
#
Using cluster from kubectl context: test-cluster-14764.k8s.local

Validating cluster test-cluster-14764.k8s.local

W1011 23:51:18.309624    6025 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-14764-k8-a909fu-1897138654.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-14764-k8-a909fu-1897138654.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1011 23:51:28.342848    6025 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-14764-k8-a909fu-1897138654.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-14764-k8-a909fu-1897138654.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1011 23:51:38.371309    6025 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-14764-k8-a909fu-1897138654.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-14764-k8-a909fu-1897138654.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1011 23:51:48.414762    6025 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-14764-k8-a909fu-1897138654.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-14764-k8-a909fu-1897138654.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1011 23:51:58.458550    6025 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-14764-k8-a909fu-1897138654.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-14764-k8-a909fu-1897138654.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1011 23:52:08.489901    6025 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-14764-k8-a909fu-1897138654.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-14764-k8-a909fu-1897138654.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1011 23:52:30.186272    6025 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)
W1011 23:52:51.874101    6025 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)
W1011 23:53:14.556992    6025 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)
W1011 23:53:36.210856    6025 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-04809767f01e6b348				machine "i-04809767f01e6b348" has not yet joined cluster
Machine	i-08348bfc0d859479d				machine "i-08348bfc0d859479d" has not yet joined cluster
Machine	i-0ff1000f939ea66a5				machine "i-0ff1000f939ea66a5" has not yet joined cluster
Node	ip-172-20-58-230.us-west-2.compute.internal	node "ip-172-20-58-230.us-west-2.compute.internal" of role "master" is not ready

Validation Failed
W1011 23:53:57.079020    6025 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-230.us-west-2.compute.internal	node "ip-172-20-58-230.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-8f5559c9b-m58l4		system-cluster-critical pod "coredns-8f5559c9b-m58l4" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-45nz2	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-45nz2" is pending
Pod	kube-system/dns-controller-5d59c585d8-s4v5q	system-cluster-critical pod "dns-controller-5d59c585d8-s4v5q" is pending
Pod	kube-system/kops-controller-fgnxw		system-node-critical pod "kops-controller-fgnxw" is pending

Validation Failed
W1011 23:54:09.519142    6025 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-m58l4						system-cluster-critical pod "coredns-8f5559c9b-m58l4" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-45nz2					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-45nz2" is pending
Pod	kube-system/etcd-manager-main-ip-172-20-58-230.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-main-ip-172-20-58-230.us-west-2.compute.internal" is pending
Pod	kube-system/kops-controller-fgnxw						system-node-critical pod "kops-controller-fgnxw" is pending
Pod	kube-system/kube-controller-manager-ip-172-20-58-230.us-west-2.compute.internal	system-cluster-critical pod "kube-controller-manager-ip-172-20-58-230.us-west-2.compute.internal" is pending

Validation Failed
W1011 23:54:21.762516    6025 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-08348bfc0d859479d				machine "i-08348bfc0d859479d" has not yet joined cluster
Machine	i-0ff1000f939ea66a5				machine "i-0ff1000f939ea66a5" has not yet joined cluster
Node	ip-172-20-58-230.us-west-2.compute.internal	master "ip-172-20-58-230.us-west-2.compute.internal" is missing kube-apiserver pod
Pod	kube-system/coredns-8f5559c9b-m58l4		system-cluster-critical pod "coredns-8f5559c9b-m58l4" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-45nz2	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-45nz2" is pending

Validation Failed
W1011 23:54:33.877657    6025 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-08348bfc0d859479d				machine "i-08348bfc0d859479d" has not yet joined cluster
Machine	i-0ff1000f939ea66a5				machine "i-0ff1000f939ea66a5" has not yet joined cluster
Node	ip-172-20-58-230.us-west-2.compute.internal	master "ip-172-20-58-230.us-west-2.compute.internal" is missing kube-apiserver pod
Pod	kube-system/coredns-8f5559c9b-m58l4		system-cluster-critical pod "coredns-8f5559c9b-m58l4" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-45nz2	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-45nz2" is pending

Validation Failed
W1011 23:54:46.106550    6025 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-0ff1000f939ea66a5							machine "i-0ff1000f939ea66a5" has not yet joined cluster
Node	ip-172-20-58-230.us-west-2.compute.internal				master "ip-172-20-58-230.us-west-2.compute.internal" is missing kube-apiserver pod
Pod	kube-system/coredns-8f5559c9b-m58l4					system-cluster-critical pod "coredns-8f5559c9b-m58l4" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-45nz2				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-45nz2" is pending
Pod	kube-system/kube-apiserver-ip-172-20-58-230.us-west-2.compute.internal	system-cluster-critical pod "kube-apiserver-ip-172-20-58-230.us-west-2.compute.internal" is pending

Validation Failed
W1011 23:54:58.234297    6025 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-04809767f01e6b348				machine "i-04809767f01e6b348" has not yet joined cluster
Machine	i-08348bfc0d859479d				machine "i-08348bfc0d859479d" has not yet joined cluster
Machine	i-0ff1000f939ea66a5				machine "i-0ff1000f939ea66a5" has not yet joined cluster
Pod	kube-system/coredns-8f5559c9b-m58l4		system-cluster-critical pod "coredns-8f5559c9b-m58l4" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-45nz2	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-45nz2" is pending

Validation Failed
W1011 23:55:10.518467    6025 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-50-203.us-west-2.compute.internal	node "ip-172-20-50-203.us-west-2.compute.internal" of role "node" is not ready
Node	ip-172-20-82-252.us-west-2.compute.internal	node "ip-172-20-82-252.us-west-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-8f5559c9b-m58l4		system-cluster-critical pod "coredns-8f5559c9b-m58l4" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-45nz2	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-45nz2" is pending

Validation Failed
W1011 23:55:22.749437    6025 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 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
Oct 11 23:57:07.650: INFO: Waiting up to 15m0s for pod "ebs-volume-tester-pqg82" in namespace "ebs-5339" to be "Succeeded or Failed"
Oct 11 23:57:07.717: INFO: Pod "ebs-volume-tester-pqg82": Phase="Pending", Reason="", readiness=false. Elapsed: 66.754912ms
Oct 11 23:57:09.784: INFO: Pod "ebs-volume-tester-pqg82": Phase="Pending", Reason="", readiness=false. Elapsed: 2.133872557s
Oct 11 23:57:11.849: INFO: Pod "ebs-volume-tester-pqg82": Phase="Pending", Reason="", readiness=false. Elapsed: 4.199620221s
Oct 11 23:57:13.916: INFO: Pod "ebs-volume-tester-pqg82": Phase="Pending", Reason="", readiness=false. Elapsed: 6.266247423s
Oct 11 23:57:15.982: INFO: Pod "ebs-volume-tester-pqg82": Phase="Pending", Reason="", readiness=false. Elapsed: 8.332421582s
Oct 11 23:57:18.048: INFO: Pod "ebs-volume-tester-pqg82": Phase="Pending", Reason="", readiness=false. Elapsed: 10.398446249s
... skipping 2 lines ...
Oct 11 23:57:24.246: INFO: Pod "ebs-volume-tester-pqg82": Phase="Pending", Reason="", readiness=false. Elapsed: 16.595895034s
Oct 11 23:57:26.312: INFO: Pod "ebs-volume-tester-pqg82": Phase="Pending", Reason="", readiness=false. Elapsed: 18.662541503s
Oct 11 23:57:28.379: INFO: Pod "ebs-volume-tester-pqg82": Phase="Pending", Reason="", readiness=false. Elapsed: 20.729545127s
Oct 11 23:57:30.445: INFO: Pod "ebs-volume-tester-pqg82": Phase="Pending", Reason="", readiness=false. Elapsed: 22.795121519s
Oct 11 23:57:32.511: INFO: Pod "ebs-volume-tester-pqg82": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.860822664s
STEP: Saw pod success
Oct 11 23:57:32.511: INFO: Pod "ebs-volume-tester-pqg82" satisfied condition "Succeeded or Failed"
STEP: validating provisioned PVs
STEP: waiting for PVC to be in phase "Bound"
Oct 11 23:57:32.511: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-sccbs] to have phase Bound
Oct 11 23:57:32.576: INFO: PersistentVolumeClaim pvc-sccbs found and phase=Bound (64.754202ms)
STEP: checking the PVC
STEP: validating provisioned PV
... skipping 42 lines ...
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/dynamic_provisioning.go:508
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
Oct 11 23:57:07.707: INFO: Waiting up to 15m0s for pod "ebs-volume-tester-sttt2" in namespace "ebs-1883" to be "Succeeded or Failed"
Oct 11 23:57:07.775: INFO: Pod "ebs-volume-tester-sttt2": Phase="Pending", Reason="", readiness=false. Elapsed: 67.976094ms
Oct 11 23:57:09.843: INFO: Pod "ebs-volume-tester-sttt2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.136545655s
Oct 11 23:57:11.912: INFO: Pod "ebs-volume-tester-sttt2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.20477947s
Oct 11 23:57:13.980: INFO: Pod "ebs-volume-tester-sttt2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.273293917s
Oct 11 23:57:16.049: INFO: Pod "ebs-volume-tester-sttt2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.341722875s
Oct 11 23:57:18.117: INFO: Pod "ebs-volume-tester-sttt2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.410077203s
... skipping 3 lines ...
Oct 11 23:57:26.398: INFO: Pod "ebs-volume-tester-sttt2": Phase="Pending", Reason="", readiness=false. Elapsed: 18.690867634s
Oct 11 23:57:28.467: INFO: Pod "ebs-volume-tester-sttt2": Phase="Pending", Reason="", readiness=false. Elapsed: 20.760315441s
Oct 11 23:57:30.537: INFO: Pod "ebs-volume-tester-sttt2": Phase="Pending", Reason="", readiness=false. Elapsed: 22.82985327s
Oct 11 23:57:32.605: INFO: Pod "ebs-volume-tester-sttt2": Phase="Pending", Reason="", readiness=false. Elapsed: 24.898528112s
Oct 11 23:57:34.674: INFO: Pod "ebs-volume-tester-sttt2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 26.967083237s
STEP: Saw pod success
Oct 11 23:57:34.674: INFO: Pod "ebs-volume-tester-sttt2" satisfied condition "Succeeded or Failed"
STEP: validating provisioned PVs
STEP: waiting for PVC to be in phase "Bound"
Oct 11 23:57:34.674: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-gxdmj] to have phase Bound
Oct 11 23:57:34.742: INFO: PersistentVolumeClaim pvc-gxdmj found and phase=Bound (67.636157ms)
STEP: checking the PVC
STEP: validating provisioned PV
... skipping 28 lines ...
/home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/dynamic_provisioning.go:493
  should allow for topology aware volume scheduling
  /home/prow/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/tests/e2e/dynamic_provisioning.go:508
------------------------------

Ran 2 of 33 Specs in 64.120 seconds
SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 31 Skipped


Ginkgo ran 1 suite in 1m59.086967997s
Test Suite Passed
+ TEST_PASSED=0
+ set -e
... skipping 361 lines ...
	volume:vol-071673dfdf792385b
	security-group:sg-0880581c9bfafeee3
	subnet:subnet-059936d7baaf30df3
	route-table:rtb-03592f5aa5d53e8a4
	volume:vol-01b420c404917e2a3
	internet-gateway:igw-029512f61626d3870
{"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-10-11T23:59:11Z"}