This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-05-26 06:41
Elapsed33m36s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 666 lines ...
timeout --foreground 300 bash -c "while ! kubectl get secrets | grep capz-cqqr74-kubeconfig; do sleep 1; done"
capz-cqqr74-kubeconfig                 cluster.x-k8s.io/secret               1      0s
# Get kubeconfig and store it locally.
kubectl get secrets capz-cqqr74-kubeconfig -o json | jq -r .data.value | base64 --decode > ./kubeconfig
timeout --foreground 600 bash -c "while ! kubectl --kubeconfig=./kubeconfig get nodes | grep master; do sleep 1; done"
Unable to connect to the server: dial tcp 65.52.245.146:6443: i/o timeout
error: the server doesn't have a resource type "nodes"
No resources found
capz-cqqr74-control-plane-hh9kg   NotReady   control-plane,master   2s    v1.22.0-alpha.2.169+aa0017ad138ac8
run "kubectl --kubeconfig=./kubeconfig ..." to work with the new target cluster
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
Waiting for 1 control plane machine(s) and 2 worker machine(s) to become Ready
node/capz-cqqr74-control-plane-hh9kg condition met
... skipping 210 lines ...
May 26 07:01:10.418: INFO: Condition Ready of node capz-cqqr74-mp-0000000 is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable  NoSchedule 2021-05-26 06:57:17 +0000 UTC} {node.kubernetes.io/unreachable  NoExecute 2021-05-26 06:57:22 +0000 UTC}]. Failure
May 26 07:01:10.418: INFO: Condition Ready of node capz-cqqr74-mp-0000002 is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable  NoSchedule 2021-05-26 06:57:12 +0000 UTC} {node.kubernetes.io/unreachable  NoExecute 2021-05-26 06:57:17 +0000 UTC}]. Failure
May 26 07:01:12.420: INFO: Condition Ready of node capz-cqqr74-mp-0000000 is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable  NoSchedule 2021-05-26 06:57:17 +0000 UTC} {node.kubernetes.io/unreachable  NoExecute 2021-05-26 06:57:22 +0000 UTC}]. Failure
May 26 07:01:12.420: INFO: Condition Ready of node capz-cqqr74-mp-0000002 is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable  NoSchedule 2021-05-26 06:57:12 +0000 UTC} {node.kubernetes.io/unreachable  NoExecute 2021-05-26 06:57:17 +0000 UTC}]. Failure
May 26 07:01:12.448: INFO: Condition Ready of node capz-cqqr74-mp-0000000 is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable  NoSchedule 2021-05-26 06:57:17 +0000 UTC} {node.kubernetes.io/unreachable  NoExecute 2021-05-26 06:57:22 +0000 UTC}]. Failure
May 26 07:01:12.448: INFO: Condition Ready of node capz-cqqr74-mp-0000002 is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable  NoSchedule 2021-05-26 06:57:12 +0000 UTC} {node.kubernetes.io/unreachable  NoExecute 2021-05-26 06:57:17 +0000 UTC}]. Failure
May 26 07:01:12.449: FAIL: All nodes should be ready after test, Not ready nodes: ", capz-cqqr74-mp-0000000, capz-cqqr74-mp-0000002"

Full Stack Trace
sigs.k8s.io/azuredisk-csi-driver/test/e2e.TestE2E(0xc00036a180)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:218 +0x1b6
testing.tRunner(0xc00036a180, 0x2183000)
	/usr/local/go/src/testing/testing.go:1193 +0xef
