This job view page is being replaced by Spyglass soon. Check out the new job view.
PRwongma7: Fix windows NodePublish failing because mount target doesn't exist
ResultABORTED
Tests 0 failed / 2 succeeded
Started2021-10-06 19:44
Elapsed11m45s
Revision27215b0f089d4beb53faf3524e841ef65f287032
Refs 1081

No Test Failures!


Show 2 Passed Tests

Show 31 Skipped Tests

Error lines from build-log.txt

... skipping 329 lines ...
#6 12.25   Installing : 7:device-mapper-libs-1.02.170-6.amzn2.5.x86_64             23/32 
#6 12.32   Installing : cryptsetup-libs-1.7.4-4.amzn2.x86_64                       24/32 
#6 12.40   Installing : elfutils-libs-0.176-2.amzn2.x86_64                         25/32 
#6 12.50   Installing : systemd-libs-219-78.amzn2.0.15.x86_64                      26/32 
#6 12.56   Installing : 1:dbus-libs-1.10.24-7.amzn2.x86_64                         27/32 
#6 13.69   Installing : systemd-219-78.amzn2.0.15.x86_64                           28/32 
#6 14.07 Failed to get D-Bus connection: Operation not permitted
#6 14.09   Installing : elfutils-default-yama-scope-0.176-2.amzn2.noarch           29/32 
#6 14.22   Installing : 1:dbus-1.10.24-7.amzn2.x86_64                              30/32 
#6 14.37   Installing : e2fsprogs-1.42.9-19.amzn2.x86_64                           31/32 
#6 14.56   Installing : xfsprogs-4.5.0-18.amzn2.0.1.x86_64                         32/32 
#6 14.62   Verifying  : cracklib-2.9.0-11.amzn2.0.2.x86_64                          1/32 
#6 14.64   Verifying  : gzip-1.5-10.amzn2.x86_64                                    2/32 
... skipping 212 lines ...
## Validating cluster test-cluster-16025.k8s.local
#
Using cluster from kubectl context: test-cluster-16025.k8s.local

Validating cluster test-cluster-16025.k8s.local

W1006 19:46:41.158033    6055 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-16025-k8-e19v3n-55250149.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-16025-k8-e19v3n-55250149.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1006 19:46:51.191597    6055 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-16025-k8-e19v3n-55250149.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-16025-k8-e19v3n-55250149.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1006 19:47:01.249599    6055 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-16025-k8-e19v3n-55250149.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-16025-k8-e19v3n-55250149.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1006 19:47:11.297410    6055 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-16025-k8-e19v3n-55250149.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-16025-k8-e19v3n-55250149.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1006 19:47:21.329954    6055 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api-test-cluster-16025-k8-e19v3n-55250149.us-west-2.elb.amazonaws.com/api/v1/nodes": dial tcp: lookup api-test-cluster-16025-k8-e19v3n-55250149.us-west-2.elb.amazonaws.com on 10.63.240.10:53: no such host
W1006 19:47:44.043589    6055 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)
W1006 19:48:05.751641    6055 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)
W1006 19:48:27.458220    6055 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)
W1006 19:48:49.175352    6055 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)
W1006 19:49:10.812620    6055 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-02d638923a1ee1652				machine "i-02d638923a1ee1652" has not yet joined cluster
Machine	i-079029e5a79901b10				machine "i-079029e5a79901b10" has not yet joined cluster
Machine	i-0bdd1361f946d7bb8				machine "i-0bdd1361f946d7bb8" has not yet joined cluster
Node	ip-172-20-42-162.us-west-2.compute.internal	node "ip-172-20-42-162.us-west-2.compute.internal" of role "master" is not ready

