This job view page is being replaced by Spyglass soon. Check out the new job view.
PRedreed: feat: Azure Disk CSI Driver V2 (a.k.a. Project Mandalay) initial implementation
ResultABORTED
Tests 0 failed / 19 succeeded
Started2021-06-09 16:50
Elapsed1h13m
Revision24afed1d758a5087c010476b0508042d3e565e81
Refs 864

No Test Failures!


Show 19 Passed Tests

Show 66 Skipped Tests

Error lines from build-log.txt

... skipping 69 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11248  100 11248    0     0  98666      0 --:--:-- --:--:-- --:--:-- 98666
Downloading https://get.helm.sh/helm-v3.6.0-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-db065d4b460d614e20b145fcfd8771d38a9550f7 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v2.0.0-alpha.1-db065d4b460d614e20b145fcfd8771d38a9550f7 not found: manifest unknown: manifest tagged by "v2.0.0-alpha.1-db065d4b460d614e20b145fcfd8771d38a9550f7" 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=v2.0.0-alpha.1-db065d4b460d614e20b145fcfd8771d38a9550f7 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=db065d4b460d614e20b145fcfd8771d38a9550f7 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2021-06-09T16:58:26Z -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/amd64/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
# 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 1588 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 227 lines ...
            type: object
          status:
            description: status represents the current state of AzVolumeAttachment.
              Nil status indicates that the underlying volume of AzVolumeAttachment
              has not yet been attached to the specified node
            properties:
              error:
                description: Error occurred during attach/detach of volume
                properties:
                  currentNode:
                    description: "NodeName is a type that holds a api.Node's Name
                      identifier. Being a type captures intent and helps make sure
                      that the node name is not confused with similar concepts (the
                      hostname, the cloud provider id, the cloud provider name etc)
... skipping 197 lines ...
            - volumeCapability
            type: object
          status:
            description: status represents the current state of AzVolume. Nil status
              indicates that the underlying volume has not yet been provisioned
            properties:
              error:
                description: Error occurred during creation/deletion of volume
                properties:
                  currentNode:
                    description: "NodeName is a type that holds a api.Node's Name
                      identifier. Being a type captures intent and helps make sure
                      that the node name is not confused with similar concepts (the
                      hostname, the cloud provider id, the cloud provider name etc)
... skipping 1006 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 253 lines ...
Go Version: go1.16.4
Platform: linux/amd64
Topology Key: N/A