... skipping 203 lines ...
May 26 07:04:10.707: INFO: Condition Ready of node capz-cqqr74-mp-0000000 is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable  NoSchedule 2021-05-26 06:57:17 +0000 UTC} {node.kubernetes.io/unreachable  NoExecute 2021-05-26 06:57:22 +0000 UTC}]. Failure
May 26 07:04:10.707: INFO: Condition Ready of node capz-cqqr74-mp-0000002 is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable  NoSchedule 2021-05-26 06:57:12 +0000 UTC} {node.kubernetes.io/unreachable  NoExecute 2021-05-26 06:57:17 +0000 UTC}]. Failure
May 26 07:04:12.707: INFO: Condition Ready of node capz-cqqr74-mp-0000000 is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable  NoSchedule 2021-05-26 06:57:17 +0000 UTC} {node.kubernetes.io/unreachable  NoExecute 2021-05-26 06:57:22 +0000 UTC}]. Failure
May 26 07:04:12.707: INFO: Condition Ready of node capz-cqqr74-mp-0000002 is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable  NoSchedule 2021-05-26 06:57:12 +0000 UTC} {node.kubernetes.io/unreachable  NoExecute 2021-05-26 06:57:17 +0000 UTC}]. Failure
May 26 07:04:12.736: INFO: Condition Ready of node capz-cqqr74-mp-0000000 is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable  NoSchedule 2021-05-26 06:57:17 +0000 UTC} {node.kubernetes.io/unreachable  NoExecute 2021-05-26 06:57:22 +0000 UTC}]. Failure
May 26 07:04:12.736: INFO: Condition Ready of node capz-cqqr74-mp-0000002 is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable  NoSchedule 2021-05-26 06:57:12 +0000 UTC} {node.kubernetes.io/unreachable  NoExecute 2021-05-26 06:57:17 +0000 UTC}]. Failure
May 26 07:04:12.736: FAIL: All nodes should be ready after test, Not ready nodes: ", capz-cqqr74-mp-0000000, capz-cqqr74-mp-0000002"

Full Stack Trace
sigs.k8s.io/azuredisk-csi-driver/test/e2e.TestE2E(0xc00036a180)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:218 +0x1b6
testing.tRunner(0xc00036a180, 0x2183000)
	/usr/local/go/src/testing/testing.go:1193 +0xef
... skipping 154 lines ...

    test case is only available for CSI drivers

    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:253
------------------------------
Pre-Provisioned [single-az] 
  should fail when maxShares is invalid [disk.csi.azure.com][windows]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:158
STEP: Creating a kubernetes client
May 26 07:06:15.037: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
STEP: Building a namespace api object, basename azuredisk
STEP: Waiting for a default service account to be provisioned in namespace
I0526 07:06:15.180989   34220 azuredisk_driver.go:57] Using azure disk driver: kubernetes.io/azure-disk
... skipping 2 lines ...

