This job view page is being replaced by Spyglass soon. Check out the new job view.
PRsunpa93: [V2] feat: update volume attachment with publish context upon attachment completion
ResultABORTED
Tests 0 failed / 14 succeeded
Started2022-06-21 05:01
Elapsed38m0s
Revision48e7f65ca27c250dd34d36081e1027f1acfa2d2e
Refs 1361

No Test Failures!


Show 14 Passed Tests

Show 93 Skipped Tests

Error lines from build-log.txt

... skipping 94 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   213k      0 --:--:-- --:--:-- --:--:--  213k
Downloading https://get.helm.sh/helm-v3.9.0-linux-amd64.tar.gz
Verifying checksum... Done.
Preparing to install helm into /usr/local/bin
helm installed into /usr/local/bin/helm
docker pull k8sprow.azurecr.io/azuredisk-csi:latest-v2-2997e77690296ed7e15b24c0ff96ce6d5abd9534 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:latest-v2-2997e77690296ed7e15b24c0ff96ce6d5abd9534 not found: manifest unknown: manifest tagged by "latest-v2-2997e77690296ed7e15b24c0ff96ce6d5abd9534" 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=latest-v2-2997e77690296ed7e15b24c0ff96ce6d5abd9534 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=2997e77690296ed7e15b24c0ff96ce6d5abd9534 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2022-06-21T05:07:28Z -extldflags "-static"" -tags azurediskv2 -mod vendor -o _output/amd64/azurediskpluginv2.exe ./pkg/azurediskplugin
docker buildx rm container-builder || true
error: no builder "container-builder" found
docker buildx create --use --name=container-builder
container-builder
# enable qemu for arm64 build
# https://github.com/docker/buildx/issues/464#issuecomment-741507760
docker run --privileged --rm tonistiigi/binfmt --uninstall qemu-aarch64
Unable to find image 'tonistiigi/binfmt:latest' locally
... skipping 685 lines ...
         }
      }
   ]
}
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker pull k8sprow.azurecr.io/azdiskschedulerextender-csi:latest-v2-2997e77690296ed7e15b24c0ff96ce6d5abd9534 || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender
Error response from daemon: manifest for k8sprow.azurecr.io/azdiskschedulerextender-csi:latest-v2-2997e77690296ed7e15b24c0ff96ce6d5abd9534 not found: manifest unknown: manifest tagged by "latest-v2-2997e77690296ed7e15b24c0ff96ce6d5abd9534" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
docker buildx rm container-builder || true
docker buildx create --use --name=container-builder
container-builder
# enable qemu for arm64 build
# https://github.com/docker/buildx/issues/464#issuecomment-741507760
... skipping 869 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 244 lines ...
            - volumeName
            - volume_context
            - volume_id
            type: object
          status:
            description: status represents the current state of AzVolumeAttachment.
              includes error, state, and attachment status
            properties:
              annotation:
                additionalProperties:
                  type: string
                description: Annotations contains additional resource information
                  to guide driver actions
... skipping 13 lines ...
                  role:
                    description: The current attachment role.
                    type: string
                required:
                - role
                type: object
              error:
                description: Error occurred during attach/detach of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 173 lines ...
            - maxMountReplicaCount
            - volumeCapability
            - volumeName
            type: object
          status:
            description: status represents the current state of AzVolume. includes
              error, state, and volume status
            properties:
              annotation:
                additionalProperties:
                  type: string
                description: Annotations contains additional resource information
                  to guide driver actions
