This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: test: run sanity test on csi-test v5.0.0
ResultABORTED
Tests 0 failed / 23 succeeded
Started2022-09-15 02:00
Elapsed1h3m
Revisionf0a1ae2fadbe989dae0e7124885a99c0feda4995
Refs 1513

No Test Failures!


Show 23 Passed Tests

Show 36 Skipped Tests

Error lines from build-log.txt

... skipping 96 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   178k      0 --:--:-- --:--:-- --:--:--  178k
Downloading https://get.helm.sh/helm-v3.9.4-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.23.0-07f19fad13a88b859262cd701fbd4f1edcf6700f || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v1.23.0-07f19fad13a88b859262cd701fbd4f1edcf6700f not found: manifest unknown: manifest tagged by "v1.23.0-07f19fad13a88b859262cd701fbd4f1edcf6700f" 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.23.0-07f19fad13a88b859262cd701fbd4f1edcf6700f -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=07f19fad13a88b859262cd701fbd4f1edcf6700f -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2022-09-15T02:05:43Z -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 1745 lines ...
                    type: string
                type: object
                oneOf:
                - required: ["persistentVolumeClaimName"]
                - required: ["volumeSnapshotContentName"]
              volumeSnapshotClassName:
                description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.'
                type: string
            required:
            - source
            type: object
          status:
            description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.
... skipping 2 lines ...
                description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.'
                type: string
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a 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 may indicate 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. The snapshot controller will keep retrying when an error occurrs during the snapshot creation. Upon success, this error field will be cleared.
                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 the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                type: string
                description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" 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
        type: object
... skipping 60 lines ...
                    type: string
                  volumeSnapshotContentName:
                    description: volumeSnapshotContentName specifies the name of a pre-existing VolumeSnapshotContent object representing an existing volume snapshot. This field should be set if the snapshot already exists and only needs a representation in Kubernetes. This field is immutable.
                    type: string
                type: object
              volumeSnapshotClassName:
                description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.'
                type: string
            required:
            - source
            type: object
          status:
            description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.
... skipping 2 lines ...
                description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.'
                type: string
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a 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 may indicate 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. The snapshot controller will keep retrying when an error occurrs during the snapshot creation. Upon success, this error field will be cleared.
                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 the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                type: string
                description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" 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
        type: object
... skipping 254 lines ...
            description: status represents the current information of a snapshot.
            properties:
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a 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 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 last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared.
                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 will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" 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
    served: true
... skipping 108 lines ...
            description: status represents the current information of a snapshot.
            properties:
              creationTime:
                description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a 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 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 last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared.
                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 will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown.
                type: boolean
              restoreSize:
                description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" 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
    served: true