Streaming logs below:
STEP: Building a namespace api object, basename azuredisk
E0609 17:11:12.330959   14465 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
I0609 17:11:12.345866   14465 azuredisk_v2.go:173] disable UseInstanceMetadata for controller
I0609 17:11:12.352512   14465 driver.go:80] Enabling controller service capability: CREATE_DELETE_VOLUME
I0609 17:11:12.352644   14465 driver.go:80] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0609 17:11:12.352687   14465 driver.go:80] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0609 17:11:12.352707   14465 driver.go:80] Enabling controller service capability: LIST_SNAPSHOTS
I0609 17:11:12.352733   14465 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
Jun  9 17:11:14.237: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-cngbs" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Jun  9 17:11:14.285: INFO: Pod "azuredisk-volume-tester-cngbs": Phase="Pending", Reason="", readiness=false. Elapsed: 48.13782ms
Jun  9 17:11:16.335: INFO: Pod "azuredisk-volume-tester-cngbs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.098297113s
Jun  9 17:11:18.382: INFO: Pod "azuredisk-volume-tester-cngbs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.145347949s
Jun  9 17:11:20.430: INFO: Pod "azuredisk-volume-tester-cngbs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.193277691s
Jun  9 17:11:22.477: INFO: Pod "azuredisk-volume-tester-cngbs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.239623995s
Jun  9 17:11:24.526: INFO: Pod "azuredisk-volume-tester-cngbs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.28874478s
... skipping 8 lines ...
Jun  9 17:11:42.963: INFO: Pod "azuredisk-volume-tester-cngbs": Phase="Pending", Reason="", readiness=false. Elapsed: 28.726318123s
Jun  9 17:11:45.010: INFO: Pod "azuredisk-volume-tester-cngbs": Phase="Pending", Reason="", readiness=false. Elapsed: 30.773162686s
Jun  9 17:11:47.057: INFO: Pod "azuredisk-volume-tester-cngbs": Phase="Pending", Reason="", readiness=false. Elapsed: 32.819518791s
Jun  9 17:11:49.105: INFO: Pod "azuredisk-volume-tester-cngbs": Phase="Pending", Reason="", readiness=false. Elapsed: 34.86764029s
Jun  9 17:11:51.152: INFO: Pod "azuredisk-volume-tester-cngbs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.915142697s
STEP: Saw pod success
Jun  9 17:11:51.152: INFO: Pod "azuredisk-volume-tester-cngbs" satisfied condition "Succeeded or Failed"
Jun  9 17:11:51.152: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-cngbs"
Jun  9 17:11:51.260: INFO: Pod azuredisk-volume-tester-cngbs has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-cngbs in namespace azuredisk-8081
STEP: validating provisioned PV
STEP: checking the PV
... skipping 38 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
Jun  9 17:12:42.387: INFO: deleting Pod "azuredisk-1318"/"azuredisk-volume-tester-zzt2g"
Jun  9 17:12:42.439: INFO: Error getting logs for pod azuredisk-volume-tester-zzt2g: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-zzt2g)
STEP: Deleting pod azuredisk-volume-tester-zzt2g in namespace azuredisk-1318
STEP: validating provisioned PV
STEP: checking the PV
Jun  9 17:12:42.582: INFO: deleting PVC "azuredisk-1318"/"pvc-kswrf"
Jun  9 17:12:42.582: INFO: Deleting PersistentVolumeClaim "pvc-kswrf"
STEP: waiting for claim's PV "pvc-a9bf7c26-7fdc-44b8-ad3b-a3c280aca84a" to be deleted
... skipping 37 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
Jun  9 17:13:29.755: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-x94gv" in namespace "azuredisk-694" to be "Succeeded or Failed"
Jun  9 17:13:29.800: INFO: Pod "azuredisk-volume-tester-x94gv": Phase="Pending", Reason="", readiness=false. Elapsed: 45.293717ms
Jun  9 17:13:31.847: INFO: Pod "azuredisk-volume-tester-x94gv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.091454296s
Jun  9 17:13:33.893: INFO: Pod "azuredisk-volume-tester-x94gv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.13756093s
Jun  9 17:13:35.940: INFO: Pod "azuredisk-volume-tester-x94gv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.184684852s
Jun  9 17:13:37.990: INFO: Pod "azuredisk-volume-tester-x94gv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.234769832s
Jun  9 17:13:40.037: INFO: Pod "azuredisk-volume-tester-x94gv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.281749456s
... skipping 10 lines ...
Jun  9 17:14:02.569: INFO: Pod "azuredisk-volume-tester-x94gv": Phase="Pending", Reason="", readiness=false. Elapsed: 32.814258897s
Jun  9 17:14:04.617: INFO: Pod "azuredisk-volume-tester-x94gv": Phase="Pending", Reason="", readiness=false. Elapsed: 34.861420399s
Jun  9 17:14:06.664: INFO: Pod "azuredisk-volume-tester-x94gv": Phase="Pending", Reason="", readiness=false. Elapsed: 36.908370717s
Jun  9 17:14:08.710: INFO: Pod "azuredisk-volume-tester-x94gv": Phase="Pending", Reason="", readiness=false. Elapsed: 38.954798574s
Jun  9 17:14:10.757: INFO: Pod "azuredisk-volume-tester-x94gv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.001809084s
STEP: Saw pod success
Jun  9 17:14:10.757: INFO: Pod "azuredisk-volume-tester-x94gv" satisfied condition "Succeeded or Failed"
Jun  9 17:14:10.757: INFO: deleting Pod "azuredisk-694"/"azuredisk-volume-tester-x94gv"
Jun  9 17:14:10.806: INFO: Pod azuredisk-volume-tester-x94gv has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-x94gv 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
Jun  9 17:14:52.967: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-stc8n" in namespace "azuredisk-3274" to be "Error status code"
Jun  9 17:14:53.012: INFO: Pod "azuredisk-volume-tester-stc8n": Phase="Pending", Reason="", readiness=false. Elapsed: 45.353757ms
Jun  9 17:14:55.059: INFO: Pod "azuredisk-volume-tester-stc8n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.092338607s
Jun  9 17:14:57.106: INFO: Pod "azuredisk-volume-tester-stc8n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.138962033s
Jun  9 17:14:59.153: INFO: Pod "azuredisk-volume-tester-stc8n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.185994933s
Jun  9 17:15:01.199: INFO: Pod "azuredisk-volume-tester-stc8n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.232339607s
Jun  9 17:15:03.247: INFO: Pod "azuredisk-volume-tester-stc8n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.27997903s
Jun  9 17:15:05.295: INFO: Pod "azuredisk-volume-tester-stc8n": Phase="Pending", Reason="", readiness=false. Elapsed: 12.328227247s
Jun  9 17:15:07.342: INFO: Pod "azuredisk-volume-tester-stc8n": Phase="Pending", Reason="", readiness=false. Elapsed: 14.37521971s
Jun  9 17:15:09.389: INFO: Pod "azuredisk-volume-tester-stc8n": Phase="Pending", Reason="", readiness=false. Elapsed: 16.421825786s
Jun  9 17:15:11.435: INFO: Pod "azuredisk-volume-tester-stc8n": Phase="Pending", Reason="", readiness=false. Elapsed: 18.468196785s
Jun  9 17:15:13.482: INFO: Pod "azuredisk-volume-tester-stc8n": Phase="Pending", Reason="", readiness=false. Elapsed: 20.514918489s
Jun  9 17:15:15.529: INFO: Pod "azuredisk-volume-tester-stc8n": Phase="Pending", Reason="", readiness=false. Elapsed: 22.562244284s
Jun  9 17:15:17.576: INFO: Pod "azuredisk-volume-tester-stc8n": Phase="Failed", Reason="", readiness=false. Elapsed: 24.609081694s
STEP: Saw pod failure
Jun  9 17:15:17.576: INFO: Pod "azuredisk-volume-tester-stc8n" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Jun  9 17:15:17.625: INFO: deleting Pod "azuredisk-3274"/"azuredisk-volume-tester-stc8n"
Jun  9 17:15:17.673: INFO: Pod azuredisk-volume-tester-stc8n has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-stc8n in namespace azuredisk-3274
STEP: validating provisioned PV
... skipping 336 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
Jun  9 17:24:33.785: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-6rznw" in namespace "azuredisk-3090" to be "Succeeded or Failed"
Jun  9 17:24:33.833: INFO: Pod "azuredisk-volume-tester-6rznw": Phase="Pending", Reason="", readiness=false. Elapsed: 47.491478ms
Jun  9 17:24:35.880: INFO: Pod "azuredisk-volume-tester-6rznw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.094345173s
Jun  9 17:24:37.934: INFO: Pod "azuredisk-volume-tester-6rznw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.148597316s
Jun  9 17:24:40.037: INFO: Pod "azuredisk-volume-tester-6rznw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.25124607s
Jun  9 17:24:42.082: INFO: Pod "azuredisk-volume-tester-6rznw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.29658862s
Jun  9 17:24:44.131: INFO: Pod "azuredisk-volume-tester-6rznw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.345166933s
... skipping 2 lines ...
Jun  9 17:24:50.275: INFO: Pod "azuredisk-volume-tester-6rznw": Phase="Pending", Reason="", readiness=false. Elapsed: 16.489211555s
Jun  9 17:24:52.321: INFO: Pod "azuredisk-volume-tester-6rznw": Phase="Pending", Reason="", readiness=false. Elapsed: 18.535488824s
Jun  9 17:24:54.368: INFO: Pod "azuredisk-volume-tester-6rznw": Phase="Pending", Reason="", readiness=false. Elapsed: 20.582570821s
Jun  9 17:24:56.414: INFO: Pod "azuredisk-volume-tester-6rznw": Phase="Pending", Reason="", readiness=false. Elapsed: 22.628788997s
Jun  9 17:24:58.461: INFO: Pod "azuredisk-volume-tester-6rznw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.675702737s
STEP: Saw pod success
Jun  9 17:24:58.461: INFO: Pod "azuredisk-volume-tester-6rznw" satisfied condition "Succeeded or Failed"
STEP: cloning existing volume
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying a second pod with cloned volume
STEP: checking that the pod's command exits with no error
Jun  9 17:24:58.654: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vcjg2" in namespace "azuredisk-3090" to be "Succeeded or Failed"
Jun  9 17:24:58.702: INFO: Pod "azuredisk-volume-tester-vcjg2": Phase="Pending", Reason="", readiness=false. Elapsed: 47.778563ms
Jun  9 17:25:00.749: INFO: Pod "azuredisk-volume-tester-vcjg2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.095398211s
Jun  9 17:25:02.795: INFO: Pod "azuredisk-volume-tester-vcjg2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.141083391s
Jun  9 17:25:04.841: INFO: Pod "azuredisk-volume-tester-vcjg2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.187468781s
Jun  9 17:25:06.890: INFO: Pod "azuredisk-volume-tester-vcjg2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.236204974s
Jun  9 17:25:08.939: INFO: Pod "azuredisk-volume-tester-vcjg2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.2848238s
... skipping 10 lines ...
Jun  9 17:25:31.461: INFO: Pod "azuredisk-volume-tester-vcjg2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.807262553s
Jun  9 17:25:33.508: INFO: Pod "azuredisk-volume-tester-vcjg2": Phase="Pending", Reason="", readiness=false. Elapsed: 34.85451228s
Jun  9 17:25:35.556: INFO: Pod "azuredisk-volume-tester-vcjg2": Phase="Pending", Reason="", readiness=false. Elapsed: 36.901576474s
Jun  9 17:25:37.602: INFO: Pod "azuredisk-volume-tester-vcjg2": Phase="Pending", Reason="", readiness=false. Elapsed: 38.947859037s
Jun  9 17:25:39.648: INFO: Pod "azuredisk-volume-tester-vcjg2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.994115306s
STEP: Saw pod success
Jun  9 17:25:39.648: INFO: Pod "azuredisk-volume-tester-vcjg2" satisfied condition "Succeeded or Failed"
Jun  9 17:25:39.648: INFO: deleting Pod "azuredisk-3090"/"azuredisk-volume-tester-vcjg2"
Jun  9 17:25:39.779: INFO: Pod azuredisk-volume-tester-vcjg2 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-vcjg2 in namespace azuredisk-3090
STEP: validating provisioned PV
STEP: checking the PV
... skipping 53 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
Jun  9 17:26:32.563: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-9lrsg" in namespace "azuredisk-4078" to be "Succeeded or Failed"
Jun  9 17:26:32.611: INFO: Pod "azuredisk-volume-tester-9lrsg": Phase="Pending", Reason="", readiness=false. Elapsed: 48.431752ms
Jun  9 17:26:34.659: INFO: Pod "azuredisk-volume-tester-9lrsg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.096371105s
Jun  9 17:26:36.705: INFO: Pod "azuredisk-volume-tester-9lrsg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.142496692s
Jun  9 17:26:38.752: INFO: Pod "azuredisk-volume-tester-9lrsg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.189263401s
Jun  9 17:26:40.799: INFO: Pod "azuredisk-volume-tester-9lrsg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.236160077s
Jun  9 17:26:42.847: INFO: Pod "azuredisk-volume-tester-9lrsg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.284579119s
... skipping 10 lines ...
Jun  9 17:27:05.370: INFO: Pod "azuredisk-volume-tester-9lrsg": Phase="Pending", Reason="", readiness=false. Elapsed: 32.806843322s
Jun  9 17:27:07.421: INFO: Pod "azuredisk-volume-tester-9lrsg": Phase="Pending", Reason="", readiness=false. Elapsed: 34.858565852s
Jun  9 17:27:09.470: INFO: Pod "azuredisk-volume-tester-9lrsg": Phase="Pending", Reason="", readiness=false. Elapsed: 36.906936624s
Jun  9 17:27:11.518: INFO: Pod "azuredisk-volume-tester-9lrsg": Phase="Pending", Reason="", readiness=false. Elapsed: 38.954750575s
Jun  9 17:27:13.565: INFO: Pod "azuredisk-volume-tester-9lrsg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.001922248s
STEP: Saw pod success
Jun  9 17:27:13.565: INFO: Pod "azuredisk-volume-tester-9lrsg" satisfied condition "Succeeded or Failed"
STEP: cloning existing volume
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying a second pod with cloned volume
STEP: checking that the pod's command exits with no error
Jun  9 17:27:13.761: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-fs62g" in namespace "azuredisk-4078" to be "Succeeded or Failed"
Jun  9 17:27:13.810: INFO: Pod "azuredisk-volume-tester-fs62g": Phase="Pending", Reason="", readiness=false. Elapsed: 49.440988ms
Jun  9 17:27:15.859: INFO: Pod "azuredisk-volume-tester-fs62g": Phase="Pending", Reason="", readiness=false. Elapsed: 2.097654493s
Jun  9 17:27:17.905: INFO: Pod "azuredisk-volume-tester-fs62g": Phase="Pending", Reason="", readiness=false. Elapsed: 4.144389637s
Jun  9 17:27:19.953: INFO: Pod "azuredisk-volume-tester-fs62g": Phase="Pending", Reason="", readiness=false. Elapsed: 6.191747352s
Jun  9 17:27:22.000: INFO: Pod "azuredisk-volume-tester-fs62g": Phase="Pending", Reason="", readiness=false. Elapsed: 8.238930869s
Jun  9 17:27:24.049: INFO: Pod "azuredisk-volume-tester-fs62g": Phase="Pending", Reason="", readiness=false. Elapsed: 10.28802251s
... skipping 2 lines ...
Jun  9 17:27:30.196: INFO: Pod "azuredisk-volume-tester-fs62g": Phase="Pending", Reason="", readiness=false. Elapsed: 16.435018944s
Jun  9 17:27:32.242: INFO: Pod "azuredisk-volume-tester-fs62g": Phase="Pending", Reason="", readiness=false. Elapsed: 18.48152916s
Jun  9 17:27:34.291: INFO: Pod "azuredisk-volume-tester-fs62g": Phase="Pending", Reason="", readiness=false. Elapsed: 20.530061003s
Jun  9 17:27:36.339: INFO: Pod "azuredisk-volume-tester-fs62g": Phase="Pending", Reason="", readiness=false. Elapsed: 22.578340917s
Jun  9 17:27:38.387: INFO: Pod "azuredisk-volume-tester-fs62g": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.626544717s
STEP: Saw pod success
Jun  9 17:27:38.387: INFO: Pod "azuredisk-volume-tester-fs62g" satisfied condition "Succeeded or Failed"
Jun  9 17:27:38.388: INFO: deleting Pod "azuredisk-4078"/"azuredisk-volume-tester-fs62g"
Jun  9 17:27:38.436: INFO: Pod azuredisk-volume-tester-fs62g has the following logs: 20.0G