... skipping 34 lines ...
                    type: string
                required:
                - capacity_bytes
                - node_expansion_required
                - volume_id
                type: object
              error:
                description: Error occurred during creation/deletion of volume
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  parameters:
... skipping 1061 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 455 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jun 21 05:15:58.903: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-4t2cm" in namespace "azuredisk-9752" to be "Succeeded or Failed"
Jun 21 05:15:59.005: INFO: Pod "azuredisk-volume-tester-4t2cm": Phase="Pending", Reason="", readiness=false. Elapsed: 102.641744ms
Jun 21 05:16:01.109: INFO: Pod "azuredisk-volume-tester-4t2cm": Phase="Pending", Reason="", readiness=false. Elapsed: 2.20570989s
Jun 21 05:16:03.211: INFO: Pod "azuredisk-volume-tester-4t2cm": Phase="Pending", Reason="", readiness=false. Elapsed: 4.308377792s
Jun 21 05:16:05.315: INFO: Pod "azuredisk-volume-tester-4t2cm": Phase="Pending", Reason="", readiness=false. Elapsed: 6.412523873s
Jun 21 05:16:07.419: INFO: Pod "azuredisk-volume-tester-4t2cm": Phase="Pending", Reason="", readiness=false. Elapsed: 8.516484032s
Jun 21 05:16:09.524: INFO: Pod "azuredisk-volume-tester-4t2cm": Phase="Pending", Reason="", readiness=false. Elapsed: 10.62072321s
... skipping 3 lines ...
Jun 21 05:16:17.937: INFO: Pod "azuredisk-volume-tester-4t2cm": Phase="Pending", Reason="", readiness=false. Elapsed: 19.03420357s
Jun 21 05:16:20.041: INFO: Pod "azuredisk-volume-tester-4t2cm": Phase="Pending", Reason="", readiness=false. Elapsed: 21.138034659s
Jun 21 05:16:22.144: INFO: Pod "azuredisk-volume-tester-4t2cm": Phase="Pending", Reason="", readiness=false. Elapsed: 23.240983396s
Jun 21 05:16:24.248: INFO: Pod "azuredisk-volume-tester-4t2cm": Phase="Pending", Reason="", readiness=false. Elapsed: 25.344964059s
Jun 21 05:16:26.353: INFO: Pod "azuredisk-volume-tester-4t2cm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 27.449715982s
STEP: Saw pod success
Jun 21 05:16:26.353: INFO: Pod "azuredisk-volume-tester-4t2cm" satisfied condition "Succeeded or Failed"
Jun 21 05:16:26.353: INFO: deleting Pod "azuredisk-9752"/"azuredisk-volume-tester-4t2cm"
Jun 21 05:16:26.490: INFO: Pod azuredisk-volume-tester-4t2cm has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-4t2cm in namespace azuredisk-9752
STEP: validating provisioned PV
STEP: checking the PV
... skipping 122 lines ...
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod has 'FailedMount' event
Jun 21 05:17:11.461: INFO: deleting Pod "azuredisk-3936"/"azuredisk-volume-tester-dmzcg"
Jun 21 05:17:11.565: INFO: Error getting logs for pod azuredisk-volume-tester-dmzcg: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-dmzcg)
STEP: Deleting pod azuredisk-volume-tester-dmzcg in namespace azuredisk-3936
STEP: validating provisioned PV
STEP: checking the PV
Jun 21 05:17:11.874: INFO: deleting PVC "azuredisk-3936"/"pvc-77vks"
Jun 21 05:17:11.874: INFO: Deleting PersistentVolumeClaim "pvc-77vks"
STEP: waiting for claim's PV "pvc-d5d2a215-0755-47b5-a6b2-bb1f05ae32b7" to be deleted
... skipping 55 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jun 21 05:19:27.195: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-n6twr" in namespace "azuredisk-3275" to be "Succeeded or Failed"
Jun 21 05:19:27.297: INFO: Pod "azuredisk-volume-tester-n6twr": Phase="Pending", Reason="", readiness=false. Elapsed: 101.993471ms
Jun 21 05:19:29.400: INFO: Pod "azuredisk-volume-tester-n6twr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.204565136s
Jun 21 05:19:31.504: INFO: Pod "azuredisk-volume-tester-n6twr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.308618974s
Jun 21 05:19:33.607: INFO: Pod "azuredisk-volume-tester-n6twr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.411772665s
Jun 21 05:19:35.712: INFO: Pod "azuredisk-volume-tester-n6twr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.516426188s
Jun 21 05:19:37.817: INFO: Pod "azuredisk-volume-tester-n6twr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.622075602s
Jun 21 05:19:39.922: INFO: Pod "azuredisk-volume-tester-n6twr": Phase="Pending", Reason="", readiness=false. Elapsed: 12.726877496s
Jun 21 05:19:42.026: INFO: Pod "azuredisk-volume-tester-n6twr": Phase="Pending", Reason="", readiness=false. Elapsed: 14.830927312s
Jun 21 05:19:44.130: INFO: Pod "azuredisk-volume-tester-n6twr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 16.934482494s
STEP: Saw pod success
Jun 21 05:19:44.130: INFO: Pod "azuredisk-volume-tester-n6twr" satisfied condition "Succeeded or Failed"
Jun 21 05:19:44.130: INFO: deleting Pod "azuredisk-3275"/"azuredisk-volume-tester-n6twr"
Jun 21 05:19:44.255: INFO: Pod azuredisk-volume-tester-n6twr has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-n6twr in namespace azuredisk-3275
STEP: validating provisioned PV
STEP: checking the PV
... skipping 36 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with an error
Jun 21 05:20:07.585: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-lbqfj" in namespace "azuredisk-3106" to be "Error status code"
Jun 21 05:20:07.688: INFO: Pod "azuredisk-volume-tester-lbqfj": Phase="Pending", Reason="", readiness=false. Elapsed: 102.18738ms
Jun 21 05:20:09.791: INFO: Pod "azuredisk-volume-tester-lbqfj": Phase="Pending", Reason="", readiness=false. Elapsed: 2.205417136s
Jun 21 05:20:11.895: INFO: Pod "azuredisk-volume-tester-lbqfj": Phase="Pending", Reason="", readiness=false. Elapsed: 4.309196359s
Jun 21 05:20:13.997: INFO: Pod "azuredisk-volume-tester-lbqfj": Phase="Pending", Reason="", readiness=false. Elapsed: 6.411990125s
Jun 21 05:20:16.101: INFO: Pod "azuredisk-volume-tester-lbqfj": Phase="Pending", Reason="", readiness=false. Elapsed: 8.515650034s
Jun 21 05:20:18.207: INFO: Pod "azuredisk-volume-tester-lbqfj": Phase="Pending", Reason="", readiness=false. Elapsed: 10.621945148s
Jun 21 05:20:20.312: INFO: Pod "azuredisk-volume-tester-lbqfj": Phase="Pending", Reason="", readiness=false. Elapsed: 12.72632801s
Jun 21 05:20:22.415: INFO: Pod "azuredisk-volume-tester-lbqfj": Phase="Pending", Reason="", readiness=false. Elapsed: 14.829578661s
Jun 21 05:20:24.519: INFO: Pod "azuredisk-volume-tester-lbqfj": Phase="Failed", Reason="", readiness=false. Elapsed: 16.93386922s
STEP: Saw pod failure
Jun 21 05:20:24.519: INFO: Pod "azuredisk-volume-tester-lbqfj" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Jun 21 05:20:24.625: INFO: deleting Pod "azuredisk-3106"/"azuredisk-volume-tester-lbqfj"
Jun 21 05:20:24.731: INFO: Pod azuredisk-volume-tester-lbqfj has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-lbqfj in namespace azuredisk-3106
STEP: validating provisioned PV
... skipping 167 lines ...