This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: fix: support create snapshot in parallel
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-04-06 08:29
Elapsed28m33s
Revisiona2dd442e705df62b6182901d1da23e8e208d91da
Refs 777

No Test Failures!


Error lines from build-log.txt

... skipping 65 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11248  100 11248    0     0   168k      0 --:--:-- --:--:-- --:--:--  168k
Downloading https://get.helm.sh/helm-v3.5.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:v2.0.0-alpha.1-3e50c36c0d5a6d7278c97e2e5437f3140f000571 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v2.0.0-alpha.1-3e50c36c0d5a6d7278c97e2e5437f3140f000571 not found: manifest unknown: manifest tagged by "v2.0.0-alpha.1-3e50c36c0d5a6d7278c97e2e5437f3140f000571" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
CGO_ENABLED=0 GOOS=linux go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=v2.0.0-alpha.1-3e50c36c0d5a6d7278c97e2e5437f3140f000571 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=3e50c36c0d5a6d7278c97e2e5437f3140f000571 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-04-06T08:36:52Z -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.DriverName=disk.csi.azure.com -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.topologyKey=topology.disk.csi.azure.com/zone -extldflags "-static"" -tags azurediskv2 -mod vendor -o _output/azurediskpluginv2 ./pkg/azurediskplugin
CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=v2.0.0-alpha.1-3e50c36c0d5a6d7278c97e2e5437f3140f000571 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=3e50c36c0d5a6d7278c97e2e5437f3140f000571 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-04-06T08:37:47Z -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.DriverName=disk.csi.azure.com -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.topologyKey=topology.disk.csi.azure.com/zone -extldflags "-static"" -tags azurediskv2 -mod vendor -o _output/azurediskpluginv2.exe ./pkg/azurediskplugin
docker buildx rm container-builder || true
error: no builder "container-builder" found
docker buildx create --use --name=container-builder
container-builder
make container-linux
make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker buildx build --pull --output=type=registry --platform="linux/amd64" --build-arg PLUGIN_NAME=azurediskpluginv2 \
	-t k8sprow.azurecr.io/azuredisk-csi:v2.0.0-alpha.1-3e50c36c0d5a6d7278c97e2e5437f3140f000571-linux-amd64 -f ./pkg/azurediskplugin/Dockerfile .
... skipping 1058 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 ...
                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 12 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 267 lines ...
                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
  version: v1beta1
... skipping 819 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 171 lines ...
Go Version: go1.16.1
Platform: linux/amd64
Topology Key: N/A

