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:30
Elapsed27m32s
Revisiona2dd442e705df62b6182901d1da23e8e208d91da
Refs 777

No Test Failures!


Error lines from build-log.txt

... skipping 63 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.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:v1.2.0-3e50c36c0d5a6d7278c97e2e5437f3140f000571 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v1.2.0-3e50c36c0d5a6d7278c97e2e5437f3140f000571 not found: manifest unknown: manifest tagged by "v1.2.0-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=v1.2.0-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:35:43Z -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""  -mod vendor -o _output/azurediskplugin ./pkg/azurediskplugin
CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=v1.2.0-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:14Z -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""  -mod vendor -o _output/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
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=azurediskplugin \
	-t k8sprow.azurecr.io/azuredisk-csi:v1.2.0-3e50c36c0d5a6d7278c97e2e5437f3140f000571-linux-amd64 -f ./pkg/azurediskplugin/Dockerfile .
... skipping 1096 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 168 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:40:52.412052   12896 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:40:52.413143   12896 azuredisk.go:147] disable UseInstanceMetadata for controller
I0406 08:40:52.413351   12896 driver.go:80] Enabling controller service capability: CREATE_DELETE_VOLUME
I0406 08:40:52.413451   12896 driver.go:80] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0406 08:40:52.413582   12896 driver.go:80] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0406 08:40:52.413641   12896 driver.go:80] Enabling controller service capability: LIST_SNAPSHOTS
I0406 08:40:52.413672   12896 driver.go:80] Enabling controller service capability: CLONE_VOLUME
... skipping 21 lines ...
Apr  6 08:40:57.624: INFO: PersistentVolumeClaim pvc-j5nkc found and phase=Bound (4.098699012s)
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
Apr  6 08:40:57.769: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-b2zg8" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Apr  6 08:40:57.801: INFO: Pod "azuredisk-volume-tester-b2zg8": Phase="Pending", Reason="", readiness=false. Elapsed: 31.617632ms
Apr  6 08:40:59.834: INFO: Pod "azuredisk-volume-tester-b2zg8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06408458s
Apr  6 08:41:01.867: INFO: Pod "azuredisk-volume-tester-b2zg8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.097339822s
Apr  6 08:41:03.901: INFO: Pod "azuredisk-volume-tester-b2zg8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.131482899s
Apr  6 08:41:05.933: INFO: Pod "azuredisk-volume-tester-b2zg8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.163965907s
Apr  6 08:41:07.967: INFO: Pod "azuredisk-volume-tester-b2zg8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.197866494s
... skipping 25 lines ...
Apr  6 08:42:00.852: INFO: Pod "azuredisk-volume-tester-b2zg8": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.082248631s
Apr  6 08:42:02.886: INFO: Pod "azuredisk-volume-tester-b2zg8": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.116490043s
Apr  6 08:42:04.919: INFO: Pod "azuredisk-volume-tester-b2zg8": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.149039282s
Apr  6 08:42:06.952: INFO: Pod "azuredisk-volume-tester-b2zg8": Phase="Pending", Reason="", readiness=false. Elapsed: 1m9.182535927s
Apr  6 08:42:08.986: INFO: Pod "azuredisk-volume-tester-b2zg8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m11.216107194s
STEP: Saw pod success
Apr  6 08:42:08.986: INFO: Pod "azuredisk-volume-tester-b2zg8" satisfied condition "Succeeded or Failed"
Apr  6 08:42:08.986: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-b2zg8"
Apr  6 08:42:09.050: INFO: Pod azuredisk-volume-tester-b2zg8 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-b2zg8 in namespace azuredisk-8081
Apr  6 08:42:09.091: INFO: deleting PVC "azuredisk-8081"/"pvc-j5nkc"
Apr  6 08:42:09.091: INFO: Deleting PersistentVolumeClaim "pvc-j5nkc"
... skipping 47 lines ...
STEP: validating provisioned PV
STEP: checking the PV
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod has 'FailedMount' event
Apr  6 08:43:20.897: INFO: deleting Pod "azuredisk-1318"/"azuredisk-volume-tester-bv5rc"
Apr  6 08:43:20.931: INFO: Error getting logs for pod azuredisk-volume-tester-bv5rc: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-bv5rc)
STEP: Deleting pod azuredisk-volume-tester-bv5rc in namespace azuredisk-1318
Apr  6 08:43:20.964: INFO: deleting PVC "azuredisk-1318"/"pvc-zxxjq"
Apr  6 08:43:20.965: INFO: Deleting PersistentVolumeClaim "pvc-zxxjq"
STEP: waiting for claim's PV "pvc-2ea92f3b-70b5-475e-9a04-1fe87bca9bcd" to be deleted
Apr  6 08:43:21.004: INFO: Waiting up to 10m0s for PersistentVolume pvc-2ea92f3b-70b5-475e-9a04-1fe87bca9bcd to get deleted
Apr  6 08:43:21.035: INFO: PersistentVolume pvc-2ea92f3b-70b5-475e-9a04-1fe87bca9bcd found and phase=Bound (31.29222ms)
... skipping 42 lines ...
Apr  6 08:44:06.610: INFO: PersistentVolumeClaim pvc-l4lbv found and phase=Bound (4.100360441s)
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
Apr  6 08:44:06.709: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-scm29" in namespace "azuredisk-694" to be "Succeeded or Failed"
Apr  6 08:44:06.741: INFO: Pod "azuredisk-volume-tester-scm29": Phase="Pending", Reason="", readiness=false. Elapsed: 31.833908ms
Apr  6 08:44:08.776: INFO: Pod "azuredisk-volume-tester-scm29": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067022386s
Apr  6 08:44:10.810: INFO: Pod "azuredisk-volume-tester-scm29": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100986687s
Apr  6 08:44:12.846: INFO: Pod "azuredisk-volume-tester-scm29": Phase="Pending", Reason="", readiness=false. Elapsed: 6.137220974s
Apr  6 08:44:14.881: INFO: Pod "azuredisk-volume-tester-scm29": Phase="Pending", Reason="", readiness=false. Elapsed: 8.171909485s
Apr  6 08:44:16.914: INFO: Pod "azuredisk-volume-tester-scm29": Phase="Pending", Reason="", readiness=false. Elapsed: 10.204984247s
Apr  6 08:44:18.963: INFO: Pod "azuredisk-volume-tester-scm29": Phase="Pending", Reason="", readiness=false. Elapsed: 12.253651184s
Apr  6 08:44:20.997: INFO: Pod "azuredisk-volume-tester-scm29": Phase="Pending", Reason="", readiness=false. Elapsed: 14.288500046s
Apr  6 08:44:23.031: INFO: Pod "azuredisk-volume-tester-scm29": Phase="Pending", Reason="", readiness=false. Elapsed: 16.322081526s
Apr  6 08:44:25.068: INFO: Pod "azuredisk-volume-tester-scm29": Phase="Pending", Reason="", readiness=false. Elapsed: 18.359157256s
Apr  6 08:44:27.102: INFO: Pod "azuredisk-volume-tester-scm29": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.392785256s
STEP: Saw pod success
Apr  6 08:44:27.102: INFO: Pod "azuredisk-volume-tester-scm29" satisfied condition "Succeeded or Failed"
Apr  6 08:44:27.102: INFO: deleting Pod "azuredisk-694"/"azuredisk-volume-tester-scm29"
Apr  6 08:44:27.138: INFO: Pod azuredisk-volume-tester-scm29 has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-scm29 in namespace azuredisk-694
Apr  6 08:44:27.180: INFO: deleting PVC "azuredisk-694"/"pvc-l4lbv"
Apr  6 08:44:27.180: INFO: Deleting PersistentVolumeClaim "pvc-l4lbv"
... skipping 42 lines ...
Apr  6 08:44:57.734: INFO: PersistentVolumeClaim pvc-lmbjw found and phase=Bound (4.100577905s)
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 an error
Apr  6 08:44:57.831: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-7lc6k" in namespace "azuredisk-3274" to be "Error status code"
Apr  6 08:44:57.866: INFO: Pod "azuredisk-volume-tester-7lc6k": Phase="Pending", Reason="", readiness=false. Elapsed: 34.275449ms
Apr  6 08:44:59.900: INFO: Pod "azuredisk-volume-tester-7lc6k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.068387973s
Apr  6 08:45:01.933: INFO: Pod "azuredisk-volume-tester-7lc6k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.101755454s
Apr  6 08:45:03.967: INFO: Pod "azuredisk-volume-tester-7lc6k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.135708657s
Apr  6 08:45:06.001: INFO: Pod "azuredisk-volume-tester-7lc6k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.169508682s
Apr  6 08:45:08.035: INFO: Pod "azuredisk-volume-tester-7lc6k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.203742228s
... skipping 2 lines ...
Apr  6 08:45:14.138: INFO: Pod "azuredisk-volume-tester-7lc6k": Phase="Pending", Reason="", readiness=false. Elapsed: 16.307046106s
Apr  6 08:45:16.172: INFO: Pod "azuredisk-volume-tester-7lc6k": Phase="Pending", Reason="", readiness=false. Elapsed: 18.340812444s
Apr  6 08:45:18.207: INFO: Pod "azuredisk-volume-tester-7lc6k": Phase="Pending", Reason="", readiness=false. Elapsed: 20.376019024s
Apr  6 08:45:20.242: INFO: Pod "azuredisk-volume-tester-7lc6k": Phase="Pending", Reason="", readiness=false. Elapsed: 22.410268479s
Apr  6 08:45:22.276: INFO: Pod "azuredisk-volume-tester-7lc6k": Phase="Pending", Reason="", readiness=false. Elapsed: 24.444709769s
Apr  6 08:45:24.310: INFO: Pod "azuredisk-volume-tester-7lc6k": Phase="Pending", Reason="", readiness=false. Elapsed: 26.478334953s
Apr  6 08:45:26.344: INFO: Pod "azuredisk-volume-tester-7lc6k": Phase="Failed", Reason="", readiness=false. Elapsed: 28.512276385s
STEP: Saw pod failure
Apr  6 08:45:26.344: INFO: Pod "azuredisk-volume-tester-7lc6k" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Apr  6 08:45:26.380: INFO: deleting Pod "azuredisk-3274"/"azuredisk-volume-tester-7lc6k"
Apr  6 08:45:26.416: INFO: Pod azuredisk-volume-tester-7lc6k has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-7lc6k in namespace azuredisk-3274
Apr  6 08:45:26.461: INFO: deleting PVC "azuredisk-3274"/"pvc-lmbjw"
... skipping 432 lines ...
Apr  6 08:54:45.185: INFO: PersistentVolumeClaim pvc-fq8bw found and phase=Bound (4.0995255s)
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
Apr  6 08:54:45.284: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-z92p5" in namespace "azuredisk-3721" to be "Succeeded or Failed"
Apr  6 08:54:45.316: INFO: Pod "azuredisk-volume-tester-z92p5": Phase="Pending", Reason="", readiness=false. Elapsed: 32.128616ms
Apr  6 08:54:47.349: INFO: Pod "azuredisk-volume-tester-z92p5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.064794801s
Apr  6 08:54:49.383: INFO: Pod "azuredisk-volume-tester-z92p5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.099571185s
Apr  6 08:54:51.419: INFO: Pod "azuredisk-volume-tester-z92p5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.134588039s
Apr  6 08:54:53.453: INFO: Pod "azuredisk-volume-tester-z92p5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.169571079s
Apr  6 08:54:55.488: INFO: Pod "azuredisk-volume-tester-z92p5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.20420258s
... skipping 11 lines ...
Apr  6 08:55:19.897: INFO: Pod "azuredisk-volume-tester-z92p5": Phase="Pending", Reason="", readiness=false. Elapsed: 34.612870734s
Apr  6 08:55:21.931: INFO: Pod "azuredisk-volume-tester-z92p5": Phase="Pending", Reason="", readiness=false. Elapsed: 36.647368848s
Apr  6 08:55:23.965: INFO: Pod "azuredisk-volume-tester-z92p5": Phase="Pending", Reason="", readiness=false. Elapsed: 38.68095089s
Apr  6 08:55:26.014: INFO: Pod "azuredisk-volume-tester-z92p5": Phase="Pending", Reason="", readiness=false. Elapsed: 40.730447995s
Apr  6 08:55:28.053: INFO: Pod "azuredisk-volume-tester-z92p5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.768916561s
STEP: Saw pod success
Apr  6 08:55:28.053: INFO: Pod "azuredisk-volume-tester-z92p5" satisfied condition "Succeeded or Failed"
Apr  6 08:55:28.053: INFO: deleting Pod "azuredisk-3721"/"azuredisk-volume-tester-z92p5"
Apr  6 08:55:28.199: INFO: Pod azuredisk-volume-tester-z92p5 has the following logs: hello world
hello world
hello world