... skipping 861 lines ...
          image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.5.0"
          args:
            - "-csi-address=$(ADDRESS)"
            - "-v=2"
            - "-leader-election"
            - "--leader-election-namespace=kube-system"
            - '-handle-volume-inuse-error=false'
            - '-feature-gates=RecoverVolumeExpansionFailure=true'
            - "-timeout=240s"
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          volumeMounts:
... skipping 209 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
Sep 15 02:16:32.698: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-m8f8f" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Sep 15 02:16:32.750: INFO: Pod "azuredisk-volume-tester-m8f8f": Phase="Pending", Reason="", readiness=false. Elapsed: 52.691336ms
Sep 15 02:16:34.804: INFO: Pod "azuredisk-volume-tester-m8f8f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106072599s
Sep 15 02:16:36.858: INFO: Pod "azuredisk-volume-tester-m8f8f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.160694642s
Sep 15 02:16:38.912: INFO: Pod "azuredisk-volume-tester-m8f8f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.214299334s
Sep 15 02:16:40.967: INFO: Pod "azuredisk-volume-tester-m8f8f": Phase="Pending", Reason="", readiness=false. Elapsed: 8.269444155s
Sep 15 02:16:43.021: INFO: Pod "azuredisk-volume-tester-m8f8f": Phase="Pending", Reason="", readiness=false. Elapsed: 10.323143125s
... skipping 13 lines ...
Sep 15 02:17:11.794: INFO: Pod "azuredisk-volume-tester-m8f8f": Phase="Pending", Reason="", readiness=false. Elapsed: 39.096259435s
Sep 15 02:17:13.847: INFO: Pod "azuredisk-volume-tester-m8f8f": Phase="Pending", Reason="", readiness=false. Elapsed: 41.149809189s
Sep 15 02:17:15.902: INFO: Pod "azuredisk-volume-tester-m8f8f": Phase="Pending", Reason="", readiness=false. Elapsed: 43.204799359s
Sep 15 02:17:17.957: INFO: Pod "azuredisk-volume-tester-m8f8f": Phase="Pending", Reason="", readiness=false. Elapsed: 45.259423638s
Sep 15 02:17:20.011: INFO: Pod "azuredisk-volume-tester-m8f8f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 47.312914271s
STEP: Saw pod success
Sep 15 02:17:20.011: INFO: Pod "azuredisk-volume-tester-m8f8f" satisfied condition "Succeeded or Failed"
Sep 15 02:17:20.011: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-m8f8f"
Sep 15 02:17:20.099: INFO: Pod azuredisk-volume-tester-m8f8f has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-m8f8f in namespace azuredisk-8081
STEP: validating provisioned PV
STEP: checking the PV
... skipping 46 lines ...
Sep 15 02:17:59.074: INFO: PersistentVolumeClaim pvc-822tb found but phase is Pending instead of Bound.
Sep 15 02:18:01.127: INFO: PersistentVolumeClaim pvc-822tb found and phase=Bound (4.159242718s)
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
Sep 15 02:18:01.289: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-qwnf2" in namespace "azuredisk-2540" to be "Succeeded or Failed"
Sep 15 02:18:01.342: INFO: Pod "azuredisk-volume-tester-qwnf2": Phase="Pending", Reason="", readiness=false. Elapsed: 52.695836ms
Sep 15 02:18:03.397: INFO: Pod "azuredisk-volume-tester-qwnf2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.107342447s
Sep 15 02:18:05.452: INFO: Pod "azuredisk-volume-tester-qwnf2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.162181454s
Sep 15 02:18:07.505: INFO: Pod "azuredisk-volume-tester-qwnf2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.215915921s
Sep 15 02:18:09.559: INFO: Pod "azuredisk-volume-tester-qwnf2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.269642943s
Sep 15 02:18:11.614: INFO: Pod "azuredisk-volume-tester-qwnf2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.324537033s
Sep 15 02:18:13.667: INFO: Pod "azuredisk-volume-tester-qwnf2": Phase="Pending", Reason="", readiness=false. Elapsed: 12.378006813s
Sep 15 02:18:15.721: INFO: Pod "azuredisk-volume-tester-qwnf2": Phase="Pending", Reason="", readiness=false. Elapsed: 14.431701074s
Sep 15 02:18:17.776: INFO: Pod "azuredisk-volume-tester-qwnf2": Phase="Pending", Reason="", readiness=false. Elapsed: 16.486038791s
Sep 15 02:18:19.830: INFO: Pod "azuredisk-volume-tester-qwnf2": Phase="Pending", Reason="", readiness=false. Elapsed: 18.540626071s
Sep 15 02:18:21.885: INFO: Pod "azuredisk-volume-tester-qwnf2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 20.595452249s
STEP: Saw pod success
Sep 15 02:18:21.885: INFO: Pod "azuredisk-volume-tester-qwnf2" satisfied condition "Succeeded or Failed"
Sep 15 02:18:21.885: INFO: deleting Pod "azuredisk-2540"/"azuredisk-volume-tester-qwnf2"
Sep 15 02:18:21.940: INFO: Pod azuredisk-volume-tester-qwnf2 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-qwnf2 in namespace azuredisk-2540
Sep 15 02:18:22.001: INFO: deleting PVC "azuredisk-2540"/"pvc-822tb"
Sep 15 02:18:22.001: INFO: Deleting PersistentVolumeClaim "pvc-822tb"
... skipping 43 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
Sep 15 02:19:29.179: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-566f5" in namespace "azuredisk-4728" to be "Succeeded or Failed"
Sep 15 02:19:29.232: INFO: Pod "azuredisk-volume-tester-566f5": Phase="Pending", Reason="", readiness=false. Elapsed: 53.303657ms
Sep 15 02:19:31.287: INFO: Pod "azuredisk-volume-tester-566f5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.10791851s
Sep 15 02:19:33.344: INFO: Pod "azuredisk-volume-tester-566f5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.164673233s
Sep 15 02:19:35.398: INFO: Pod "azuredisk-volume-tester-566f5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.218764814s
Sep 15 02:19:37.452: INFO: Pod "azuredisk-volume-tester-566f5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.273312701s
Sep 15 02:19:39.507: INFO: Pod "azuredisk-volume-tester-566f5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.327626673s
... skipping 9 lines ...
Sep 15 02:20:00.052: INFO: Pod "azuredisk-volume-tester-566f5": Phase="Pending", Reason="", readiness=false. Elapsed: 30.87269927s
Sep 15 02:20:02.105: INFO: Pod "azuredisk-volume-tester-566f5": Phase="Pending", Reason="", readiness=false. Elapsed: 32.926202881s
Sep 15 02:20:04.160: INFO: Pod "azuredisk-volume-tester-566f5": Phase="Pending", Reason="", readiness=false. Elapsed: 34.981011311s
Sep 15 02:20:06.213: INFO: Pod "azuredisk-volume-tester-566f5": Phase="Pending", Reason="", readiness=false. Elapsed: 37.033711213s
Sep 15 02:20:08.268: INFO: Pod "azuredisk-volume-tester-566f5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.089222364s
STEP: Saw pod success
Sep 15 02:20:08.268: INFO: Pod "azuredisk-volume-tester-566f5" satisfied condition "Succeeded or Failed"
Sep 15 02:20:08.268: INFO: deleting Pod "azuredisk-4728"/"azuredisk-volume-tester-566f5"
Sep 15 02:20:08.355: INFO: Pod azuredisk-volume-tester-566f5 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-566f5 in namespace azuredisk-4728
STEP: validating provisioned PV
STEP: checking the PV
... skipping 42 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
Sep 15 02:21:12.607: INFO: deleting Pod "azuredisk-5466"/"azuredisk-volume-tester-pd2cq"
Sep 15 02:21:12.663: INFO: Error getting logs for pod azuredisk-volume-tester-pd2cq: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-pd2cq)
STEP: Deleting pod azuredisk-volume-tester-pd2cq in namespace azuredisk-5466
STEP: validating provisioned PV
STEP: checking the PV
Sep 15 02:21:12.827: INFO: deleting PVC "azuredisk-5466"/"pvc-8jxk7"
Sep 15 02:21:12.827: INFO: Deleting PersistentVolumeClaim "pvc-8jxk7"
STEP: waiting for claim's PV "pvc-e0fcdbb0-19df-4979-bc30-5301cba5aaba" to be deleted
... skipping 44 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
Sep 15 02:22:30.287: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-m7h2l" in namespace "azuredisk-2790" to be "Succeeded or Failed"
Sep 15 02:22:30.341: INFO: Pod "azuredisk-volume-tester-m7h2l": Phase="Pending", Reason="", readiness=false. Elapsed: 53.704455ms
Sep 15 02:22:32.395: INFO: Pod "azuredisk-volume-tester-m7h2l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.107983507s
Sep 15 02:22:34.456: INFO: Pod "azuredisk-volume-tester-m7h2l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.168364832s
Sep 15 02:22:36.510: INFO: Pod "azuredisk-volume-tester-m7h2l": Phase="Pending", Reason="", readiness=false. Elapsed: 6.222103153s
Sep 15 02:22:38.565: INFO: Pod "azuredisk-volume-tester-m7h2l": Phase="Pending", Reason="", readiness=false. Elapsed: 8.277605932s
Sep 15 02:22:40.620: INFO: Pod "azuredisk-volume-tester-m7h2l": Phase="Pending", Reason="", readiness=false. Elapsed: 10.33249839s
... skipping 2 lines ...
Sep 15 02:22:46.785: INFO: Pod "azuredisk-volume-tester-m7h2l": Phase="Pending", Reason="", readiness=false. Elapsed: 16.497772483s
Sep 15 02:22:48.841: INFO: Pod "azuredisk-volume-tester-m7h2l": Phase="Pending", Reason="", readiness=false. Elapsed: 18.553485056s
Sep 15 02:22:50.895: INFO: Pod "azuredisk-volume-tester-m7h2l": Phase="Pending", Reason="", readiness=false. Elapsed: 20.607987685s
Sep 15 02:22:52.949: INFO: Pod "azuredisk-volume-tester-m7h2l": Phase="Pending", Reason="", readiness=false. Elapsed: 22.661910176s
Sep 15 02:22:55.005: INFO: Pod "azuredisk-volume-tester-m7h2l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.717234802s
STEP: Saw pod success
Sep 15 02:22:55.005: INFO: Pod "azuredisk-volume-tester-m7h2l" satisfied condition "Succeeded or Failed"
Sep 15 02:22:55.005: INFO: deleting Pod "azuredisk-2790"/"azuredisk-volume-tester-m7h2l"
Sep 15 02:22:55.085: INFO: Pod azuredisk-volume-tester-m7h2l has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-m7h2l in namespace azuredisk-2790
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
Sep 15 02:23:32.411: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-jq76l" in namespace "azuredisk-5356" to be "Error status code"
Sep 15 02:23:32.467: INFO: Pod "azuredisk-volume-tester-jq76l": Phase="Pending", Reason="", readiness=false. Elapsed: 55.931025ms
Sep 15 02:23:34.522: INFO: Pod "azuredisk-volume-tester-jq76l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.110807691s
Sep 15 02:23:36.577: INFO: Pod "azuredisk-volume-tester-jq76l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.165067862s
Sep 15 02:23:38.633: INFO: Pod "azuredisk-volume-tester-jq76l": Phase="Pending", Reason="", readiness=false. Elapsed: 6.221438491s
Sep 15 02:23:40.689: INFO: Pod "azuredisk-volume-tester-jq76l": Phase="Pending", Reason="", readiness=false. Elapsed: 8.27776628s
Sep 15 02:23:42.747: INFO: Pod "azuredisk-volume-tester-jq76l": Phase="Pending", Reason="", readiness=false. Elapsed: 10.335285648s
... skipping 23 lines ...
Sep 15 02:24:32.082: INFO: Pod "azuredisk-volume-tester-jq76l": Phase="Pending", Reason="", readiness=false. Elapsed: 59.670621079s
Sep 15 02:24:34.138: INFO: Pod "azuredisk-volume-tester-jq76l": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.726581398s
Sep 15 02:24:36.193: INFO: Pod "azuredisk-volume-tester-jq76l": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.781663372s
Sep 15 02:24:38.250: INFO: Pod "azuredisk-volume-tester-jq76l": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.838184201s
Sep 15 02:24:40.304: INFO: Pod "azuredisk-volume-tester-jq76l": Phase="Pending", Reason="", readiness=false. Elapsed: 1m7.892284293s
Sep 15 02:24:42.360: INFO: Pod "azuredisk-volume-tester-jq76l": Phase="Pending", Reason="", readiness=false. Elapsed: 1m9.94816233s
Sep 15 02:24:44.416: INFO: Pod "azuredisk-volume-tester-jq76l": Phase="Failed", Reason="", readiness=false. Elapsed: 1m12.004926394s
STEP: Saw pod failure
Sep 15 02:24:44.416: INFO: Pod "azuredisk-volume-tester-jq76l" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Sep 15 02:24:44.496: INFO: deleting Pod "azuredisk-5356"/"azuredisk-volume-tester-jq76l"
Sep 15 02:24:44.552: INFO: Pod azuredisk-volume-tester-jq76l has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-jq76l in namespace azuredisk-5356
STEP: validating provisioned PV
... skipping 338 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
Sep 15 02:32:40.087: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-mhzqq" in namespace "azuredisk-4376" to be "Succeeded or Failed"
Sep 15 02:32:40.140: INFO: Pod "azuredisk-volume-tester-mhzqq": Phase="Pending", Reason="", readiness=false. Elapsed: 52.109333ms
Sep 15 02:32:42.194: INFO: Pod "azuredisk-volume-tester-mhzqq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106137382s
Sep 15 02:32:44.249: INFO: Pod "azuredisk-volume-tester-mhzqq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.161026572s
Sep 15 02:32:46.303: INFO: Pod "azuredisk-volume-tester-mhzqq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.215976429s
Sep 15 02:32:48.358: INFO: Pod "azuredisk-volume-tester-mhzqq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.270274033s
Sep 15 02:32:50.411: INFO: Pod "azuredisk-volume-tester-mhzqq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.323377689s
Sep 15 02:32:52.464: INFO: Pod "azuredisk-volume-tester-mhzqq": Phase="Pending", Reason="", readiness=false. Elapsed: 12.376438749s
Sep 15 02:32:54.517: INFO: Pod "azuredisk-volume-tester-mhzqq": Phase="Pending", Reason="", readiness=false. Elapsed: 14.429893041s
Sep 15 02:32:56.571: INFO: Pod "azuredisk-volume-tester-mhzqq": Phase="Pending", Reason="", readiness=false. Elapsed: 16.4834011s
Sep 15 02:32:58.624: INFO: Pod "azuredisk-volume-tester-mhzqq": Phase="Pending", Reason="", readiness=false. Elapsed: 18.536907109s
Sep 15 02:33:00.678: INFO: Pod "azuredisk-volume-tester-mhzqq": Phase="Pending", Reason="", readiness=false. Elapsed: 20.590690793s
Sep 15 02:33:02.732: INFO: Pod "azuredisk-volume-tester-mhzqq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.644628735s
STEP: Saw pod success
Sep 15 02:33:02.732: INFO: Pod "azuredisk-volume-tester-mhzqq" satisfied condition "Succeeded or Failed"
STEP: sleep 5s and then clone volume
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
Sep 15 02:33:07.953: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-v9lwm" in namespace "azuredisk-4376" to be "Succeeded or Failed"
Sep 15 02:33:08.006: INFO: Pod "azuredisk-volume-tester-v9lwm": Phase="Pending", Reason="", readiness=false. Elapsed: 52.704127ms
Sep 15 02:33:10.059: INFO: Pod "azuredisk-volume-tester-v9lwm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106536181s
Sep 15 02:33:12.117: INFO: Pod "azuredisk-volume-tester-v9lwm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.164077827s
Sep 15 02:33:14.172: INFO: Pod "azuredisk-volume-tester-v9lwm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.218893371s
Sep 15 02:33:16.228: INFO: Pod "azuredisk-volume-tester-v9lwm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.275088023s
Sep 15 02:33:18.282: INFO: Pod "azuredisk-volume-tester-v9lwm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.329495122s
... skipping 9 lines ...
Sep 15 02:33:38.821: INFO: Pod "azuredisk-volume-tester-v9lwm": Phase="Pending", Reason="", readiness=false. Elapsed: 30.868458206s
Sep 15 02:33:40.876: INFO: Pod "azuredisk-volume-tester-v9lwm": Phase="Pending", Reason="", readiness=false. Elapsed: 32.923193462s
Sep 15 02:33:42.931: INFO: Pod "azuredisk-volume-tester-v9lwm": Phase="Pending", Reason="", readiness=false. Elapsed: 34.978399531s
Sep 15 02:33:44.985: INFO: Pod "azuredisk-volume-tester-v9lwm": Phase="Pending", Reason="", readiness=false. Elapsed: 37.03215018s
Sep 15 02:33:47.040: INFO: Pod "azuredisk-volume-tester-v9lwm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.087069347s
STEP: Saw pod success
Sep 15 02:33:47.040: INFO: Pod "azuredisk-volume-tester-v9lwm" satisfied condition "Succeeded or Failed"
Sep 15 02:33:47.040: INFO: deleting Pod "azuredisk-4376"/"azuredisk-volume-tester-v9lwm"
Sep 15 02:33:47.117: INFO: Pod azuredisk-volume-tester-v9lwm has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-v9lwm in namespace azuredisk-4376
STEP: validating provisioned PV
STEP: checking the PV
... skipping 52 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
Sep 15 02:34:29.549: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-dwcjj" in namespace "azuredisk-7996" to be "Succeeded or Failed"
Sep 15 02:34:29.602: INFO: Pod "azuredisk-volume-tester-dwcjj": Phase="Pending", Reason="", readiness=false. Elapsed: 53.021882ms
Sep 15 02:34:31.657: INFO: Pod "azuredisk-volume-tester-dwcjj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.108383083s
Sep 15 02:34:33.711: INFO: Pod "azuredisk-volume-tester-dwcjj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.162096219s
Sep 15 02:34:35.765: INFO: Pod "azuredisk-volume-tester-dwcjj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.216457912s
Sep 15 02:34:37.820: INFO: Pod "azuredisk-volume-tester-dwcjj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.270963091s
Sep 15 02:34:39.875: INFO: Pod "azuredisk-volume-tester-dwcjj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.325647198s
Sep 15 02:34:41.929: INFO: Pod "azuredisk-volume-tester-dwcjj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.38020799s
Sep 15 02:34:43.984: INFO: Pod "azuredisk-volume-tester-dwcjj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.434843761s
Sep 15 02:34:46.039: INFO: Pod "azuredisk-volume-tester-dwcjj": Phase="Pending", Reason="", readiness=false. Elapsed: 16.489830905s
Sep 15 02:34:48.094: INFO: Pod "azuredisk-volume-tester-dwcjj": Phase="Pending", Reason="", readiness=false. Elapsed: 18.544514926s
Sep 15 02:34:50.149: INFO: Pod "azuredisk-volume-tester-dwcjj": Phase="Pending", Reason="", readiness=false. Elapsed: 20.600137459s
Sep 15 02:34:52.203: INFO: Pod "azuredisk-volume-tester-dwcjj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.654230902s
STEP: Saw pod success
Sep 15 02:34:52.203: INFO: Pod "azuredisk-volume-tester-dwcjj" satisfied condition "Succeeded or Failed"
STEP: sleep 5s and then clone volume
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
Sep 15 02:34:57.422: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-hvtlk" in namespace "azuredisk-7996" to be "Succeeded or Failed"
Sep 15 02:34:57.475: INFO: Pod "azuredisk-volume-tester-hvtlk": Phase="Pending", Reason="", readiness=false. Elapsed: 52.61426ms
Sep 15 02:34:59.529: INFO: Pod "azuredisk-volume-tester-hvtlk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106199592s
Sep 15 02:35:01.583: INFO: Pod "azuredisk-volume-tester-hvtlk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.160963233s
Sep 15 02:35:03.638: INFO: Pod "azuredisk-volume-tester-hvtlk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.214990105s
Sep 15 02:35:05.693: INFO: Pod "azuredisk-volume-tester-hvtlk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.270143466s
Sep 15 02:35:07.746: INFO: Pod "azuredisk-volume-tester-hvtlk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.323583443s
... skipping 9 lines ...
Sep 15 02:35:28.292: INFO: Pod "azuredisk-volume-tester-hvtlk": Phase="Pending", Reason="", readiness=false. Elapsed: 30.869270613s
Sep 15 02:35:30.346: INFO: Pod "azuredisk-volume-tester-hvtlk": Phase="Pending", Reason="", readiness=false. Elapsed: 32.923271534s
Sep 15 02:35:32.400: INFO: Pod "azuredisk-volume-tester-hvtlk": Phase="Pending", Reason="", readiness=false. Elapsed: 34.9779304s
Sep 15 02:35:34.458: INFO: Pod "azuredisk-volume-tester-hvtlk": Phase="Pending", Reason="", readiness=false. Elapsed: 37.035271331s
Sep 15 02:35:36.512: INFO: Pod "azuredisk-volume-tester-hvtlk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.089943172s
STEP: Saw pod success
Sep 15 02:35:36.513: INFO: Pod "azuredisk-volume-tester-hvtlk" satisfied condition "Succeeded or Failed"
Sep 15 02:35:36.513: INFO: deleting Pod "azuredisk-7996"/"azuredisk-volume-tester-hvtlk"
Sep 15 02:35:36.574: INFO: Pod azuredisk-volume-tester-hvtlk has the following logs: 20.0G