STEP: Deleting pod azuredisk-volume-tester-fs62g in namespace azuredisk-4078
STEP: validating provisioned PV
STEP: checking the PV
... skipping 63 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
Jun  9 17:28:31.321: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-z9hbh" in namespace "azuredisk-3721" to be "Succeeded or Failed"
Jun  9 17:28:31.373: INFO: Pod "azuredisk-volume-tester-z9hbh": Phase="Pending", Reason="", readiness=false. Elapsed: 52.14067ms
Jun  9 17:28:33.419: INFO: Pod "azuredisk-volume-tester-z9hbh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.098553332s
Jun  9 17:28:35.466: INFO: Pod "azuredisk-volume-tester-z9hbh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.144811235s
Jun  9 17:28:37.517: INFO: Pod "azuredisk-volume-tester-z9hbh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.196779764s
Jun  9 17:28:39.565: INFO: Pod "azuredisk-volume-tester-z9hbh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.24412006s
Jun  9 17:28:41.615: INFO: Pod "azuredisk-volume-tester-z9hbh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.293969356s
... skipping 10 lines ...
Jun  9 17:29:04.138: INFO: Pod "azuredisk-volume-tester-z9hbh": Phase="Pending", Reason="", readiness=false. Elapsed: 32.817415505s
Jun  9 17:29:06.185: INFO: Pod "azuredisk-volume-tester-z9hbh": Phase="Pending", Reason="", readiness=false. Elapsed: 34.864714396s
Jun  9 17:29:08.235: INFO: Pod "azuredisk-volume-tester-z9hbh": Phase="Pending", Reason="", readiness=false. Elapsed: 36.914476449s
Jun  9 17:29:10.282: INFO: Pod "azuredisk-volume-tester-z9hbh": Phase="Pending", Reason="", readiness=false. Elapsed: 38.961173397s
Jun  9 17:29:12.329: INFO: Pod "azuredisk-volume-tester-z9hbh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.008330372s
STEP: Saw pod success
Jun  9 17:29:12.329: INFO: Pod "azuredisk-volume-tester-z9hbh" satisfied condition "Succeeded or Failed"
Jun  9 17:29:12.329: INFO: deleting Pod "azuredisk-3721"/"azuredisk-volume-tester-z9hbh"
Jun  9 17:29:12.378: INFO: Pod azuredisk-volume-tester-z9hbh has the following logs: hello world
hello world
hello world

