This job view page is being replaced by Spyglass soon. Check out the new job view.
PRnearora-msft: fix: Update K8s version to fix snapshot e2e test
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-07-26 23:05
Elapsed36m4s
Revisionec69880f5dd844ea39987b3e044521f90fe3d61e
Refs 947

No Test Failures!


Error lines from build-log.txt

... skipping 72 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11248  100 11248    0     0   174k      0 --:--:-- --:--:-- --:--:--  174k
Downloading https://get.helm.sh/helm-v3.6.3-linux-amd64.tar.gz
Verifying checksum... Done.
Preparing to install helm into /usr/local/bin
helm installed into /usr/local/bin/helm
docker pull k8sprow.azurecr.io/azuredisk-csi:v1.6.0-ebd1ba6092966acc91a5ad2057229a66dbea8b4a || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v1.6.0-ebd1ba6092966acc91a5ad2057229a66dbea8b4a not found: manifest unknown: manifest tagged by "v1.6.0-ebd1ba6092966acc91a5ad2057229a66dbea8b4a" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=v1.6.0-ebd1ba6092966acc91a5ad2057229a66dbea8b4a -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=ebd1ba6092966acc91a5ad2057229a66dbea8b4a -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-07-26T23:13:19Z -extldflags "-static""  -mod vendor -o _output/amd64/azurediskplugin.exe ./pkg/azurediskplugin
docker buildx rm container-builder || true
error: no builder "container-builder" found
docker buildx create --use --name=container-builder
container-builder
# enable qemu for arm64 build
# https://github.com/docker/buildx/issues/464#issuecomment-741507760
docker run --privileged --rm tonistiigi/binfmt --uninstall qemu-aarch64
Unable to find image 'tonistiigi/binfmt:latest' locally
... skipping 1548 lines ...
                    type: string
                type: object
              volumeSnapshotClassName:
                description: 'volumeSnapshotClassName is the name of the VolumeSnapshotClass
                  requested by the VolumeSnapshot. If not specified, the default snapshot
                  class will be used if one exists. If not specified, and there is
                  no default snapshot class, dynamic snapshot creation will fail.
                  Empty string is not allowed for this field. TODO(xiangqian): a webhook
                  validation on empty string. More info: https://kubernetes.io/docs/concepts/storage/volume-snapshot-classes'
                type: string
            required:
            - source
            type: object
... skipping 22 lines ...
                  pre-existing snapshot, this field will be filled with the "creation_time"
                  value returned from the CSI "ListSnapshots" gRPC call if the driver
                  supports it. If not specified, it indicates that the creation time
                  of the snapshot is unknown.
                format: date-time
                type: string
              error:
                description: error is the last observed error during snapshot creation,
                  if any. This field could be helpful to upper level controllers(i.e.,
                  application controller) to decide whether they should continue on
                  waiting for the snapshot to be created based on the type of error
                  reported.
                properties:
                  message:
                    description: 'message is a string detailing the encountered error
                      during snapshot creation if specified. NOTE: message may be
                      logged, and it should not contain sensitive information.'
                    type: string
                  time:
                    description: time is the timestamp when the error was encountered.
                    format: date-time
                    type: string
                type: object
              readyToUse:
                description: readyToUse indicates if a snapshot is ready to be used
                  to restore a volume. In dynamic snapshot creation case, this field
... skipping 10 lines ...
                  in bytes. In dynamic snapshot creation case, this field will be
                  filled in with the "size_bytes" value returned from CSI "CreateSnapshotRequest"
                  gRPC call. For a pre-existing snapshot, this field will be filled
                  with the "size_bytes" value returned from the CSI "ListSnapshots"
                  gRPC call if the driver supports it. When restoring a volume from
                  this snapshot, the size of the volume MUST NOT be smaller than the
                  restoreSize if it is specified, otherwise the restoration will fail.
                  If not specified, it indicates that the size is unknown.
                pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$
                x-kubernetes-int-or-string: true
            type: object
        required:
        - spec