STEP: Deleting pod azuredisk-volume-tester-hvtlk in namespace azuredisk-7996
STEP: validating provisioned PV
STEP: checking the PV
... skipping 62 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
Sep 15 02:36:19.204: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-b26wz" in namespace "azuredisk-59" to be "Succeeded or Failed"
Sep 15 02:36:19.257: INFO: Pod "azuredisk-volume-tester-b26wz": Phase="Pending", Reason="", readiness=false. Elapsed: 52.549575ms
Sep 15 02:36:21.310: INFO: Pod "azuredisk-volume-tester-b26wz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.105977914s
Sep 15 02:36:23.364: INFO: Pod "azuredisk-volume-tester-b26wz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.160011165s
Sep 15 02:36:25.418: INFO: Pod "azuredisk-volume-tester-b26wz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.213853352s
Sep 15 02:36:27.472: INFO: Pod "azuredisk-volume-tester-b26wz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.268130299s
Sep 15 02:36:29.528: INFO: Pod "azuredisk-volume-tester-b26wz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.32318008s
... skipping 9 lines ...
Sep 15 02:36:50.071: INFO: Pod "azuredisk-volume-tester-b26wz": Phase="Pending", Reason="", readiness=false. Elapsed: 30.866969739s
Sep 15 02:36:52.126: INFO: Pod "azuredisk-volume-tester-b26wz": Phase="Pending", Reason="", readiness=false. Elapsed: 32.921787778s
Sep 15 02:36:54.180: INFO: Pod "azuredisk-volume-tester-b26wz": Phase="Pending", Reason="", readiness=false. Elapsed: 34.975473058s
Sep 15 02:36:56.235: INFO: Pod "azuredisk-volume-tester-b26wz": Phase="Pending", Reason="", readiness=false. Elapsed: 37.030289214s
Sep 15 02:36:58.290: INFO: Pod "azuredisk-volume-tester-b26wz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.085288628s
STEP: Saw pod success
Sep 15 02:36:58.290: INFO: Pod "azuredisk-volume-tester-b26wz" satisfied condition "Succeeded or Failed"
Sep 15 02:36:58.290: INFO: deleting Pod "azuredisk-59"/"azuredisk-volume-tester-b26wz"
Sep 15 02:36:58.356: INFO: Pod azuredisk-volume-tester-b26wz has the following logs: hello world
hello world
hello world