STEP: Deleting pod azuredisk-volume-tester-z9hbh in namespace azuredisk-3721
... skipping 71 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
Jun  9 17:30:20.568: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-p6rz5" in namespace "azuredisk-2888" to be "Succeeded or Failed"
Jun  9 17:30:20.631: INFO: Pod "azuredisk-volume-tester-p6rz5": Phase="Pending", Reason="", readiness=false. Elapsed: 62.804987ms
Jun  9 17:30:22.678: INFO: Pod "azuredisk-volume-tester-p6rz5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.109281674s
Jun  9 17:30:24.725: INFO: Pod "azuredisk-volume-tester-p6rz5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.157077366s
Jun  9 17:30:26.780: INFO: Pod "azuredisk-volume-tester-p6rz5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.211866984s
Jun  9 17:30:28.828: INFO: Pod "azuredisk-volume-tester-p6rz5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.259694957s
Jun  9 17:30:30.875: INFO: Pod "azuredisk-volume-tester-p6rz5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.306862323s
... skipping 10 lines ...
Jun  9 17:30:53.395: INFO: Pod "azuredisk-volume-tester-p6rz5": Phase="Pending", Reason="", readiness=false. Elapsed: 32.82667404s
Jun  9 17:30:55.445: INFO: Pod "azuredisk-volume-tester-p6rz5": Phase="Pending", Reason="", readiness=false. Elapsed: 34.877188746s
Jun  9 17:30:57.493: INFO: Pod "azuredisk-volume-tester-p6rz5": Phase="Pending", Reason="", readiness=false. Elapsed: 36.924902372s
Jun  9 17:30:59.542: INFO: Pod "azuredisk-volume-tester-p6rz5": Phase="Pending", Reason="", readiness=false. Elapsed: 38.973823468s
Jun  9 17:31:01.590: INFO: Pod "azuredisk-volume-tester-p6rz5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 41.021266769s
STEP: Saw pod success
Jun  9 17:31:01.590: INFO: Pod "azuredisk-volume-tester-p6rz5" satisfied condition "Succeeded or Failed"
Jun  9 17:31:01.590: INFO: deleting Pod "azuredisk-2888"/"azuredisk-volume-tester-p6rz5"
Jun  9 17:31:01.695: INFO: Pod azuredisk-volume-tester-p6rz5 has the following logs: 100+0 records in
100+0 records out
104857600 bytes (100.0MB) copied, 0.065851 seconds, 1.5GB/s
hello world