Validation Failed
W1006 19:49:23.742215    6055 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-0bdd1361f946d7bb8				machine "i-0bdd1361f946d7bb8" has not yet joined cluster
Node	ip-172-20-42-162.us-west-2.compute.internal	node "ip-172-20-42-162.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-8f5559c9b-tgmhw		system-cluster-critical pod "coredns-8f5559c9b-tgmhw" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-7x79p	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-7x79p" is pending
Pod	kube-system/dns-controller-5d59c585d8-hcxq9	system-cluster-critical pod "dns-controller-5d59c585d8-hcxq9" is pending

Validation Failed
W1006 19:49:35.929847    6055 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-42-162.us-west-2.compute.internal					master "ip-172-20-42-162.us-west-2.compute.internal" is missing kube-controller-manager pod
Node	ip-172-20-42-162.us-west-2.compute.internal					master "ip-172-20-42-162.us-west-2.compute.internal" is missing kube-scheduler pod
Pod	kube-system/coredns-8f5559c9b-tgmhw						system-cluster-critical pod "coredns-8f5559c9b-tgmhw" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-7x79p					system-cluster-critical pod "coredns-autoscaler-6f594f4c58-7x79p" is pending
Pod	kube-system/etcd-manager-events-ip-172-20-42-162.us-west-2.compute.internal	system-cluster-critical pod "etcd-manager-events-ip-172-20-42-162.us-west-2.compute.internal" is pending

Validation Failed
W1006 19:49:48.249222    6055 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-42-162.us-west-2.compute.internal				master "ip-172-20-42-162.us-west-2.compute.internal" is missing kube-apiserver pod
Node	ip-172-20-42-162.us-west-2.compute.internal				master "ip-172-20-42-162.us-west-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-8f5559c9b-tgmhw					system-cluster-critical pod "coredns-8f5559c9b-tgmhw" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-7x79p				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-7x79p" is pending
Pod	kube-system/kube-apiserver-ip-172-20-42-162.us-west-2.compute.internal	system-cluster-critical pod "kube-apiserver-ip-172-20-42-162.us-west-2.compute.internal" is pending

Validation Failed
W1006 19:50:00.650088    6055 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-0bdd1361f946d7bb8				machine "i-0bdd1361f946d7bb8" has not yet joined cluster
Node	ip-172-20-35-205.us-west-2.compute.internal	node "ip-172-20-35-205.us-west-2.compute.internal" of role "node" is not ready
Node	ip-172-20-42-162.us-west-2.compute.internal	master "ip-172-20-42-162.us-west-2.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-8f5559c9b-tgmhw		system-cluster-critical pod "coredns-8f5559c9b-tgmhw" is pending
Pod	kube-system/coredns-autoscaler-6f594f4c58-7x79p	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-7x79p" is pending

Validation Failed
W1006 19:50:12.985524    6055 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 9 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-8f5559c9b-n92xf		system-cluster-critical pod "coredns-8f5559c9b-n92xf" is pending
Pod	kube-system/coredns-8f5559c9b-tgmhw		system-cluster-critical pod "coredns-8f5559c9b-tgmhw" is not ready (coredns)
Pod	kube-system/coredns-autoscaler-6f594f4c58-7x79p	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-7x79p" is pending