S [SKIPPING] [0.205 seconds]
Pre-Provisioned
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:37
  [single-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:67
    should fail when maxShares is invalid [disk.csi.azure.com][windows] [It]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:158

    test case is only available for CSI drivers

    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:253
------------------------------
... skipping 81 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
May 26 07:06:16.969: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-lggzh" in namespace "azuredisk-5356" to be "Succeeded or Failed"
May 26 07:06:16.997: INFO: Pod "azuredisk-volume-tester-lggzh": Phase="Pending", Reason="", readiness=false. Elapsed: 28.463607ms
May 26 07:06:19.028: INFO: Pod "azuredisk-volume-tester-lggzh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059184006s
May 26 07:06:21.173: INFO: Pod "azuredisk-volume-tester-lggzh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.204762443s
May 26 07:06:23.202: INFO: Pod "azuredisk-volume-tester-lggzh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.233377079s
May 26 07:06:25.234: INFO: Pod "azuredisk-volume-tester-lggzh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.265493296s
May 26 07:06:27.268: INFO: Pod "azuredisk-volume-tester-lggzh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.299487944s
... skipping 11 lines ...
May 26 07:06:51.604: INFO: Pod "azuredisk-volume-tester-lggzh": Phase="Pending", Reason="", readiness=false. Elapsed: 34.634958717s
May 26 07:06:53.631: INFO: Pod "azuredisk-volume-tester-lggzh": Phase="Pending", Reason="", readiness=false. Elapsed: 36.662635682s
May 26 07:06:55.665: INFO: Pod "azuredisk-volume-tester-lggzh": Phase="Pending", Reason="", readiness=false. Elapsed: 38.696024084s
May 26 07:06:57.693: INFO: Pod "azuredisk-volume-tester-lggzh": Phase="Pending", Reason="", readiness=false. Elapsed: 40.724215089s
May 26 07:06:59.721: INFO: Pod "azuredisk-volume-tester-lggzh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.752441576s
STEP: Saw pod success
May 26 07:06:59.721: INFO: Pod "azuredisk-volume-tester-lggzh" satisfied condition "Succeeded or Failed"
May 26 07:06:59.721: INFO: deleting Pod "azuredisk-5356"/"azuredisk-volume-tester-lggzh"
May 26 07:06:59.770: INFO: Pod azuredisk-volume-tester-lggzh has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-lggzh in namespace azuredisk-5356
STEP: validating provisioned PV
STEP: checking the PV
May 26 07:06:59.861: INFO: deleting PVC "azuredisk-5356"/"pvc-tfwvf"
May 26 07:06:59.861: INFO: Deleting PersistentVolumeClaim "pvc-tfwvf"
STEP: waiting for claim's PV "pvc-bbaee327-de26-4fb4-874c-d41f0285ee0d" to be deleted
May 26 07:06:59.910: INFO: Waiting up to 10m0s for PersistentVolume pvc-bbaee327-de26-4fb4-874c-d41f0285ee0d to get deleted
May 26 07:06:59.938: INFO: PersistentVolume pvc-bbaee327-de26-4fb4-874c-d41f0285ee0d found and phase=Released (27.692763ms)
May 26 07:07:04.967: INFO: PersistentVolume pvc-bbaee327-de26-4fb4-874c-d41f0285ee0d found and phase=Failed (5.05724169s)
May 26 07:07:09.994: INFO: PersistentVolume pvc-bbaee327-de26-4fb4-874c-d41f0285ee0d found and phase=Failed (10.084262458s)
May 26 07:07:15.021: INFO: PersistentVolume pvc-bbaee327-de26-4fb4-874c-d41f0285ee0d found and phase=Failed (15.110974323s)
May 26 07:07:20.050: INFO: PersistentVolume pvc-bbaee327-de26-4fb4-874c-d41f0285ee0d found and phase=Failed (20.139631848s)
May 26 07:07:25.079: INFO: PersistentVolume pvc-bbaee327-de26-4fb4-874c-d41f0285ee0d found and phase=Failed (25.169281604s)
May 26 07:07:30.109: INFO: PersistentVolume pvc-bbaee327-de26-4fb4-874c-d41f0285ee0d found and phase=Failed (30.198998673s)
May 26 07:07:35.137: INFO: PersistentVolume pvc-bbaee327-de26-4fb4-874c-d41f0285ee0d found and phase=Failed (35.22665574s)
May 26 07:07:40.166: INFO: PersistentVolume pvc-bbaee327-de26-4fb4-874c-d41f0285ee0d found and phase=Failed (40.255908451s)
May 26 07:07:45.196: INFO: PersistentVolume pvc-bbaee327-de26-4fb4-874c-d41f0285ee0d found and phase=Failed (45.286042382s)
May 26 07:07:50.225: INFO: PersistentVolume pvc-bbaee327-de26-4fb4-874c-d41f0285ee0d was removed
May 26 07:07:50.225: INFO: Waiting up to 5m0s for PersistentVolumeClaim azuredisk-5356 to be removed
May 26 07:07:50.251: INFO: Claim "azuredisk-5356" in namespace "pvc-tfwvf" doesn't exist in the system
May 26 07:07:50.251: INFO: deleting StorageClass azuredisk-5356-kubernetes.io-azure-disk-dynamic-sc-6dfp5
May 26 07:07:50.279: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "azuredisk-5356" for this suite.
... skipping 23 lines ...
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod has 'FailedMount' event
May 26 07:08:13.334: INFO: deleting Pod "azuredisk-6413"/"azuredisk-volume-tester-n6nnn"
May 26 07:08:13.362: INFO: Error getting logs for pod azuredisk-volume-tester-n6nnn: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-n6nnn)
STEP: Deleting pod azuredisk-volume-tester-n6nnn in namespace azuredisk-6413
STEP: validating provisioned PV
STEP: checking the PV
May 26 07:08:13.444: INFO: deleting PVC "azuredisk-6413"/"pvc-kfjhb"
May 26 07:08:13.444: INFO: Deleting PersistentVolumeClaim "pvc-kfjhb"
STEP: waiting for claim's PV "pvc-5ddd27b4-855a-41bd-a49b-085c2a4278f8" to be deleted
May 26 07:08:13.473: INFO: Waiting up to 10m0s for PersistentVolume pvc-5ddd27b4-855a-41bd-a49b-085c2a4278f8 to get deleted
May 26 07:08:13.499: INFO: PersistentVolume pvc-5ddd27b4-855a-41bd-a49b-085c2a4278f8 found and phase=Bound (26.298727ms)
May 26 07:08:18.531: INFO: PersistentVolume pvc-5ddd27b4-855a-41bd-a49b-085c2a4278f8 found and phase=Bound (5.058386974s)
May 26 07:08:23.559: INFO: PersistentVolume pvc-5ddd27b4-855a-41bd-a49b-085c2a4278f8 found and phase=Failed (10.086942537s)
May 26 07:08:28.588: INFO: PersistentVolume pvc-5ddd27b4-855a-41bd-a49b-085c2a4278f8 found and phase=Failed (15.11572856s)
May 26 07:08:33.617: INFO: PersistentVolume pvc-5ddd27b4-855a-41bd-a49b-085c2a4278f8 found and phase=Failed (20.144566889s)
May 26 07:08:38.646: INFO: PersistentVolume pvc-5ddd27b4-855a-41bd-a49b-085c2a4278f8 found and phase=Failed (25.173733842s)
May 26 07:08:43.678: INFO: PersistentVolume pvc-5ddd27b4-855a-41bd-a49b-085c2a4278f8 found and phase=Failed (30.205022233s)
May 26 07:08:48.706: INFO: PersistentVolume pvc-5ddd27b4-855a-41bd-a49b-085c2a4278f8 found and phase=Failed (35.233402286s)
May 26 07:08:53.734: INFO: PersistentVolume pvc-5ddd27b4-855a-41bd-a49b-085c2a4278f8 found and phase=Failed (40.261910027s)
May 26 07:08:58.763: INFO: PersistentVolume pvc-5ddd27b4-855a-41bd-a49b-085c2a4278f8 found and phase=Failed (45.290373811s)
May 26 07:09:03.790: INFO: PersistentVolume pvc-5ddd27b4-855a-41bd-a49b-085c2a4278f8 was removed
May 26 07:09:03.790: INFO: Waiting up to 5m0s for PersistentVolumeClaim azuredisk-6413 to be removed
May 26 07:09:03.817: INFO: Claim "azuredisk-6413" in namespace "pvc-kfjhb" doesn't exist in the system
May 26 07:09:03.817: INFO: deleting StorageClass azuredisk-6413-kubernetes.io-azure-disk-dynamic-sc-j26dv
May 26 07:09:03.847: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "azuredisk-6413" for this suite.
... skipping 21 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
May 26 07:09:04.859: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-zw89h" in namespace "azuredisk-4147" to be "Succeeded or Failed"
May 26 07:09:04.885: INFO: Pod "azuredisk-volume-tester-zw89h": Phase="Pending", Reason="", readiness=false. Elapsed: 25.689614ms
May 26 07:09:06.912: INFO: Pod "azuredisk-volume-tester-zw89h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.053515082s
May 26 07:09:08.946: INFO: Pod "azuredisk-volume-tester-zw89h": Phase="Pending", Reason="", readiness=false. Elapsed: 4.086698354s
May 26 07:09:10.975: INFO: Pod "azuredisk-volume-tester-zw89h": Phase="Pending", Reason="", readiness=false. Elapsed: 6.115963212s
May 26 07:09:13.003: INFO: Pod "azuredisk-volume-tester-zw89h": Phase="Pending", Reason="", readiness=false. Elapsed: 8.144542989s
May 26 07:09:15.031: INFO: Pod "azuredisk-volume-tester-zw89h": Phase="Pending", Reason="", readiness=false. Elapsed: 10.171763487s
... skipping 2 lines ...
May 26 07:09:21.115: INFO: Pod "azuredisk-volume-tester-zw89h": Phase="Pending", Reason="", readiness=false. Elapsed: 16.256236626s
May 26 07:09:23.145: INFO: Pod "azuredisk-volume-tester-zw89h": Phase="Pending", Reason="", readiness=false. Elapsed: 18.286438529s
May 26 07:09:25.175: INFO: Pod "azuredisk-volume-tester-zw89h": Phase="Pending", Reason="", readiness=false. Elapsed: 20.315927753s
May 26 07:09:27.205: INFO: Pod "azuredisk-volume-tester-zw89h": Phase="Pending", Reason="", readiness=false. Elapsed: 22.345729809s
May 26 07:09:29.232: INFO: Pod "azuredisk-volume-tester-zw89h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.373385074s
STEP: Saw pod success
May 26 07:09:29.232: INFO: Pod "azuredisk-volume-tester-zw89h" satisfied condition "Succeeded or Failed"
May 26 07:09:29.232: INFO: deleting Pod "azuredisk-4147"/"azuredisk-volume-tester-zw89h"
May 26 07:09:29.279: INFO: Pod azuredisk-volume-tester-zw89h has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-zw89h in namespace azuredisk-4147
STEP: validating provisioned PV
STEP: checking the PV
May 26 07:09:29.378: INFO: deleting PVC "azuredisk-4147"/"pvc-mfm8z"
May 26 07:09:29.378: INFO: Deleting PersistentVolumeClaim "pvc-mfm8z"
STEP: waiting for claim's PV "pvc-8ee6de86-2929-4206-9c8e-43048bfc12ee" to be deleted
May 26 07:09:29.406: INFO: Waiting up to 10m0s for PersistentVolume pvc-8ee6de86-2929-4206-9c8e-43048bfc12ee to get deleted
May 26 07:09:29.433: INFO: PersistentVolume pvc-8ee6de86-2929-4206-9c8e-43048bfc12ee found and phase=Released (26.813452ms)
May 26 07:09:34.461: INFO: PersistentVolume pvc-8ee6de86-2929-4206-9c8e-43048bfc12ee found and phase=Failed (5.055232705s)
May 26 07:09:39.491: INFO: PersistentVolume pvc-8ee6de86-2929-4206-9c8e-43048bfc12ee found and phase=Failed (10.084663255s)
May 26 07:09:44.518: INFO: PersistentVolume pvc-8ee6de86-2929-4206-9c8e-43048bfc12ee found and phase=Failed (15.112365539s)
May 26 07:09:49.546: INFO: PersistentVolume pvc-8ee6de86-2929-4206-9c8e-43048bfc12ee found and phase=Failed (20.140451386s)
May 26 07:09:54.574: INFO: PersistentVolume pvc-8ee6de86-2929-4206-9c8e-43048bfc12ee found and phase=Failed (25.1681919s)
May 26 07:09:59.603: INFO: PersistentVolume pvc-8ee6de86-2929-4206-9c8e-43048bfc12ee found and phase=Failed (30.197350531s)
May 26 07:10:04.631: INFO: PersistentVolume pvc-8ee6de86-2929-4206-9c8e-43048bfc12ee was removed
May 26 07:10:04.631: INFO: Waiting up to 5m0s for PersistentVolumeClaim azuredisk-4147 to be removed
May 26 07:10:04.658: INFO: Claim "azuredisk-4147" in namespace "pvc-mfm8z" doesn't exist in the system
May 26 07:10:04.658: INFO: deleting StorageClass azuredisk-4147-kubernetes.io-azure-disk-dynamic-sc-cpjnn
May 26 07:10:04.687: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "azuredisk-4147" for this suite.
... skipping 21 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with an error
May 26 07:10:05.693: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-lxmpj" in namespace "azuredisk-1957" to be "Error status code"
May 26 07:10:05.719: INFO: Pod "azuredisk-volume-tester-lxmpj": Phase="Pending", Reason="", readiness=false. Elapsed: 26.692209ms
May 26 07:10:07.747: INFO: Pod "azuredisk-volume-tester-lxmpj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.053839017s
May 26 07:10:09.776: INFO: Pod "azuredisk-volume-tester-lxmpj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.082841278s
May 26 07:10:11.804: INFO: Pod "azuredisk-volume-tester-lxmpj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.111510935s
May 26 07:10:13.834: INFO: Pod "azuredisk-volume-tester-lxmpj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.141666237s
May 26 07:10:15.862: INFO: Pod "azuredisk-volume-tester-lxmpj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.16932134s
May 26 07:10:17.889: INFO: Pod "azuredisk-volume-tester-lxmpj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.196584206s
May 26 07:10:19.925: INFO: Pod "azuredisk-volume-tester-lxmpj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.232217874s
May 26 07:10:21.955: INFO: Pod "azuredisk-volume-tester-lxmpj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.262160507s
May 26 07:10:23.983: INFO: Pod "azuredisk-volume-tester-lxmpj": Phase="Pending", Reason="", readiness=false. Elapsed: 18.290630297s
May 26 07:10:26.011: INFO: Pod "azuredisk-volume-tester-lxmpj": Phase="Pending", Reason="", readiness=false. Elapsed: 20.318604494s
May 26 07:10:28.038: INFO: Pod "azuredisk-volume-tester-lxmpj": Phase="Pending", Reason="", readiness=false. Elapsed: 22.345299773s
May 26 07:10:30.065: INFO: Pod "azuredisk-volume-tester-lxmpj": Phase="Failed", Reason="", readiness=false. Elapsed: 24.372626813s
STEP: Saw pod failure
May 26 07:10:30.065: INFO: Pod "azuredisk-volume-tester-lxmpj" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
May 26 07:10:30.096: INFO: deleting Pod "azuredisk-1957"/"azuredisk-volume-tester-lxmpj"
May 26 07:10:30.125: INFO: Pod azuredisk-volume-tester-lxmpj has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-lxmpj in namespace azuredisk-1957
STEP: validating provisioned PV
STEP: checking the PV
May 26 07:10:30.225: INFO: deleting PVC "azuredisk-1957"/"pvc-mbpfb"
May 26 07:10:30.225: INFO: Deleting PersistentVolumeClaim "pvc-mbpfb"
STEP: waiting for claim's PV "pvc-2126de40-360d-4cdf-b397-6238394b10b6" to be deleted
May 26 07:10:30.253: INFO: Waiting up to 10m0s for PersistentVolume pvc-2126de40-360d-4cdf-b397-6238394b10b6 to get deleted
May 26 07:10:30.279: INFO: PersistentVolume pvc-2126de40-360d-4cdf-b397-6238394b10b6 found and phase=Released (26.554776ms)
May 26 07:10:35.315: INFO: PersistentVolume pvc-2126de40-360d-4cdf-b397-6238394b10b6 found and phase=Failed (5.062086903s)
May 26 07:10:40.344: INFO: PersistentVolume pvc-2126de40-360d-4cdf-b397-6238394b10b6 found and phase=Failed (10.091512695s)
May 26 07:10:45.378: INFO: PersistentVolume pvc-2126de40-360d-4cdf-b397-6238394b10b6 found and phase=Failed (15.125651711s)
May 26 07:10:50.407: INFO: PersistentVolume pvc-2126de40-360d-4cdf-b397-6238394b10b6 found and phase=Failed (20.154173587s)
May 26 07:10:55.443: INFO: PersistentVolume pvc-2126de40-360d-4cdf-b397-6238394b10b6 found and phase=Failed (25.190044453s)
May 26 07:11:00.471: INFO: PersistentVolume pvc-2126de40-360d-4cdf-b397-6238394b10b6 found and phase=Failed (30.217785794s)
May 26 07:11:05.499: INFO: PersistentVolume pvc-2126de40-360d-4cdf-b397-6238394b10b6 was removed
May 26 07:11:05.499: INFO: Waiting up to 5m0s for PersistentVolumeClaim azuredisk-1957 to be removed
May 26 07:11:05.526: INFO: Claim "azuredisk-1957" in namespace "pvc-mbpfb" doesn't exist in the system
May 26 07:11:05.526: INFO: deleting StorageClass azuredisk-1957-kubernetes.io-azure-disk-dynamic-sc-fnfj5
May 26 07:11:05.556: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "azuredisk-1957" for this suite.
... skipping 53 lines ...
May 26 07:12:43.269: INFO: PersistentVolume pvc-7005557d-7887-4778-8a16-54f7b0df7038 found and phase=Bound (10.083084777s)
May 26 07:12:48.298: INFO: PersistentVolume pvc-7005557d-7887-4778-8a16-54f7b0df7038 found and phase=Bound (15.112091626s)
May 26 07:12:53.325: INFO: PersistentVolume pvc-7005557d-7887-4778-8a16-54f7b0df7038 found and phase=Bound (20.138957395s)
May 26 07:12:58.353: INFO: PersistentVolume pvc-7005557d-7887-4778-8a16-54f7b0df7038 found and phase=Bound (25.167054838s)
May 26 07:13:03.380: INFO: PersistentVolume pvc-7005557d-7887-4778-8a16-54f7b0df7038 found and phase=Bound (30.194143848s)
May 26 07:13:08.407: INFO: PersistentVolume pvc-7005557d-7887-4778-8a16-54f7b0df7038 found and phase=Bound (35.220960622s)
May 26 07:13:13.434: INFO: PersistentVolume pvc-7005557d-7887-4778-8a16-54f7b0df7038 found and phase=Failed (40.248045836s)
May 26 07:13:18.462: INFO: PersistentVolume pvc-7005557d-7887-4778-8a16-54f7b0df7038 found and phase=Failed (45.275278612s)
May 26 07:13:23.489: INFO: PersistentVolume pvc-7005557d-7887-4778-8a16-54f7b0df7038 found and phase=Failed (50.302468672s)
May 26 07:13:28.532: INFO: PersistentVolume pvc-7005557d-7887-4778-8a16-54f7b0df7038 found and phase=Failed (55.345888889s)
May 26 07:13:33.560: INFO: PersistentVolume pvc-7005557d-7887-4778-8a16-54f7b0df7038 was removed
May 26 07:13:33.560: INFO: Waiting up to 5m0s for PersistentVolumeClaim azuredisk-8705 to be removed
May 26 07:13:33.586: INFO: Claim "azuredisk-8705" in namespace "pvc-7lpcj" doesn't exist in the system
May 26 07:13:33.586: INFO: deleting StorageClass azuredisk-8705-kubernetes.io-azure-disk-dynamic-sc-fr8qw
May 26 07:13:33.615: INFO: deleting Pod "azuredisk-8705"/"azuredisk-volume-tester-2r8zk"
May 26 07:13:33.653: INFO: Pod azuredisk-volume-tester-2r8zk has the following logs: 
... skipping 10 lines ...
May 26 07:13:48.874: INFO: PersistentVolume pvc-889d044b-8a59-400e-a4bc-435081b91e7e found and phase=Bound (15.10886797s)
May 26 07:13:53.903: INFO: PersistentVolume pvc-889d044b-8a59-400e-a4bc-435081b91e7e found and phase=Bound (20.137926476s)
May 26 07:13:58.932: INFO: PersistentVolume pvc-889d044b-8a59-400e-a4bc-435081b91e7e found and phase=Bound (25.167164739s)
May 26 07:14:03.960: INFO: PersistentVolume pvc-889d044b-8a59-400e-a4bc-435081b91e7e found and phase=Bound (30.195102082s)
May 26 07:14:08.989: INFO: PersistentVolume pvc-889d044b-8a59-400e-a4bc-435081b91e7e found and phase=Bound (35.223957132s)
May 26 07:14:14.017: INFO: PersistentVolume pvc-889d044b-8a59-400e-a4bc-435081b91e7e found and phase=Bound (40.251815057s)
May 26 07:14:19.049: INFO: PersistentVolume pvc-889d044b-8a59-400e-a4bc-435081b91e7e found and phase=Failed (45.283768553s)
May 26 07:14:24.080: INFO: PersistentVolume pvc-889d044b-8a59-400e-a4bc-435081b91e7e found and phase=Failed (50.314869193s)
May 26 07:14:29.108: INFO: PersistentVolume pvc-889d044b-8a59-400e-a4bc-435081b91e7e found and phase=Failed (55.343125865s)
May 26 07:14:34.137: INFO: PersistentVolume pvc-889d044b-8a59-400e-a4bc-435081b91e7e was removed
May 26 07:14:34.137: INFO: Waiting up to 5m0s for PersistentVolumeClaim azuredisk-8705 to be removed
May 26 07:14:34.164: INFO: Claim "azuredisk-8705" in namespace "pvc-dx8cs" doesn't exist in the system
May 26 07:14:34.164: INFO: deleting StorageClass azuredisk-8705-kubernetes.io-azure-disk-dynamic-sc-fzltn
May 26 07:14:34.193: INFO: deleting Pod "azuredisk-8705"/"azuredisk-volume-tester-48n8x"
May 26 07:14:34.231: INFO: Pod azuredisk-volume-tester-48n8x has the following logs: 
... skipping 16 lines ...