... skipping 50 lines ...
Jun  9 17:31:39.306: INFO: >>> kubeConfig: /root/tmp713684325/kubeconfig/kubeconfig.eastus2.json
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jun  9 17:31:39.450: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-hgkg5" in namespace "azuredisk-8510" to be "Succeeded or Failed"
Jun  9 17:31:39.498: INFO: Pod "azuredisk-volume-tester-hgkg5": Phase="Pending", Reason="", readiness=false. Elapsed: 47.671535ms
Jun  9 17:31:41.545: INFO: Pod "azuredisk-volume-tester-hgkg5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.094227832s
Jun  9 17:31:43.593: INFO: Pod "azuredisk-volume-tester-hgkg5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.142887042s
Jun  9 17:31:45.640: INFO: Pod "azuredisk-volume-tester-hgkg5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.189810463s
Jun  9 17:31:47.686: INFO: Pod "azuredisk-volume-tester-hgkg5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.23589198s
Jun  9 17:31:49.734: INFO: Pod "azuredisk-volume-tester-hgkg5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.283160017s
... skipping 10 lines ...
Jun  9 17:32:12.260: INFO: Pod "azuredisk-volume-tester-hgkg5": Phase="Pending", Reason="", readiness=false. Elapsed: 32.809095804s
Jun  9 17:32:14.306: INFO: Pod "azuredisk-volume-tester-hgkg5": Phase="Pending", Reason="", readiness=false. Elapsed: 34.855922266s
Jun  9 17:32:16.353: INFO: Pod "azuredisk-volume-tester-hgkg5": Phase="Pending", Reason="", readiness=false. Elapsed: 36.902591451s
Jun  9 17:32:18.399: INFO: Pod "azuredisk-volume-tester-hgkg5": Phase="Pending", Reason="", readiness=false. Elapsed: 38.948830587s
Jun  9 17:32:20.447: INFO: Pod "azuredisk-volume-tester-hgkg5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.996751902s
STEP: Saw pod success
Jun  9 17:32:20.447: INFO: Pod "azuredisk-volume-tester-hgkg5" satisfied condition "Succeeded or Failed"
STEP: Checking Prow test resource group
2021/06/09 17:32:20 Running in Prow, converting AZURE_CREDENTIALS to AZURE_CREDENTIAL_FILE
2021/06/09 17:32:20 Reading credentials file /etc/azure-cred/credentials
STEP: Prow test resource group: kubetest-e0ffkymh
STEP: Creating external resource group: azuredisk-csi-driver-test-a4cad519-c948-11eb-b795-1e6c77c4ab3d
STEP: creating volume snapshot class with external rg azuredisk-csi-driver-test-a4cad519-c948-11eb-b795-1e6c77c4ab3d
... skipping 5 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 a pod with a volume restored from the snapshot
STEP: checking that the pod's command exits with no error
Jun  9 17:32:36.750: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-72jzb" in namespace "azuredisk-8510" to be "Succeeded or Failed"
Jun  9 17:32:36.828: INFO: Pod "azuredisk-volume-tester-72jzb": Phase="Pending", Reason="", readiness=false. Elapsed: 77.612473ms
Jun  9 17:32:38.875: INFO: Pod "azuredisk-volume-tester-72jzb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.124933084s
Jun  9 17:32:40.923: INFO: Pod "azuredisk-volume-tester-72jzb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.172634004s
Jun  9 17:32:42.972: INFO: Pod "azuredisk-volume-tester-72jzb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.221832635s
Jun  9 17:32:45.019: INFO: Pod "azuredisk-volume-tester-72jzb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.269161707s
Jun  9 17:32:47.066: INFO: Pod "azuredisk-volume-tester-72jzb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.315684315s
... skipping 2 lines ...
Jun  9 17:32:53.207: INFO: Pod "azuredisk-volume-tester-72jzb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.456682933s
Jun  9 17:32:55.256: INFO: Pod "azuredisk-volume-tester-72jzb": Phase="Pending", Reason="", readiness=false. Elapsed: 18.505301933s
Jun  9 17:32:57.302: INFO: Pod "azuredisk-volume-tester-72jzb": Phase="Pending", Reason="", readiness=false. Elapsed: 20.551859875s
Jun  9 17:32:59.350: INFO: Pod "azuredisk-volume-tester-72jzb": Phase="Pending", Reason="", readiness=false. Elapsed: 22.599259199s
Jun  9 17:33:01.396: INFO: Pod "azuredisk-volume-tester-72jzb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.645325469s
STEP: Saw pod success
Jun  9 17:33:01.396: INFO: Pod "azuredisk-volume-tester-72jzb" satisfied condition "Succeeded or Failed"
Jun  9 17:33:01.396: INFO: deleting Pod "azuredisk-8510"/"azuredisk-volume-tester-72jzb"
Jun  9 17:33:01.497: INFO: Pod azuredisk-volume-tester-72jzb has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-72jzb in namespace azuredisk-8510
STEP: validating provisioned PV
STEP: checking the PV
... skipping 56 lines ...
Jun  9 17:34:40.762: INFO: >>> kubeConfig: /root/tmp713684325/kubeconfig/kubeconfig.eastus2.json
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jun  9 17:34:40.908: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vlcl7" in namespace "azuredisk-5561" to be "Succeeded or Failed"
Jun  9 17:34:40.954: INFO: Pod "azuredisk-volume-tester-vlcl7": Phase="Pending", Reason="", readiness=false. Elapsed: 46.2558ms
Jun  9 17:34:43.000: INFO: Pod "azuredisk-volume-tester-vlcl7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.092269565s
Jun  9 17:34:45.047: INFO: Pod "azuredisk-volume-tester-vlcl7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.139246885s
Jun  9 17:34:47.093: INFO: Pod "azuredisk-volume-tester-vlcl7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.185120831s
Jun  9 17:34:49.139: INFO: Pod "azuredisk-volume-tester-vlcl7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.231503351s
Jun  9 17:34:51.186: INFO: Pod "azuredisk-volume-tester-vlcl7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.277987902s
... skipping 2 lines ...
Jun  9 17:34:57.327: INFO: Pod "azuredisk-volume-tester-vlcl7": Phase="Pending", Reason="", readiness=false. Elapsed: 16.419515017s
Jun  9 17:34:59.374: INFO: Pod "azuredisk-volume-tester-vlcl7": Phase="Pending", Reason="", readiness=false. Elapsed: 18.466802115s
Jun  9 17:35:01.421: INFO: Pod "azuredisk-volume-tester-vlcl7": Phase="Pending", Reason="", readiness=false. Elapsed: 20.513780924s
Jun  9 17:35:03.468: INFO: Pod "azuredisk-volume-tester-vlcl7": Phase="Pending", Reason="", readiness=false. Elapsed: 22.560148759s
Jun  9 17:35:05.514: INFO: Pod "azuredisk-volume-tester-vlcl7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.606280042s
STEP: Saw pod success
Jun  9 17:35:05.514: INFO: Pod "azuredisk-volume-tester-vlcl7" satisfied condition "Succeeded or Failed"
STEP: Checking Prow test resource group
2021/06/09 17:35:05 Running in Prow, converting AZURE_CREDENTIALS to AZURE_CREDENTIAL_FILE
2021/06/09 17:35:05 Reading credentials file /etc/azure-cred/credentials
STEP: Prow test resource group: kubetest-e0ffkymh
STEP: Creating external resource group: azuredisk-csi-driver-test-072d8f54-c949-11eb-b795-1e6c77c4ab3d
STEP: creating volume snapshot class with external rg azuredisk-csi-driver-test-072d8f54-c949-11eb-b795-1e6c77c4ab3d
STEP: setting up the VolumeSnapshotClass
STEP: creating a VolumeSnapshotClass
STEP: taking snapshots
STEP: creating a VolumeSnapshot for pvc-zfz7s
STEP: deploying a new pod to overwrite pv data
STEP: checking that the pod's command exits with no error
Jun  9 17:35:06.492: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-9w4f4" in namespace "azuredisk-5561" to be "Succeeded or Failed"
Jun  9 17:35:06.542: INFO: Pod "azuredisk-volume-tester-9w4f4": Phase="Pending", Reason="", readiness=false. Elapsed: 49.667978ms
Jun  9 17:35:08.589: INFO: Pod "azuredisk-volume-tester-9w4f4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.096849995s
Jun  9 17:35:10.636: INFO: Pod "azuredisk-volume-tester-9w4f4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.144030369s
Jun  9 17:35:12.687: INFO: Pod "azuredisk-volume-tester-9w4f4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.194759676s
Jun  9 17:35:14.733: INFO: Pod "azuredisk-volume-tester-9w4f4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.240963264s
Jun  9 17:35:16.781: INFO: Pod "azuredisk-volume-tester-9w4f4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.288751967s
Jun  9 17:35:18.828: INFO: Pod "azuredisk-volume-tester-9w4f4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.335909226s
Jun  9 17:35:20.876: INFO: Pod "azuredisk-volume-tester-9w4f4": Phase="Pending", Reason="", readiness=false. Elapsed: 14.383716823s
Jun  9 17:35:22.933: INFO: Pod "azuredisk-volume-tester-9w4f4": Phase="Pending", Reason="", readiness=false. Elapsed: 16.441305432s
Jun  9 17:35:24.980: INFO: Pod "azuredisk-volume-tester-9w4f4": Phase="Pending", Reason="", readiness=false. Elapsed: 18.48842969s
Jun  9 17:35:27.028: INFO: Pod "azuredisk-volume-tester-9w4f4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.535759275s
STEP: Saw pod success
Jun  9 17:35:27.028: INFO: Pod "azuredisk-volume-tester-9w4f4" satisfied condition "Succeeded or Failed"
STEP: waiting for VolumeSnapshot to be ready to use - volume-snapshot-v4hhj
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 a pod with a volume restored from the snapshot
STEP: checking that the pod's command exits with no error
Jun  9 17:35:42.231: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-nvtmx" in namespace "azuredisk-5561" to be "Succeeded or Failed"
Jun  9 17:35:42.279: INFO: Pod "azuredisk-volume-tester-nvtmx": Phase="Pending", Reason="", readiness=false. Elapsed: 47.91349ms
Jun  9 17:35:44.329: INFO: Pod "azuredisk-volume-tester-nvtmx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.098504781s
Jun  9 17:35:46.376: INFO: Pod "azuredisk-volume-tester-nvtmx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.144829729s
Jun  9 17:35:48.423: INFO: Pod "azuredisk-volume-tester-nvtmx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.192270956s
Jun  9 17:35:50.470: INFO: Pod "azuredisk-volume-tester-nvtmx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.23915668s
Jun  9 17:35:52.519: INFO: Pod "azuredisk-volume-tester-nvtmx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.287969304s
... skipping 2 lines ...
Jun  9 17:35:58.659: INFO: Pod "azuredisk-volume-tester-nvtmx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.428232411s
Jun  9 17:36:00.705: INFO: Pod "azuredisk-volume-tester-nvtmx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.474200439s
Jun  9 17:36:02.751: INFO: Pod "azuredisk-volume-tester-nvtmx": Phase="Pending", Reason="", readiness=false. Elapsed: 20.520626227s
Jun  9 17:36:04.799: INFO: Pod "azuredisk-volume-tester-nvtmx": Phase="Pending", Reason="", readiness=false. Elapsed: 22.567892979s
Jun  9 17:36:06.846: INFO: Pod "azuredisk-volume-tester-nvtmx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.615113904s
STEP: Saw pod success
Jun  9 17:36:06.846: INFO: Pod "azuredisk-volume-tester-nvtmx" satisfied condition "Succeeded or Failed"
Jun  9 17:36:06.846: INFO: deleting Pod "azuredisk-5561"/"azuredisk-volume-tester-nvtmx"
Jun  9 17:36:06.928: INFO: Pod azuredisk-volume-tester-nvtmx has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-nvtmx in namespace azuredisk-5561
STEP: validating provisioned PV
STEP: checking the PV
... skipping 67 lines ...
STEP: creating a PVC
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jun  9 17:37:46.818: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-tzwqq" in namespace "azuredisk-4376" to be "Succeeded or Failed"
Jun  9 17:37:46.878: INFO: Pod "azuredisk-volume-tester-tzwqq": Phase="Pending", Reason="", readiness=false. Elapsed: 59.896786ms
Jun  9 17:37:48.924: INFO: Pod "azuredisk-volume-tester-tzwqq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106157671s
Jun  9 17:37:50.990: INFO: Pod "azuredisk-volume-tester-tzwqq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.172306955s
Jun  9 17:37:53.041: INFO: Pod "azuredisk-volume-tester-tzwqq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.22250893s
Jun  9 17:37:55.089: INFO: Pod "azuredisk-volume-tester-tzwqq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.270605233s
Jun  9 17:37:57.136: INFO: Pod "azuredisk-volume-tester-tzwqq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.31800117s
... skipping 12 lines ...
Jun  9 17:38:23.751: INFO: Pod "azuredisk-volume-tester-tzwqq": Phase="Pending", Reason="", readiness=false. Elapsed: 36.933207279s
Jun  9 17:38:25.799: INFO: Pod "azuredisk-volume-tester-tzwqq": Phase="Pending", Reason="", readiness=false. Elapsed: 38.981000817s
Jun  9 17:38:27.846: INFO: Pod "azuredisk-volume-tester-tzwqq": Phase="Pending", Reason="", readiness=false. Elapsed: 41.02833419s
Jun  9 17:38:29.894: INFO: Pod "azuredisk-volume-tester-tzwqq": Phase="Pending", Reason="", readiness=false. Elapsed: 43.075968224s
Jun  9 17:38:31.942: INFO: Pod "azuredisk-volume-tester-tzwqq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 45.123556087s
STEP: Saw pod success
Jun  9 17:38:31.942: INFO: Pod "azuredisk-volume-tester-tzwqq" satisfied condition "Succeeded or Failed"
Jun  9 17:38:31.942: INFO: deleting Pod "azuredisk-4376"/"azuredisk-volume-tester-tzwqq"
Jun  9 17:38:31.991: INFO: Pod azuredisk-volume-tester-tzwqq has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-tzwqq in namespace azuredisk-4376
STEP: validating provisioned PV
STEP: checking the PV
... skipping 206 lines ...