STEP: Deleting pod azuredisk-volume-tester-b26wz in namespace azuredisk-59
... skipping 74 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
Sep 15 02:38:16.514: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-zq9tj" in namespace "azuredisk-2546" to be "Succeeded or Failed"
Sep 15 02:38:16.568: INFO: Pod "azuredisk-volume-tester-zq9tj": Phase="Pending", Reason="", readiness=false. Elapsed: 53.264787ms
Sep 15 02:38:18.621: INFO: Pod "azuredisk-volume-tester-zq9tj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106889992s
Sep 15 02:38:20.675: INFO: Pod "azuredisk-volume-tester-zq9tj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.160411098s
Sep 15 02:38:22.729: INFO: Pod "azuredisk-volume-tester-zq9tj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.214594109s
Sep 15 02:38:24.785: INFO: Pod "azuredisk-volume-tester-zq9tj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.270407766s
Sep 15 02:38:26.840: INFO: Pod "azuredisk-volume-tester-zq9tj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.325659046s
... skipping 9 lines ...
Sep 15 02:38:47.391: INFO: Pod "azuredisk-volume-tester-zq9tj": Phase="Pending", Reason="", readiness=false. Elapsed: 30.87660952s
Sep 15 02:38:49.445: INFO: Pod "azuredisk-volume-tester-zq9tj": Phase="Pending", Reason="", readiness=false. Elapsed: 32.930986832s
Sep 15 02:38:51.500: INFO: Pod "azuredisk-volume-tester-zq9tj": Phase="Pending", Reason="", readiness=false. Elapsed: 34.985346335s
Sep 15 02:38:53.554: INFO: Pod "azuredisk-volume-tester-zq9tj": Phase="Pending", Reason="", readiness=false. Elapsed: 37.03968758s
Sep 15 02:38:55.609: INFO: Pod "azuredisk-volume-tester-zq9tj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.094410723s
STEP: Saw pod success
Sep 15 02:38:55.609: INFO: Pod "azuredisk-volume-tester-zq9tj" satisfied condition "Succeeded or Failed"
Sep 15 02:38:55.609: INFO: deleting Pod "azuredisk-2546"/"azuredisk-volume-tester-zq9tj"
Sep 15 02:38:55.686: INFO: Pod azuredisk-volume-tester-zq9tj has the following logs: 100+0 records in
100+0 records out
104857600 bytes (100.0MB) copied, 0.081465 seconds, 1.2GB/s
hello world