Streaming logs below:
STEP: Building a namespace api object, basename azuredisk
W0406 08:42:08.230208   13024 azure_config.go:46] Failed to get cloud-config from secret: failed to get secret azure-cloud-provider: secrets "azure-cloud-provider" not found, skip initializing from secret
I0406 08:42:08.231187   13024 azuredisk.go:147] disable UseInstanceMetadata for controller
I0406 08:42:08.232621   13024 driver.go:80] Enabling controller service capability: CREATE_DELETE_VOLUME
I0406 08:42:08.232725   13024 driver.go:80] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0406 08:42:08.232745   13024 driver.go:80] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0406 08:42:08.232754   13024 driver.go:80] Enabling controller service capability: LIST_SNAPSHOTS
I0406 08:42:08.232761   13024 driver.go:80] Enabling controller service capability: CLONE_VOLUME
... skipping 13 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
Apr  6 08:42:09.446: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-tzr4m" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Apr  6 08:42:09.478: INFO: Pod "azuredisk-volume-tester-tzr4m": Phase="Pending", Reason="", readiness=false. Elapsed: 32.152844ms
Apr  6 08:42:11.512: INFO: Pod "azuredisk-volume-tester-tzr4m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066194675s
Apr  6 08:42:13.546: INFO: Pod "azuredisk-volume-tester-tzr4m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.09952806s
Apr  6 08:42:15.581: INFO: Pod "azuredisk-volume-tester-tzr4m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.1344655s
Apr  6 08:42:17.615: INFO: Pod "azuredisk-volume-tester-tzr4m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.168725901s
Apr  6 08:42:19.648: INFO: Pod "azuredisk-volume-tester-tzr4m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.201602173s
... skipping 8 lines ...
Apr  6 08:42:37.956: INFO: Pod "azuredisk-volume-tester-tzr4m": Phase="Pending", Reason="", readiness=false. Elapsed: 28.510022768s
Apr  6 08:42:39.990: INFO: Pod "azuredisk-volume-tester-tzr4m": Phase="Pending", Reason="", readiness=false. Elapsed: 30.543852066s
Apr  6 08:42:42.024: INFO: Pod "azuredisk-volume-tester-tzr4m": Phase="Pending", Reason="", readiness=false. Elapsed: 32.578429235s
Apr  6 08:42:44.059: INFO: Pod "azuredisk-volume-tester-tzr4m": Phase="Pending", Reason="", readiness=false. Elapsed: 34.613323373s
Apr  6 08:42:46.094: INFO: Pod "azuredisk-volume-tester-tzr4m": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.648188119s
STEP: Saw pod success
Apr  6 08:42:46.094: INFO: Pod "azuredisk-volume-tester-tzr4m" satisfied condition "Succeeded or Failed"
Apr  6 08:42:46.094: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-tzr4m"
Apr  6 08:42:46.193: INFO: Pod azuredisk-volume-tester-tzr4m has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-tzr4m in namespace azuredisk-8081
STEP: validating provisioned PV
STEP: checking the PV
... skipping 41 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
Apr  6 08:43:51.998: INFO: deleting Pod "azuredisk-1318"/"azuredisk-volume-tester-7fx88"
Apr  6 08:43:52.034: INFO: Error getting logs for pod azuredisk-volume-tester-7fx88: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-7fx88)
STEP: Deleting pod azuredisk-volume-tester-7fx88 in namespace azuredisk-1318
STEP: validating provisioned PV
STEP: checking the PV
Apr  6 08:43:52.135: INFO: deleting PVC "azuredisk-1318"/"pvc-vbdwf"
Apr  6 08:43:52.135: INFO: Deleting PersistentVolumeClaim "pvc-vbdwf"
STEP: waiting for claim's PV "pvc-a3c9427f-5c70-4e5d-88f1-1d19b14f59c3" to be deleted
... skipping 38 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
Apr  6 08:44:43.774: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-rmj7l" in namespace "azuredisk-694" to be "Succeeded or Failed"
Apr  6 08:44:43.814: INFO: Pod "azuredisk-volume-tester-rmj7l": Phase="Pending", Reason="", readiness=false. Elapsed: 40.373627ms
Apr  6 08:44:45.848: INFO: Pod "azuredisk-volume-tester-rmj7l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.073867631s
Apr  6 08:44:47.882: INFO: Pod "azuredisk-volume-tester-rmj7l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.10803122s
Apr  6 08:44:49.917: INFO: Pod "azuredisk-volume-tester-rmj7l": Phase="Pending", Reason="", readiness=false. Elapsed: 6.142748741s
Apr  6 08:44:51.951: INFO: Pod "azuredisk-volume-tester-rmj7l": Phase="Pending", Reason="", readiness=false. Elapsed: 8.176704686s
Apr  6 08:44:53.986: INFO: Pod "azuredisk-volume-tester-rmj7l": Phase="Pending", Reason="", readiness=false. Elapsed: 10.212218178s
... skipping 2 lines ...
Apr  6 08:45:00.089: INFO: Pod "azuredisk-volume-tester-rmj7l": Phase="Pending", Reason="", readiness=false. Elapsed: 16.314890123s
Apr  6 08:45:02.123: INFO: Pod "azuredisk-volume-tester-rmj7l": Phase="Pending", Reason="", readiness=false. Elapsed: 18.349595783s
Apr  6 08:45:04.157: INFO: Pod "azuredisk-volume-tester-rmj7l": Phase="Pending", Reason="", readiness=false. Elapsed: 20.383277238s
Apr  6 08:45:06.193: INFO: Pod "azuredisk-volume-tester-rmj7l": Phase="Pending", Reason="", readiness=false. Elapsed: 22.419531652s
Apr  6 08:45:08.227: INFO: Pod "azuredisk-volume-tester-rmj7l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.453627101s
STEP: Saw pod success
Apr  6 08:45:08.228: INFO: Pod "azuredisk-volume-tester-rmj7l" satisfied condition "Succeeded or Failed"
Apr  6 08:45:08.228: INFO: deleting Pod "azuredisk-694"/"azuredisk-volume-tester-rmj7l"
Apr  6 08:45:08.266: INFO: Pod azuredisk-volume-tester-rmj7l has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-rmj7l in namespace azuredisk-694
STEP: validating provisioned PV
STEP: checking the PV
... skipping 39 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
Apr  6 08:45:50.025: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-886rb" in namespace "azuredisk-3274" to be "Error status code"
Apr  6 08:45:50.061: INFO: Pod "azuredisk-volume-tester-886rb": Phase="Pending", Reason="", readiness=false. Elapsed: 36.356298ms
Apr  6 08:45:52.095: INFO: Pod "azuredisk-volume-tester-886rb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069725927s
Apr  6 08:45:54.128: INFO: Pod "azuredisk-volume-tester-886rb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.10287395s
Apr  6 08:45:56.162: INFO: Pod "azuredisk-volume-tester-886rb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.136730846s
Apr  6 08:45:58.195: INFO: Pod "azuredisk-volume-tester-886rb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170005044s
Apr  6 08:46:00.229: INFO: Pod "azuredisk-volume-tester-886rb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.204385601s
Apr  6 08:46:02.264: INFO: Pod "azuredisk-volume-tester-886rb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.239339s
Apr  6 08:46:04.298: INFO: Pod "azuredisk-volume-tester-886rb": Phase="Pending", Reason="", readiness=false. Elapsed: 14.272905157s
Apr  6 08:46:06.332: INFO: Pod "azuredisk-volume-tester-886rb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.30733408s
Apr  6 08:46:08.367: INFO: Pod "azuredisk-volume-tester-886rb": Phase="Pending", Reason="", readiness=false. Elapsed: 18.341980735s
Apr  6 08:46:10.401: INFO: Pod "azuredisk-volume-tester-886rb": Phase="Pending", Reason="", readiness=false. Elapsed: 20.375548831s
Apr  6 08:46:12.435: INFO: Pod "azuredisk-volume-tester-886rb": Phase="Pending", Reason="", readiness=false. Elapsed: 22.409938787s
Apr  6 08:46:14.471: INFO: Pod "azuredisk-volume-tester-886rb": Phase="Failed", Reason="", readiness=false. Elapsed: 24.445610497s
STEP: Saw pod failure
Apr  6 08:46:14.471: INFO: Pod "azuredisk-volume-tester-886rb" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Apr  6 08:46:14.511: INFO: deleting Pod "azuredisk-3274"/"azuredisk-volume-tester-886rb"
Apr  6 08:46:14.548: INFO: Pod azuredisk-volume-tester-886rb has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-886rb in namespace azuredisk-3274
STEP: validating provisioned PV
... skipping 407 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
Apr  6 08:54:37.419: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-fvt6r" in namespace "azuredisk-3721" to be "Succeeded or Failed"
Apr  6 08:54:37.454: INFO: Pod "azuredisk-volume-tester-fvt6r": Phase="Pending", Reason="", readiness=false. Elapsed: 34.454912ms
Apr  6 08:54:39.489: INFO: Pod "azuredisk-volume-tester-fvt6r": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069505535s
Apr  6 08:54:41.522: INFO: Pod "azuredisk-volume-tester-fvt6r": Phase="Pending", Reason="", readiness=false. Elapsed: 4.102363758s
Apr  6 08:54:43.555: INFO: Pod "azuredisk-volume-tester-fvt6r": Phase="Pending", Reason="", readiness=false. Elapsed: 6.136000658s
Apr  6 08:54:45.590: INFO: Pod "azuredisk-volume-tester-fvt6r": Phase="Pending", Reason="", readiness=false. Elapsed: 8.170930576s
Apr  6 08:54:47.624: INFO: Pod "azuredisk-volume-tester-fvt6r": Phase="Pending", Reason="", readiness=false. Elapsed: 10.204572501s
... skipping 11 lines ...
Apr  6 08:55:12.058: INFO: Pod "azuredisk-volume-tester-fvt6r": Phase="Pending", Reason="", readiness=false. Elapsed: 34.638451115s
Apr  6 08:55:14.092: INFO: Pod "azuredisk-volume-tester-fvt6r": Phase="Pending", Reason="", readiness=false. Elapsed: 36.672879996s
Apr  6 08:55:16.126: INFO: Pod "azuredisk-volume-tester-fvt6r": Phase="Pending", Reason="", readiness=false. Elapsed: 38.706622438s
Apr  6 08:55:18.160: INFO: Pod "azuredisk-volume-tester-fvt6r": Phase="Pending", Reason="", readiness=false. Elapsed: 40.740681638s
Apr  6 08:55:20.193: INFO: Pod "azuredisk-volume-tester-fvt6r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.77415501s
STEP: Saw pod success
Apr  6 08:55:20.193: INFO: Pod "azuredisk-volume-tester-fvt6r" satisfied condition "Succeeded or Failed"
Apr  6 08:55:20.193: INFO: deleting Pod "azuredisk-3721"/"azuredisk-volume-tester-fvt6r"
Apr  6 08:55:20.292: INFO: Pod azuredisk-volume-tester-fvt6r has the following logs: hello world
hello world
hello world