STEP: Deleting pod azuredisk-volume-tester-z92p5 in namespace azuredisk-3721
... skipping 80 lines ...
Apr  6 08:56:38.523: INFO: PersistentVolumeClaim pvc-4k8dx found and phase=Bound (4.100284298s)
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
Apr  6 08:56:38.623: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-gsztw" in namespace "azuredisk-2888" to be "Succeeded or Failed"
Apr  6 08:56:38.655: INFO: Pod "azuredisk-volume-tester-gsztw": Phase="Pending", Reason="", readiness=false. Elapsed: 31.785384ms
Apr  6 08:56:40.689: INFO: Pod "azuredisk-volume-tester-gsztw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.066440715s
Apr  6 08:56:42.723: INFO: Pod "azuredisk-volume-tester-gsztw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.100330809s
Apr  6 08:56:44.757: INFO: Pod "azuredisk-volume-tester-gsztw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.133791782s
Apr  6 08:56:46.791: INFO: Pod "azuredisk-volume-tester-gsztw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.167977973s
Apr  6 08:56:48.829: INFO: Pod "azuredisk-volume-tester-gsztw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.206490704s
... skipping 7 lines ...
Apr  6 08:57:05.097: INFO: Pod "azuredisk-volume-tester-gsztw": Phase="Pending", Reason="", readiness=false. Elapsed: 26.474599123s
Apr  6 08:57:07.132: INFO: Pod "azuredisk-volume-tester-gsztw": Phase="Pending", Reason="", readiness=false. Elapsed: 28.509343658s
Apr  6 08:57:09.166: INFO: Pod "azuredisk-volume-tester-gsztw": Phase="Pending", Reason="", readiness=false. Elapsed: 30.543546114s
Apr  6 08:57:11.202: INFO: Pod "azuredisk-volume-tester-gsztw": Phase="Pending", Reason="", readiness=false. Elapsed: 32.57914514s
Apr  6 08:57:13.236: INFO: Pod "azuredisk-volume-tester-gsztw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 34.613565055s
STEP: Saw pod success
Apr  6 08:57:13.236: INFO: Pod "azuredisk-volume-tester-gsztw" satisfied condition "Succeeded or Failed"
Apr  6 08:57:13.236: INFO: deleting Pod "azuredisk-2888"/"azuredisk-volume-tester-gsztw"
Apr  6 08:57:13.293: INFO: Pod azuredisk-volume-tester-gsztw has the following logs: 100+0 records in
100+0 records out
104857600 bytes (100.0MB) copied, 0.059527 seconds, 1.6GB/s
hello world

... skipping 112 lines ...