This job view page is being replaced by Spyglass soon. Check out the new job view.
PRzmyzheng: Draft PR to test VMSSFlex-CSI integration
ResultABORTED
Tests 0 failed / 13 succeeded
Started2022-09-14 00:51
Elapsed38m46s
Revision66bd2c4682a3e986d488777037b23bffd8b2219a
Refs 1512

No Test Failures!


Show 13 Passed Tests

Show 46 Skipped Tests

Error lines from build-log.txt

... skipping 95 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   162k      0 --:--:-- --:--:-- --:--:--  162k
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-e6ae87d70ab5eba40431d3d3f3f6a61280f4f9e5 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v1.23.0-e6ae87d70ab5eba40431d3d3f3f6a61280f4f9e5 not found: manifest unknown: manifest tagged by "v1.23.0-e6ae87d70ab5eba40431d3d3f3f6a61280f4f9e5" 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-e6ae87d70ab5eba40431d3d3f3f6a61280f4f9e5 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=e6ae87d70ab5eba40431d3d3f3f6a61280f4f9e5 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2022-09-14T00:57:21Z -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 1785 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 208 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 14 01:07:31.801: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-jzn66" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Sep 14 01:07:31.838: INFO: Pod "azuredisk-volume-tester-jzn66": Phase="Pending", Reason="", readiness=false. Elapsed: 36.692037ms
Sep 14 01:07:33.876: INFO: Pod "azuredisk-volume-tester-jzn66": Phase="Pending", Reason="", readiness=false. Elapsed: 2.075144313s
Sep 14 01:07:35.914: INFO: Pod "azuredisk-volume-tester-jzn66": Phase="Pending", Reason="", readiness=false. Elapsed: 4.11360433s
Sep 14 01:07:37.952: INFO: Pod "azuredisk-volume-tester-jzn66": Phase="Pending", Reason="", readiness=false. Elapsed: 6.151408851s
Sep 14 01:07:39.991: INFO: Pod "azuredisk-volume-tester-jzn66": Phase="Pending", Reason="", readiness=false. Elapsed: 8.189939659s
Sep 14 01:07:42.029: INFO: Pod "azuredisk-volume-tester-jzn66": Phase="Pending", Reason="", readiness=false. Elapsed: 10.227676843s
... skipping 4 lines ...
Sep 14 01:07:52.221: INFO: Pod "azuredisk-volume-tester-jzn66": Phase="Pending", Reason="", readiness=false. Elapsed: 20.420404586s
Sep 14 01:07:54.259: INFO: Pod "azuredisk-volume-tester-jzn66": Phase="Pending", Reason="", readiness=false. Elapsed: 22.458505266s
Sep 14 01:07:56.297: INFO: Pod "azuredisk-volume-tester-jzn66": Phase="Pending", Reason="", readiness=false. Elapsed: 24.496591175s
Sep 14 01:07:58.336: INFO: Pod "azuredisk-volume-tester-jzn66": Phase="Pending", Reason="", readiness=false. Elapsed: 26.535157281s
Sep 14 01:08:00.375: INFO: Pod "azuredisk-volume-tester-jzn66": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.573812725s
STEP: Saw pod success
Sep 14 01:08:00.375: INFO: Pod "azuredisk-volume-tester-jzn66" satisfied condition "Succeeded or Failed"
Sep 14 01:08:00.375: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-jzn66"
Sep 14 01:08:00.443: INFO: Pod azuredisk-volume-tester-jzn66 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-jzn66 in namespace azuredisk-8081
STEP: validating provisioned PV
STEP: checking the PV
... skipping 97 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 14 01:08:56.491: INFO: deleting Pod "azuredisk-5466"/"azuredisk-volume-tester-p8kdn"
Sep 14 01:08:56.553: INFO: Error getting logs for pod azuredisk-volume-tester-p8kdn: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-p8kdn)
STEP: Deleting pod azuredisk-volume-tester-p8kdn in namespace azuredisk-5466
STEP: validating provisioned PV
STEP: checking the PV
Sep 14 01:08:56.664: INFO: deleting PVC "azuredisk-5466"/"pvc-57mbm"
Sep 14 01:08:56.664: INFO: Deleting PersistentVolumeClaim "pvc-57mbm"
STEP: waiting for claim's PV "pvc-a4b66fbf-b5b4-4084-8789-423bcf6587cb" to be deleted
... skipping 58 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 14 01:11:23.867: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-2hzfb" in namespace "azuredisk-2790" to be "Succeeded or Failed"
Sep 14 01:11:23.905: INFO: Pod "azuredisk-volume-tester-2hzfb": Phase="Pending", Reason="", readiness=false. Elapsed: 37.692552ms
Sep 14 01:11:25.943: INFO: Pod "azuredisk-volume-tester-2hzfb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.076041883s
Sep 14 01:11:27.981: INFO: Pod "azuredisk-volume-tester-2hzfb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.114394902s
Sep 14 01:11:30.020: INFO: Pod "azuredisk-volume-tester-2hzfb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.15264694s
Sep 14 01:11:32.058: INFO: Pod "azuredisk-volume-tester-2hzfb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.191440967s
Sep 14 01:11:34.098: INFO: Pod "azuredisk-volume-tester-2hzfb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.2307141s
Sep 14 01:11:36.137: INFO: Pod "azuredisk-volume-tester-2hzfb": Phase="Pending", Reason="", readiness=false. Elapsed: 12.269771908s
Sep 14 01:11:38.176: INFO: Pod "azuredisk-volume-tester-2hzfb": Phase="Pending", Reason="", readiness=false. Elapsed: 14.308879485s
Sep 14 01:11:40.219: INFO: Pod "azuredisk-volume-tester-2hzfb": Phase="Pending", Reason="", readiness=false. Elapsed: 16.351630307s
Sep 14 01:11:42.257: INFO: Pod "azuredisk-volume-tester-2hzfb": Phase="Pending", Reason="", readiness=false. Elapsed: 18.389750416s
Sep 14 01:11:44.296: INFO: Pod "azuredisk-volume-tester-2hzfb": Phase="Pending", Reason="", readiness=false. Elapsed: 20.428553591s
Sep 14 01:11:46.334: INFO: Pod "azuredisk-volume-tester-2hzfb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.46709194s
STEP: Saw pod success
Sep 14 01:11:46.334: INFO: Pod "azuredisk-volume-tester-2hzfb" satisfied condition "Succeeded or Failed"
Sep 14 01:11:46.334: INFO: deleting Pod "azuredisk-2790"/"azuredisk-volume-tester-2hzfb"
Sep 14 01:11:46.397: INFO: Pod azuredisk-volume-tester-2hzfb has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-2hzfb 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 14 01:12:22.796: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-m6tzp" in namespace "azuredisk-5356" to be "Error status code"
Sep 14 01:12:22.833: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Pending", Reason="", readiness=false. Elapsed: 36.446801ms
Sep 14 01:12:24.871: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.0748502s
Sep 14 01:12:26.910: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.113469843s
Sep 14 01:12:28.949: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.152340373s
Sep 14 01:12:30.987: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.191279397s
Sep 14 01:12:33.026: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.230173181s
Sep 14 01:12:35.064: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.267918281s
Sep 14 01:12:37.102: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.305400948s
Sep 14 01:12:39.139: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.342786556s
Sep 14 01:12:41.176: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Pending", Reason="", readiness=false. Elapsed: 18.379884673s
Sep 14 01:12:43.215: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Pending", Reason="", readiness=false. Elapsed: 20.418341903s
Sep 14 01:12:45.252: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Pending", Reason="", readiness=false. Elapsed: 22.455504059s
Sep 14 01:12:47.289: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Pending", Reason="", readiness=false. Elapsed: 24.492736177s
Sep 14 01:12:49.326: INFO: Pod "azuredisk-volume-tester-m6tzp": Phase="Failed", Reason="", readiness=false. Elapsed: 26.529997136s
STEP: Saw pod failure
Sep 14 01:12:49.326: INFO: Pod "azuredisk-volume-tester-m6tzp" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Sep 14 01:12:49.388: INFO: deleting Pod "azuredisk-5356"/"azuredisk-volume-tester-m6tzp"
Sep 14 01:12:49.429: INFO: Pod azuredisk-volume-tester-m6tzp has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-m6tzp in namespace azuredisk-5356
STEP: validating provisioned PV
... skipping 189 lines ...