STEP: Deleting pod azuredisk-volume-tester-fvt6r in namespace azuredisk-3721
... skipping 70 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
Apr  6 08:56:22.770: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-4hmrl" in namespace "azuredisk-2888" to be "Succeeded or Failed"
Apr  6 08:56:22.803: INFO: Pod "azuredisk-volume-tester-4hmrl": Phase="Pending", Reason="", readiness=false. Elapsed: 33.478324ms
Apr  6 08:56:24.837: INFO: Pod "azuredisk-volume-tester-4hmrl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066884566s
Apr  6 08:56:26.870: INFO: Pod "azuredisk-volume-tester-4hmrl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.099971452s
Apr  6 08:56:28.904: INFO: Pod "azuredisk-volume-tester-4hmrl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.13448352s
Apr  6 08:56:30.939: INFO: Pod "azuredisk-volume-tester-4hmrl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.169153907s
Apr  6 08:56:32.974: INFO: Pod "azuredisk-volume-tester-4hmrl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.20394289s
... skipping 25 lines ...
Apr  6 08:57:25.875: INFO: Pod "azuredisk-volume-tester-4hmrl": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.104895492s
Apr  6 08:57:27.910: INFO: Pod "azuredisk-volume-tester-4hmrl": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.139565958s
Apr  6 08:57:29.945: INFO: Pod "azuredisk-volume-tester-4hmrl": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.175413647s
Apr  6 08:57:31.981: INFO: Pod "azuredisk-volume-tester-4hmrl": Phase="Pending", Reason="", readiness=false. Elapsed: 1m9.210881545s
Apr  6 08:57:34.018: INFO: Pod "azuredisk-volume-tester-4hmrl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m11.24783867s
STEP: Saw pod success
Apr  6 08:57:34.018: INFO: Pod "azuredisk-volume-tester-4hmrl" satisfied condition "Succeeded or Failed"
Apr  6 08:57:34.018: INFO: deleting Pod "azuredisk-2888"/"azuredisk-volume-tester-4hmrl"
Apr  6 08:57:34.105: INFO: Pod azuredisk-volume-tester-4hmrl has the following logs: 100+0 records in
100+0 records out
104857600 bytes (100.0MB) copied, 0.074385 seconds, 1.3GB/s
hello world

... skipping 15 lines ...