Validation Failed
W1006 19:50:25.408574    6055 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
Oct  6 19:52:12.229: INFO: Waiting up to 15m0s for pod "ebs-volume-tester-ftxk9" in namespace "ebs-6800" to be "Succeeded or Failed"
Oct  6 19:52:12.293: INFO: Pod "ebs-volume-tester-ftxk9": Phase="Pending", Reason="", readiness=false. Elapsed: 64.283026ms
Oct  6 19:52:14.359: INFO: Pod "ebs-volume-tester-ftxk9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.129630748s
Oct  6 19:52:16.425: INFO: Pod "ebs-volume-tester-ftxk9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.195528575s
Oct  6 19:52:18.491: INFO: Pod "ebs-volume-tester-ftxk9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.261653054s
Oct  6 19:52:20.557: INFO: Pod "ebs-volume-tester-ftxk9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.327544292s
Oct  6 19:52:22.621: INFO: Pod "ebs-volume-tester-ftxk9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.392086022s
Oct  6 19:52:24.688: INFO: Pod "ebs-volume-tester-ftxk9": Phase="Pending", Reason="", readiness=false. Elapsed: 12.458974641s
Oct  6 19:52:26.754: INFO: Pod "ebs-volume-tester-ftxk9": Phase="Pending", Reason="", readiness=false. Elapsed: 14.524750778s
Oct  6 19:52:28.821: INFO: Pod "ebs-volume-tester-ftxk9": Phase="Pending", Reason="", readiness=false. Elapsed: 16.59154677s
Oct  6 19:52:30.887: INFO: Pod "ebs-volume-tester-ftxk9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.65751499s
STEP: Saw pod success
Oct  6 19:52:30.887: INFO: Pod "ebs-volume-tester-ftxk9" satisfied condition "Succeeded or Failed"
STEP: validating provisioned PVs
STEP: waiting for PVC to be in phase "Bound"
Oct  6 19:52:30.887: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-7qrww] to have phase Bound
Oct  6 19:52:30.951: INFO: PersistentVolumeClaim pvc-7qrww found and phase=Bound (64.354097ms)
STEP: checking the PVC
STEP: validating provisioned PV
... skipping 41 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  6 19:52:12.248: INFO: Waiting up to 15m0s for pod "ebs-volume-tester-qwl5m" in namespace "ebs-4260" to be "Succeeded or Failed"
Oct  6 19:52:12.316: INFO: Pod "ebs-volume-tester-qwl5m": Phase="Pending", Reason="", readiness=false. Elapsed: 67.943285ms
Oct  6 19:52:14.384: INFO: Pod "ebs-volume-tester-qwl5m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.136255688s
Oct  6 19:52:16.453: INFO: Pod "ebs-volume-tester-qwl5m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.205520217s
Oct  6 19:52:18.522: INFO: Pod "ebs-volume-tester-qwl5m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.274541508s
Oct  6 19:52:20.592: INFO: Pod "ebs-volume-tester-qwl5m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.344332803s
Oct  6 19:52:22.661: INFO: Pod "ebs-volume-tester-qwl5m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.41342104s
Oct  6 19:52:24.730: INFO: Pod "ebs-volume-tester-qwl5m": Phase="Pending", Reason="", readiness=false. Elapsed: 12.482536697s
Oct  6 19:52:26.799: INFO: Pod "ebs-volume-tester-qwl5m": Phase="Pending", Reason="", readiness=false. Elapsed: 14.551121667s
Oct  6 19:52:28.868: INFO: Pod "ebs-volume-tester-qwl5m": Phase="Pending", Reason="", readiness=false. Elapsed: 16.619706285s
Oct  6 19:52:30.936: INFO: Pod "ebs-volume-tester-qwl5m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.688435257s
STEP: Saw pod success
Oct  6 19:52:30.936: INFO: Pod "ebs-volume-tester-qwl5m" satisfied condition "Succeeded or Failed"
STEP: validating provisioned PVs
STEP: waiting for PVC to be in phase "Bound"
Oct  6 19:52:30.936: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-ztf9l] to have phase Bound
Oct  6 19:52:31.006: INFO: PersistentVolumeClaim pvc-ztf9l found and phase=Bound (69.435291ms)
STEP: checking the PVC
STEP: validating provisioned PV
... skipping 24 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 35.543 seconds
SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 31 Skipped


Ginkgo ran 1 suite in 1m33.750823855s
Test Suite Passed
+ TEST_PASSED=0
+ set -e
... skipping 547 lines ...
	volume:vol-0e0853a5dbccfde96
	security-group:sg-02c8ac0a240bab5f8
	volume:vol-005c1ace748082392
	volume:vol-07614437807a08eb3
	route-table:rtb-03fa1496772d21db1
	dhcp-options:dopt-056b4ab9bbaef4063
{"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-06T19:55:06Z"}