... skipping 265 lines ...
                  supports it. If not specified, it indicates the creation time is
                  unknown. The format of this field is a Unix nanoseconds time encoded
                  as an int64. On Unix, the command `date +%s%N` returns the current
                  time in nanoseconds since 1970-01-01 00:00:00 UTC.
                format: int64
                type: integer
              error:
                description: error is the latest observed error during snapshot creation,
                  if any.
                properties:
                  message:
                    description: 'message is a string detailing the encountered error
                      during snapshot creation if specified. NOTE: message may be
                      logged, and it should not contain sensitive information.'
                    type: string
                  time:
                    description: time is the timestamp when the error was encountered.
                    format: date-time
                    type: string
                type: object
              readyToUse:
                description: readyToUse indicates if a snapshot is ready to be used
                  to restore a volume. In dynamic snapshot creation case, this field
... skipping 9 lines ...
                  in bytes. In dynamic snapshot creation case, this field will be
                  filled in with the "size_bytes" value returned from CSI "CreateSnapshotRequest"
                  gRPC call. For a pre-existing snapshot, this field will be filled
                  with the "size_bytes" value returned from the CSI "ListSnapshots"
                  gRPC call if the driver supports it. When restoring a volume from
                  this snapshot, the size of the volume MUST NOT be smaller than the
                  restoreSize if it is specified, otherwise the restoration will fail.
                  If not specified, it indicates that the size is unknown.
                format: int64
                minimum: 0
                type: integer
              snapshotHandle:
                description: snapshotHandle is the CSI "snapshot_id" of a snapshot
                  on the underlying storage system. If not specified, it indicates
                  that dynamic snapshot creation has either failed or it is still
                  in progress.
                type: string
            type: object
        required:
        - spec
        type: object
... skipping 841 lines ...
        - name: csi-resizer
          image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.1.0"
          args:
            - "-csi-address=$(ADDRESS)"
            - "-v=2"
            - "-leader-election"
            - '-handle-volume-inuse-error=true'
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          volumeMounts:
            - name: socket-dir
              mountPath: /csi
... skipping 174 lines ...
Go Version: go1.16.6
Platform: linux/amd64
Topology Key: topology.disk.csi.azure.com/zone