... skipping 58 lines ...
Sep 15 02:40:08.216: INFO: >>> kubeConfig: /root/tmp2646039615/kubeconfig/kubeconfig.westus2.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
Sep 15 02:40:08.382: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-r4hdm" in namespace "azuredisk-1598" to be "Succeeded or Failed"
Sep 15 02:40:08.436: INFO: Pod "azuredisk-volume-tester-r4hdm": Phase="Pending", Reason="", readiness=false. Elapsed: 53.073156ms
Sep 15 02:40:10.489: INFO: Pod "azuredisk-volume-tester-r4hdm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106626121s
Sep 15 02:40:12.543: INFO: Pod "azuredisk-volume-tester-r4hdm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.160122072s
Sep 15 02:40:14.598: INFO: Pod "azuredisk-volume-tester-r4hdm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.215092294s
Sep 15 02:40:16.655: INFO: Pod "azuredisk-volume-tester-r4hdm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.272411085s
Sep 15 02:40:18.709: INFO: Pod "azuredisk-volume-tester-r4hdm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.326317044s
Sep 15 02:40:20.763: INFO: Pod "azuredisk-volume-tester-r4hdm": Phase="Pending", Reason="", readiness=false. Elapsed: 12.380856517s
Sep 15 02:40:22.817: INFO: Pod "azuredisk-volume-tester-r4hdm": Phase="Pending", Reason="", readiness=false. Elapsed: 14.434099706s
Sep 15 02:40:24.871: INFO: Pod "azuredisk-volume-tester-r4hdm": Phase="Pending", Reason="", readiness=false. Elapsed: 16.488246816s
Sep 15 02:40:26.925: INFO: Pod "azuredisk-volume-tester-r4hdm": Phase="Pending", Reason="", readiness=false. Elapsed: 18.542522837s
Sep 15 02:40:28.979: INFO: Pod "azuredisk-volume-tester-r4hdm": Phase="Pending", Reason="", readiness=false. Elapsed: 20.596271616s
Sep 15 02:40:31.032: INFO: Pod "azuredisk-volume-tester-r4hdm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.650027426s
STEP: Saw pod success
Sep 15 02:40:31.033: INFO: Pod "azuredisk-volume-tester-r4hdm" satisfied condition "Succeeded or Failed"
STEP: Checking Prow test resource group
2022/09/15 02:40:31 Running in Prow, converting AZURE_CREDENTIALS to AZURE_CREDENTIAL_FILE
2022/09/15 02:40:31 Reading credentials file /etc/azure-cred/credentials
STEP: Prow test resource group: kubetest-ubptdq41
STEP: Creating external resource group: azuredisk-csi-driver-test-c3f3e090-349f-11ed-bbd5-ae2d74c9111b
STEP: creating volume snapshot class with external rg azuredisk-csi-driver-test-c3f3e090-349f-11ed-bbd5-ae2d74c9111b
... 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
Sep 15 02:40:47.759: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-flzkz" in namespace "azuredisk-1598" to be "Succeeded or Failed"
Sep 15 02:40:47.812: INFO: Pod "azuredisk-volume-tester-flzkz": Phase="Pending", Reason="", readiness=false. Elapsed: 52.467983ms
Sep 15 02:40:49.868: INFO: Pod "azuredisk-volume-tester-flzkz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.107920339s
Sep 15 02:40:51.922: INFO: Pod "azuredisk-volume-tester-flzkz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.162691605s
Sep 15 02:40:53.977: INFO: Pod "azuredisk-volume-tester-flzkz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.217670399s
Sep 15 02:40:56.031: INFO: Pod "azuredisk-volume-tester-flzkz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.271610485s
Sep 15 02:40:58.086: INFO: Pod "azuredisk-volume-tester-flzkz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.326010671s
... skipping 9 lines ...
Sep 15 02:41:18.642: INFO: Pod "azuredisk-volume-tester-flzkz": Phase="Pending", Reason="", readiness=false. Elapsed: 30.88257209s
Sep 15 02:41:20.697: INFO: Pod "azuredisk-volume-tester-flzkz": Phase="Pending", Reason="", readiness=false. Elapsed: 32.937471567s
Sep 15 02:41:22.751: INFO: Pod "azuredisk-volume-tester-flzkz": Phase="Pending", Reason="", readiness=false. Elapsed: 34.99150294s
Sep 15 02:41:24.806: INFO: Pod "azuredisk-volume-tester-flzkz": Phase="Pending", Reason="", readiness=false. Elapsed: 37.046143478s
Sep 15 02:41:26.861: INFO: Pod "azuredisk-volume-tester-flzkz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.101247898s
STEP: Saw pod success
Sep 15 02:41:26.862: INFO: Pod "azuredisk-volume-tester-flzkz" satisfied condition "Succeeded or Failed"
Sep 15 02:41:26.863: INFO: deleting Pod "azuredisk-1598"/"azuredisk-volume-tester-flzkz"
Sep 15 02:41:26.946: INFO: Pod azuredisk-volume-tester-flzkz has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-flzkz in namespace azuredisk-1598
STEP: validating provisioned PV
STEP: checking the PV
... skipping 55 lines ...
Sep 15 02:42:25.987: INFO: >>> kubeConfig: /root/tmp2646039615/kubeconfig/kubeconfig.westus2.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
Sep 15 02:42:26.151: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-8k7sf" in namespace "azuredisk-3410" to be "Succeeded or Failed"
Sep 15 02:42:26.204: INFO: Pod "azuredisk-volume-tester-8k7sf": Phase="Pending", Reason="", readiness=false. Elapsed: 53.086368ms
Sep 15 02:42:28.259: INFO: Pod "azuredisk-volume-tester-8k7sf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.108483789s
Sep 15 02:42:30.317: INFO: Pod "azuredisk-volume-tester-8k7sf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.165977577s
Sep 15 02:42:32.372: INFO: Pod "azuredisk-volume-tester-8k7sf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.220642892s
Sep 15 02:42:34.426: INFO: Pod "azuredisk-volume-tester-8k7sf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.27502966s
Sep 15 02:42:36.481: INFO: Pod "azuredisk-volume-tester-8k7sf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.329798655s
... skipping 2 lines ...
Sep 15 02:42:42.643: INFO: Pod "azuredisk-volume-tester-8k7sf": Phase="Pending", Reason="", readiness=false. Elapsed: 16.492171226s
Sep 15 02:42:44.697: INFO: Pod "azuredisk-volume-tester-8k7sf": Phase="Pending", Reason="", readiness=false. Elapsed: 18.545561653s
Sep 15 02:42:46.752: INFO: Pod "azuredisk-volume-tester-8k7sf": Phase="Pending", Reason="", readiness=false. Elapsed: 20.601442463s
Sep 15 02:42:48.807: INFO: Pod "azuredisk-volume-tester-8k7sf": Phase="Pending", Reason="", readiness=false. Elapsed: 22.655836821s
Sep 15 02:42:50.861: INFO: Pod "azuredisk-volume-tester-8k7sf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.709630815s
STEP: Saw pod success
Sep 15 02:42:50.861: INFO: Pod "azuredisk-volume-tester-8k7sf" satisfied condition "Succeeded or Failed"
STEP: Checking Prow test resource group
2022/09/15 02:42:50 Running in Prow, converting AZURE_CREDENTIALS to AZURE_CREDENTIAL_FILE
2022/09/15 02:42:50 Reading credentials file /etc/azure-cred/credentials
STEP: Prow test resource group: kubetest-ubptdq41
STEP: Creating external resource group: azuredisk-csi-driver-test-174beee6-34a0-11ed-bbd5-ae2d74c9111b
STEP: creating volume snapshot class with external rg azuredisk-csi-driver-test-174beee6-34a0-11ed-bbd5-ae2d74c9111b
STEP: setting up the VolumeSnapshotClass
STEP: creating a VolumeSnapshotClass
STEP: taking snapshots
STEP: creating a VolumeSnapshot for pvc-dn5wv
STEP: deploying a new pod to overwrite pv data
STEP: checking that the pod's command exits with no error
Sep 15 02:42:51.982: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-sfj5n" in namespace "azuredisk-3410" to be "Succeeded or Failed"
Sep 15 02:42:52.034: INFO: Pod "azuredisk-volume-tester-sfj5n": Phase="Pending", Reason="", readiness=false. Elapsed: 52.194379ms
Sep 15 02:42:54.089: INFO: Pod "azuredisk-volume-tester-sfj5n": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106852522s
Sep 15 02:42:56.142: INFO: Pod "azuredisk-volume-tester-sfj5n": Phase="Pending", Reason="", readiness=false. Elapsed: 4.16028615s
Sep 15 02:42:58.198: INFO: Pod "azuredisk-volume-tester-sfj5n": Phase="Pending", Reason="", readiness=false. Elapsed: 6.215800935s
Sep 15 02:43:00.252: INFO: Pod "azuredisk-volume-tester-sfj5n": Phase="Pending", Reason="", readiness=false. Elapsed: 8.269576025s
Sep 15 02:43:02.306: INFO: Pod "azuredisk-volume-tester-sfj5n": Phase="Pending", Reason="", readiness=false. Elapsed: 10.324389556s
... skipping 23 lines ...
Sep 15 02:43:51.613: INFO: Pod "azuredisk-volume-tester-sfj5n": Phase="Pending", Reason="", readiness=false. Elapsed: 59.630842462s
Sep 15 02:43:53.667: INFO: Pod "azuredisk-volume-tester-sfj5n": Phase="Pending", Reason="", readiness=false. Elapsed: 1m1.685389945s
Sep 15 02:43:55.723: INFO: Pod "azuredisk-volume-tester-sfj5n": Phase="Pending", Reason="", readiness=false. Elapsed: 1m3.74056931s
Sep 15 02:43:57.777: INFO: Pod "azuredisk-volume-tester-sfj5n": Phase="Pending", Reason="", readiness=false. Elapsed: 1m5.794634785s
Sep 15 02:43:59.832: INFO: Pod "azuredisk-volume-tester-sfj5n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m7.849910633s
STEP: Saw pod success
Sep 15 02:43:59.832: INFO: Pod "azuredisk-volume-tester-sfj5n" satisfied condition "Succeeded or Failed"
STEP: waiting for VolumeSnapshot to be ready to use - volume-snapshot-b8lbq
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
Sep 15 02:44:15.063: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-c2jmj" in namespace "azuredisk-3410" to be "Succeeded or Failed"
Sep 15 02:44:15.116: INFO: Pod "azuredisk-volume-tester-c2jmj": Phase="Pending", Reason="", readiness=false. Elapsed: 52.517566ms
Sep 15 02:44:17.171: INFO: Pod "azuredisk-volume-tester-c2jmj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.107380744s
Sep 15 02:44:19.225: INFO: Pod "azuredisk-volume-tester-c2jmj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.161860894s
Sep 15 02:44:21.280: INFO: Pod "azuredisk-volume-tester-c2jmj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.216993898s
Sep 15 02:44:23.334: INFO: Pod "azuredisk-volume-tester-c2jmj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.270995058s
Sep 15 02:44:25.390: INFO: Pod "azuredisk-volume-tester-c2jmj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.326342006s
... skipping 9 lines ...
Sep 15 02:44:45.935: INFO: Pod "azuredisk-volume-tester-c2jmj": Phase="Pending", Reason="", readiness=false. Elapsed: 30.872219264s
Sep 15 02:44:47.990: INFO: Pod "azuredisk-volume-tester-c2jmj": Phase="Pending", Reason="", readiness=false. Elapsed: 32.926933803s
Sep 15 02:44:50.044: INFO: Pod "azuredisk-volume-tester-c2jmj": Phase="Pending", Reason="", readiness=false. Elapsed: 34.980777035s
Sep 15 02:44:52.100: INFO: Pod "azuredisk-volume-tester-c2jmj": Phase="Pending", Reason="", readiness=false. Elapsed: 37.036638343s
Sep 15 02:44:54.156: INFO: Pod "azuredisk-volume-tester-c2jmj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.092638321s
STEP: Saw pod success
Sep 15 02:44:54.156: INFO: Pod "azuredisk-volume-tester-c2jmj" satisfied condition "Succeeded or Failed"
Sep 15 02:44:54.156: INFO: deleting Pod "azuredisk-3410"/"azuredisk-volume-tester-c2jmj"
Sep 15 02:44:54.236: INFO: Pod azuredisk-volume-tester-c2jmj has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-c2jmj in namespace azuredisk-3410
STEP: validating provisioned PV
STEP: checking the PV
... skipping 66 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
Sep 15 02:46:54.368: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-78q82" in namespace "azuredisk-8582" to be "Succeeded or Failed"
Sep 15 02:46:54.421: INFO: Pod "azuredisk-volume-tester-78q82": Phase="Pending", Reason="", readiness=false. Elapsed: 52.675582ms
Sep 15 02:46:56.475: INFO: Pod "azuredisk-volume-tester-78q82": Phase="Pending", Reason="", readiness=false. Elapsed: 2.106907885s
Sep 15 02:46:58.530: INFO: Pod "azuredisk-volume-tester-78q82": Phase="Pending", Reason="", readiness=false. Elapsed: 4.162184884s
Sep 15 02:47:00.586: INFO: Pod "azuredisk-volume-tester-78q82": Phase="Pending", Reason="", readiness=false. Elapsed: 6.21732718s
Sep 15 02:47:02.640: INFO: Pod "azuredisk-volume-tester-78q82": Phase="Pending", Reason="", readiness=false. Elapsed: 8.272252634s
Sep 15 02:47:04.696: INFO: Pod "azuredisk-volume-tester-78q82": Phase="Pending", Reason="", readiness=false. Elapsed: 10.327926706s
... skipping 9 lines ...
Sep 15 02:47:25.251: INFO: Pod "azuredisk-volume-tester-78q82": Phase="Pending", Reason="", readiness=false. Elapsed: 30.882298047s
Sep 15 02:47:27.306: INFO: Pod "azuredisk-volume-tester-78q82": Phase="Pending", Reason="", readiness=false. Elapsed: 32.937712242s
Sep 15 02:47:29.360: INFO: Pod "azuredisk-volume-tester-78q82": Phase="Pending", Reason="", readiness=false. Elapsed: 34.991912944s
Sep 15 02:47:31.415: INFO: Pod "azuredisk-volume-tester-78q82": Phase="Pending", Reason="", readiness=false. Elapsed: 37.046529535s
Sep 15 02:47:33.470: INFO: Pod "azuredisk-volume-tester-78q82": Phase="Succeeded", Reason="", readiness=false. Elapsed: 39.102105223s
STEP: Saw pod success
Sep 15 02:47:33.470: INFO: Pod "azuredisk-volume-tester-78q82" satisfied condition "Succeeded or Failed"
Sep 15 02:47:33.470: INFO: deleting Pod "azuredisk-8582"/"azuredisk-volume-tester-78q82"
Sep 15 02:47:33.533: INFO: Pod azuredisk-volume-tester-78q82 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-78q82 in namespace azuredisk-8582
STEP: validating provisioned PV
STEP: checking the PV
... skipping 321 lines ...