This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: fix: filesystem is not resized when restoring from snapshot with a bigger size
ResultABORTED
Tests 0 failed / 13 succeeded
Started2022-05-01 13:04
Elapsed42m25s
Revisionb9079ac367a70b52c1cb25345e856049980910d8
Refs 1309

No Test Failures!


Show 13 Passed Tests

Show 46 Skipped Tests

Error lines from build-log.txt

... skipping 82 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   205k      0 --:--:-- --:--:-- --:--:--  205k
Downloading https://get.helm.sh/helm-v3.8.2-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.18.0-59de170d5999bf1826de94c94c24f912e8346dd3 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v1.18.0-59de170d5999bf1826de94c94c24f912e8346dd3 not found: manifest unknown: manifest tagged by "v1.18.0-59de170d5999bf1826de94c94c24f912e8346dd3" 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.18.0-59de170d5999bf1826de94c94c24f912e8346dd3 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=59de170d5999bf1826de94c94c24f912e8346dd3 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2022-05-01T13:10:48Z -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 1588 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.4.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 180 lines ...
Go Version: go1.18.1
Platform: linux/amd64
Topology Key: topology.disk.csi.azure.com/zone

Streaming logs below:
STEP: Building a namespace api object, basename azuredisk
W0501 13:22:11.121515   14119 azure_disk_utils.go:165] InitializeCloudFromSecret: failed to get cloud config from secret /: failed to get secret /: resource name may not be empty
W0501 13:22:11.122156   14119 azuredisk.go:188] DisableAvailabilitySetNodes for controller is set as false while current VMType is vmss
I0501 13:22:11.122789   14119 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I0501 13:22:11.122809   14119 driver.go:81] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0501 13:22:11.122814   14119 driver.go:81] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0501 13:22:11.122818   14119 driver.go:81] Enabling controller service capability: CLONE_VOLUME
I0501 13:22:11.122821   14119 driver.go:81] Enabling controller service capability: EXPAND_VOLUME
... skipping 70 lines ...

    test case is only available for CSI drivers

    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:304
------------------------------
Pre-Provisioned [single-az] 
  should fail when maxShares is invalid [disk.csi.azure.com][windows]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:163
STEP: Creating a kubernetes client
May  1 13:22:14.705: INFO: >>> kubeConfig: /root/tmp2129140850/kubeconfig/kubeconfig.westeurope.json
STEP: Building a namespace api object, basename azuredisk
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
... skipping 3 lines ...

S [SKIPPING] [0.971 seconds]
Pre-Provisioned
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:37
  [single-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:69
    should fail when maxShares is invalid [disk.csi.azure.com][windows] [It]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:163

    test case is only available for CSI drivers

    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:304
------------------------------
... skipping 54 lines ...
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
I0501 13:22:18.367857   14119 azuredisk_driver.go:56] Using azure disk driver: kubernetes.io/azure-disk
STEP: Successfully provisioned AzureDisk volume: "/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-xyeqkcza/providers/Microsoft.Compute/disks/pre-provisioned-inline-volume"