Streaming logs below:
STEP: Building a namespace api object, basename azuredisk
E0726 23:21:54.955587   14120 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
W0726 23:21:54.956783   14120 azuredisk.go:207] DisableAvailabilitySetNodes for controller is set as false while current VMType is vmss
I0726 23:21:54.957416   14120 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I0726 23:21:54.957445   14120 driver.go:81] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0726 23:21:54.957450   14120 driver.go:81] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0726 23:21:54.957456   14120 driver.go:81] Enabling controller service capability: LIST_SNAPSHOTS
I0726 23:21:54.957461   14120 driver.go:81] Enabling controller service capability: CLONE_VOLUME
... skipping 17 lines ...
Jul 26 23:21:58.798: INFO: PersistentVolumeClaim pvc-bxpl8 found but phase is Pending instead of Bound.
Jul 26 23:22:00.814: INFO: PersistentVolumeClaim pvc-bxpl8 found and phase=Bound (2.029651133s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pod's command exits with an error
Jul 26 23:22:00.860: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-ljmwv" in namespace "azuredisk-8081" to be "Error status code"
Jul 26 23:22:00.874: INFO: Pod "azuredisk-volume-tester-ljmwv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.038157ms
Jul 26 23:22:02.889: INFO: Pod "azuredisk-volume-tester-ljmwv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.029693464s
Jul 26 23:22:04.905: INFO: Pod "azuredisk-volume-tester-ljmwv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.044929103s
Jul 26 23:22:06.920: INFO: Pod "azuredisk-volume-tester-ljmwv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.060329461s
Jul 26 23:22:08.936: INFO: Pod "azuredisk-volume-tester-ljmwv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.076380396s
Jul 26 23:22:10.952: INFO: Pod "azuredisk-volume-tester-ljmwv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.092022833s
Jul 26 23:22:12.967: INFO: Pod "azuredisk-volume-tester-ljmwv": Phase="Pending", Reason="", readiness=false. Elapsed: 12.107631678s
Jul 26 23:22:14.984: INFO: Pod "azuredisk-volume-tester-ljmwv": Phase="Pending", Reason="", readiness=false. Elapsed: 14.123992187s
Jul 26 23:22:16.999: INFO: Pod "azuredisk-volume-tester-ljmwv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.139449958s
Jul 26 23:22:19.014: INFO: Pod "azuredisk-volume-tester-ljmwv": Phase="Pending", Reason="", readiness=false. Elapsed: 18.154661355s
Jul 26 23:22:21.029: INFO: Pod "azuredisk-volume-tester-ljmwv": Phase="Pending", Reason="", readiness=false. Elapsed: 20.169706715s
Jul 26 23:22:23.046: INFO: Pod "azuredisk-volume-tester-ljmwv": Phase="Failed", Reason="", readiness=false. Elapsed: 22.185937488s
STEP: Saw pod failure
Jul 26 23:22:23.046: INFO: Pod "azuredisk-volume-tester-ljmwv" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Jul 26 23:22:23.099: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-ljmwv"
Jul 26 23:22:23.116: INFO: Pod azuredisk-volume-tester-ljmwv has the following logs: /bin/sh: can't create /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-ljmwv in namespace azuredisk-8081
Jul 26 23:22:23.140: INFO: deleting PVC "azuredisk-8081"/"pvc-bxpl8"
... skipping 80 lines ...
  [single-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:67
    should succeed when creating a shared disk [disk.csi.azure.com][windows]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:138
------------------------------
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
Jul 26 23:22:59.803: INFO: >>> kubeConfig: /root/tmp162254381/kubeconfig/kubeconfig.northcentralus.json
STEP: Building a namespace api object, basename azuredisk
STEP: Waiting for a default service account to be provisioned in namespace
I0726 23:22:59.880740   14120 azuredisk_driver.go:57] Using azure disk driver: disk.csi.azure.com
... skipping 20 lines ...
Jul 26 23:23:02.602: INFO: PersistentVolumeClaim pvc-frnml found but phase is Pending instead of Bound.
Jul 26 23:23:04.617: INFO: PersistentVolumeClaim pvc-frnml found and phase=Bound (2.029366658s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jul 26 23:23:04.666: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-zs4bx" in namespace "azuredisk-495" to be "Succeeded or Failed"
Jul 26 23:23:04.682: INFO: Pod "azuredisk-volume-tester-zs4bx": Phase="Pending", Reason="", readiness=false. Elapsed: 15.3991ms
Jul 26 23:23:06.697: INFO: Pod "azuredisk-volume-tester-zs4bx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.030939958s
Jul 26 23:23:08.713: INFO: Pod "azuredisk-volume-tester-zs4bx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.047056441s
Jul 26 23:23:10.728: INFO: Pod "azuredisk-volume-tester-zs4bx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.061804329s
Jul 26 23:23:12.743: INFO: Pod "azuredisk-volume-tester-zs4bx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.076596634s
Jul 26 23:23:14.758: INFO: Pod "azuredisk-volume-tester-zs4bx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.092044615s
... skipping 5 lines ...
Jul 26 23:23:26.854: INFO: Pod "azuredisk-volume-tester-zs4bx": Phase="Pending", Reason="", readiness=false. Elapsed: 22.187448081s
Jul 26 23:23:28.870: INFO: Pod "azuredisk-volume-tester-zs4bx": Phase="Pending", Reason="", readiness=false. Elapsed: 24.203905537s
Jul 26 23:23:30.885: INFO: Pod "azuredisk-volume-tester-zs4bx": Phase="Pending", Reason="", readiness=false. Elapsed: 26.218778722s
Jul 26 23:23:32.901: INFO: Pod "azuredisk-volume-tester-zs4bx": Phase="Pending", Reason="", readiness=false. Elapsed: 28.234840691s
Jul 26 23:23:34.917: INFO: Pod "azuredisk-volume-tester-zs4bx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.251011235s
STEP: Saw pod success
Jul 26 23:23:34.918: INFO: Pod "azuredisk-volume-tester-zs4bx" satisfied condition "Succeeded or Failed"
Jul 26 23:23:34.918: INFO: deleting Pod "azuredisk-495"/"azuredisk-volume-tester-zs4bx"
Jul 26 23:23:34.938: INFO: Pod azuredisk-volume-tester-zs4bx has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-zs4bx in namespace azuredisk-495
Jul 26 23:23:34.960: INFO: deleting PVC "azuredisk-495"/"pvc-frnml"
Jul 26 23:23:34.960: INFO: Deleting PersistentVolumeClaim "pvc-frnml"
... skipping 40 lines ...
Jul 26 23:24:05.224: INFO: PersistentVolumeClaim pvc-p8b2p found and phase=Bound (2.033854036s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: attaching disk to node#0
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jul 26 23:24:21.538: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-b4vq4" in namespace "azuredisk-9947" to be "Succeeded or Failed"
Jul 26 23:24:21.557: INFO: Pod "azuredisk-volume-tester-b4vq4": Phase="Pending", Reason="", readiness=false. Elapsed: 19.593232ms
Jul 26 23:24:23.573: INFO: Pod "azuredisk-volume-tester-b4vq4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.035074513s
Jul 26 23:24:25.590: INFO: Pod "azuredisk-volume-tester-b4vq4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.052419713s
Jul 26 23:24:27.606: INFO: Pod "azuredisk-volume-tester-b4vq4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.068402134s
Jul 26 23:24:29.623: INFO: Pod "azuredisk-volume-tester-b4vq4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.084926475s
Jul 26 23:24:31.638: INFO: Pod "azuredisk-volume-tester-b4vq4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.100644266s
... skipping 9 lines ...
Jul 26 23:24:51.801: INFO: Pod "azuredisk-volume-tester-b4vq4": Phase="Pending", Reason="", readiness=false. Elapsed: 30.26287189s
Jul 26 23:24:53.817: INFO: Pod "azuredisk-volume-tester-b4vq4": Phase="Pending", Reason="", readiness=false. Elapsed: 32.27934869s
Jul 26 23:24:55.832: INFO: Pod "azuredisk-volume-tester-b4vq4": Phase="Pending", Reason="", readiness=false. Elapsed: 34.294663292s
Jul 26 23:24:57.849: INFO: Pod "azuredisk-volume-tester-b4vq4": Phase="Pending", Reason="", readiness=false. Elapsed: 36.311726863s
Jul 26 23:24:59.866: INFO: Pod "azuredisk-volume-tester-b4vq4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.328244788s
STEP: Saw pod success
Jul 26 23:24:59.866: INFO: Pod "azuredisk-volume-tester-b4vq4" satisfied condition "Succeeded or Failed"
Jul 26 23:24:59.866: INFO: deleting Pod "azuredisk-9947"/"azuredisk-volume-tester-b4vq4"
Jul 26 23:24:59.945: INFO: Pod azuredisk-volume-tester-b4vq4 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-b4vq4 in namespace azuredisk-9947
Jul 26 23:25:00.025: INFO: deleting PVC "azuredisk-9947"/"pvc-p8b2p"
Jul 26 23:25:00.025: INFO: Deleting PersistentVolumeClaim "pvc-p8b2p"
... skipping 65 lines ...
Jul 26 23:25:25.101: INFO: PersistentVolumeClaim pvc-99kph found and phase=Bound (4.049185879s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jul 26 23:25:25.149: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-25vw2" in namespace "azuredisk-5356" to be "Succeeded or Failed"
Jul 26 23:25:25.169: INFO: Pod "azuredisk-volume-tester-25vw2": Phase="Pending", Reason="", readiness=false. Elapsed: 20.586236ms
Jul 26 23:25:27.186: INFO: Pod "azuredisk-volume-tester-25vw2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.037252435s
Jul 26 23:25:29.203: INFO: Pod "azuredisk-volume-tester-25vw2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.053970768s
Jul 26 23:25:31.218: INFO: Pod "azuredisk-volume-tester-25vw2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.069739509s
Jul 26 23:25:33.234: INFO: Pod "azuredisk-volume-tester-25vw2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.084942068s
Jul 26 23:25:35.250: INFO: Pod "azuredisk-volume-tester-25vw2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.101910113s
Jul 26 23:25:37.267: INFO: Pod "azuredisk-volume-tester-25vw2": Phase="Pending", Reason="", readiness=false. Elapsed: 12.118092697s
Jul 26 23:25:39.284: INFO: Pod "azuredisk-volume-tester-25vw2": Phase="Pending", Reason="", readiness=false. Elapsed: 14.135101016s
Jul 26 23:25:41.299: INFO: Pod "azuredisk-volume-tester-25vw2": Phase="Pending", Reason="", readiness=false. Elapsed: 16.150563508s
Jul 26 23:25:43.315: INFO: Pod "azuredisk-volume-tester-25vw2": Phase="Pending", Reason="", readiness=false. Elapsed: 18.165999253s
Jul 26 23:25:45.332: INFO: Pod "azuredisk-volume-tester-25vw2": Phase="Pending", Reason="", readiness=false. Elapsed: 20.183000041s
Jul 26 23:25:47.348: INFO: Pod "azuredisk-volume-tester-25vw2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.199164894s
STEP: Saw pod success
Jul 26 23:25:47.348: INFO: Pod "azuredisk-volume-tester-25vw2" satisfied condition "Succeeded or Failed"
Jul 26 23:25:47.348: INFO: deleting Pod "azuredisk-5356"/"azuredisk-volume-tester-25vw2"
Jul 26 23:25:47.424: INFO: Pod azuredisk-volume-tester-25vw2 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-25vw2 in namespace azuredisk-5356
Jul 26 23:25:47.454: INFO: deleting PVC "azuredisk-5356"/"pvc-99kph"
Jul 26 23:25:47.454: INFO: Deleting PersistentVolumeClaim "pvc-99kph"
... skipping 44 lines ...
Jul 26 23:26:30.438: INFO: PersistentVolumeClaim pvc-x2tkl found but phase is Pending instead of Bound.
Jul 26 23:26:32.454: INFO: PersistentVolumeClaim pvc-x2tkl found and phase=Bound (4.046890678s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Jul 26 23:26:32.503: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-q9ss4" in namespace "azuredisk-6413" to be "Succeeded or Failed"
Jul 26 23:26:32.520: INFO: Pod "azuredisk-volume-tester-q9ss4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.905828ms
Jul 26 23:26:34.535: INFO: Pod "azuredisk-volume-tester-q9ss4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.032132858s
Jul 26 23:26:36.551: INFO: Pod "azuredisk-volume-tester-q9ss4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.047937072s
Jul 26 23:26:38.566: INFO: Pod "azuredisk-volume-tester-q9ss4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.063380763s
Jul 26 23:26:40.583: INFO: Pod "azuredisk-volume-tester-q9ss4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.080035646s
Jul 26 23:26:42.598: INFO: Pod "azuredisk-volume-tester-q9ss4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.095441842s
Jul 26 23:26:44.619: INFO: Pod "azuredisk-volume-tester-q9ss4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.115764263s
Jul 26 23:26:46.635: INFO: Pod "azuredisk-volume-tester-q9ss4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.131856109s
Jul 26 23:26:48.651: INFO: Pod "azuredisk-volume-tester-q9ss4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.148660222s
Jul 26 23:26:50.667: INFO: Pod "azuredisk-volume-tester-q9ss4": Phase="Pending", Reason="", readiness=false. Elapsed: 18.164035498s
Jul 26 23:26:52.682: INFO: Pod "azuredisk-volume-tester-q9ss4": Phase="Pending", Reason="", readiness=false. Elapsed: 20.179259556s
Jul 26 23:26:54.698: INFO: Pod "azuredisk-volume-tester-q9ss4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.195539725s
STEP: Saw pod success
Jul 26 23:26:54.698: INFO: Pod "azuredisk-volume-tester-q9ss4" satisfied condition "Succeeded or Failed"
Jul 26 23:26:54.698: INFO: deleting Pod "azuredisk-6413"/"azuredisk-volume-tester-q9ss4"
Jul 26 23:26:54.719: INFO: Pod azuredisk-volume-tester-q9ss4 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-q9ss4 in namespace azuredisk-6413
Jul 26 23:26:54.741: INFO: deleting PVC "azuredisk-6413"/"pvc-x2tkl"
Jul 26 23:26:54.741: INFO: Deleting PersistentVolumeClaim "pvc-x2tkl"
... skipping 4 lines ...