STEP: deploying the pod
STEP: checking that the pod's command exits with no error
May  1 13:22:26.079: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-5q8qf" in namespace "azuredisk-5194" to be "Succeeded or Failed"
May  1 13:22:26.187: INFO: Pod "azuredisk-volume-tester-5q8qf": Phase="Pending", Reason="", readiness=false. Elapsed: 107.585256ms
May  1 13:22:28.296: INFO: Pod "azuredisk-volume-tester-5q8qf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216372023s
May  1 13:22:30.405: INFO: Pod "azuredisk-volume-tester-5q8qf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.325326599s
May  1 13:22:32.513: INFO: Pod "azuredisk-volume-tester-5q8qf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.433478122s
May  1 13:22:34.622: INFO: Pod "azuredisk-volume-tester-5q8qf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.542794821s
May  1 13:22:36.732: INFO: Pod "azuredisk-volume-tester-5q8qf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.652393839s
May  1 13:22:38.840: INFO: Pod "azuredisk-volume-tester-5q8qf": Phase="Pending", Reason="", readiness=false. Elapsed: 12.760719091s
May  1 13:22:40.947: INFO: Pod "azuredisk-volume-tester-5q8qf": Phase="Pending", Reason="", readiness=false. Elapsed: 14.868080491s
May  1 13:22:43.056: INFO: Pod "azuredisk-volume-tester-5q8qf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.976199709s
STEP: Saw pod success
May  1 13:22:43.056: INFO: Pod "azuredisk-volume-tester-5q8qf" satisfied condition "Succeeded or Failed"
May  1 13:22:43.056: INFO: deleting Pod "azuredisk-5194"/"azuredisk-volume-tester-5q8qf"
May  1 13:22:43.213: INFO: Pod azuredisk-volume-tester-5q8qf has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-5q8qf in namespace azuredisk-5194
May  1 13:22:43.330: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "azuredisk-5194" for this suite.
... skipping 22 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
May  1 13:22:45.458: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-fmpwl" in namespace "azuredisk-1353" to be "Succeeded or Failed"
May  1 13:22:45.566: INFO: Pod "azuredisk-volume-tester-fmpwl": Phase="Pending", Reason="", readiness=false. Elapsed: 108.030695ms
May  1 13:22:47.675: INFO: Pod "azuredisk-volume-tester-fmpwl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.216991347s
May  1 13:22:49.784: INFO: Pod "azuredisk-volume-tester-fmpwl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.326076916s
May  1 13:22:51.892: INFO: Pod "azuredisk-volume-tester-fmpwl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.434050259s
May  1 13:22:54.000: INFO: Pod "azuredisk-volume-tester-fmpwl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.542220486s
May  1 13:22:56.109: INFO: Pod "azuredisk-volume-tester-fmpwl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.651481674s
... skipping 7 lines ...
May  1 13:23:12.979: INFO: Pod "azuredisk-volume-tester-fmpwl": Phase="Pending", Reason="", readiness=false. Elapsed: 27.521707145s
May  1 13:23:15.088: INFO: Pod "azuredisk-volume-tester-fmpwl": Phase="Pending", Reason="", readiness=false. Elapsed: 29.630290456s
May  1 13:23:17.198: INFO: Pod "azuredisk-volume-tester-fmpwl": Phase="Pending", Reason="", readiness=false. Elapsed: 31.739860184s
May  1 13:23:19.305: INFO: Pod "azuredisk-volume-tester-fmpwl": Phase="Pending", Reason="", readiness=false. Elapsed: 33.847129272s
May  1 13:23:21.413: INFO: Pod "azuredisk-volume-tester-fmpwl": Phase="Succeeded", Reason="", readiness=false. Elapsed: 35.955407059s
STEP: Saw pod success
May  1 13:23:21.413: INFO: Pod "azuredisk-volume-tester-fmpwl" satisfied condition "Succeeded or Failed"
May  1 13:23:21.413: INFO: deleting Pod "azuredisk-1353"/"azuredisk-volume-tester-fmpwl"
May  1 13:23:21.548: INFO: Pod azuredisk-volume-tester-fmpwl has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-fmpwl in namespace azuredisk-1353
STEP: validating provisioned PV
STEP: checking the PV
... skipping 98 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
May  1 13:24:27.078: INFO: deleting Pod "azuredisk-1563"/"azuredisk-volume-tester-z9kcr"
May  1 13:24:27.188: INFO: Error getting logs for pod azuredisk-volume-tester-z9kcr: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-z9kcr)
STEP: Deleting pod azuredisk-volume-tester-z9kcr in namespace azuredisk-1563
STEP: validating provisioned PV
STEP: checking the PV
May  1 13:24:27.513: INFO: deleting PVC "azuredisk-1563"/"pvc-k5pj7"
May  1 13:24:27.513: INFO: Deleting PersistentVolumeClaim "pvc-k5pj7"
STEP: waiting for claim's PV "pvc-ed87025c-54fd-43fe-b9cc-e5aa878c9e46" 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
May  1 13:26:58.237: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-772q4" in namespace "azuredisk-7463" to be "Succeeded or Failed"
May  1 13:26:58.345: INFO: Pod "azuredisk-volume-tester-772q4": Phase="Pending", Reason="", readiness=false. Elapsed: 107.645888ms
May  1 13:27:00.453: INFO: Pod "azuredisk-volume-tester-772q4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215861018s
May  1 13:27:02.561: INFO: Pod "azuredisk-volume-tester-772q4": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324168234s
May  1 13:27:04.670: INFO: Pod "azuredisk-volume-tester-772q4": Phase="Pending", Reason="", readiness=false. Elapsed: 6.433512773s
May  1 13:27:06.779: INFO: Pod "azuredisk-volume-tester-772q4": Phase="Pending", Reason="", readiness=false. Elapsed: 8.542017161s
May  1 13:27:08.902: INFO: Pod "azuredisk-volume-tester-772q4": Phase="Pending", Reason="", readiness=false. Elapsed: 10.664952784s
May  1 13:27:11.011: INFO: Pod "azuredisk-volume-tester-772q4": Phase="Pending", Reason="", readiness=false. Elapsed: 12.774192209s
May  1 13:27:13.119: INFO: Pod "azuredisk-volume-tester-772q4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.882279703s
STEP: Saw pod success
May  1 13:27:13.119: INFO: Pod "azuredisk-volume-tester-772q4" satisfied condition "Succeeded or Failed"
May  1 13:27:13.119: INFO: deleting Pod "azuredisk-7463"/"azuredisk-volume-tester-772q4"
May  1 13:27:13.251: INFO: Pod azuredisk-volume-tester-772q4 has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-772q4 in namespace azuredisk-7463
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
May  1 13:27:51.919: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-f8jh7" in namespace "azuredisk-9241" to be "Error status code"
May  1 13:27:52.027: INFO: Pod "azuredisk-volume-tester-f8jh7": Phase="Pending", Reason="", readiness=false. Elapsed: 107.392503ms
May  1 13:27:54.135: INFO: Pod "azuredisk-volume-tester-f8jh7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.215575744s
May  1 13:27:56.244: INFO: Pod "azuredisk-volume-tester-f8jh7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.324924363s
May  1 13:27:58.355: INFO: Pod "azuredisk-volume-tester-f8jh7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.435500958s
May  1 13:28:00.463: INFO: Pod "azuredisk-volume-tester-f8jh7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.544048659s
May  1 13:28:02.572: INFO: Pod "azuredisk-volume-tester-f8jh7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.652954977s
May  1 13:28:04.681: INFO: Pod "azuredisk-volume-tester-f8jh7": Phase="Pending", Reason="", readiness=false. Elapsed: 12.761590031s
May  1 13:28:06.790: INFO: Pod "azuredisk-volume-tester-f8jh7": Phase="Failed", Reason="", readiness=false. Elapsed: 14.870806912s
STEP: Saw pod failure
May  1 13:28:06.790: INFO: Pod "azuredisk-volume-tester-f8jh7" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
May  1 13:28:06.930: INFO: deleting Pod "azuredisk-9241"/"azuredisk-volume-tester-f8jh7"
May  1 13:28:07.040: INFO: Pod azuredisk-volume-tester-f8jh7 has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-f8jh7 in namespace azuredisk-9241
STEP: validating provisioned PV
... skipping 188 lines ...