This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: fix: panic when allow-empty-cloud-config is set
ResultABORTED
Tests 0 failed / 0 succeeded
Started2023-01-29 07:21
Elapsed38m43s
Revision28e9cda353861985bb045512a1eb4ebca3edf9b4
Refs 1699

No Test Failures!


Error lines from build-log.txt

... skipping 107 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11345  100 11345    0     0   181k      0 --:--:-- --:--:-- --:--:--  184k
Downloading https://get.helm.sh/helm-v3.11.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:v1.27.0-91a71d20aca0952016e3206d14299d5c26740deb || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v1.27.0-91a71d20aca0952016e3206d14299d5c26740deb not found: manifest unknown: manifest tagged by "v1.27.0-91a71d20aca0952016e3206d14299d5c26740deb" 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.27.0-91a71d20aca0952016e3206d14299d5c26740deb -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=91a71d20aca0952016e3206d14299d5c26740deb -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-01-29T07:27:18Z -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 1738 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 865 lines ...
          image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.6.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 216 lines ...
STEP: setting up the StorageClass 01/29/23 07:37:14.782
STEP: creating a StorageClass  01/29/23 07:37:14.782
STEP: setting up the PVC and PV 01/29/23 07:37:14.844
STEP: creating a PVC 01/29/23 07:37:14.844
STEP: setting up the pod 01/29/23 07:37:14.908
STEP: deploying the pod 01/29/23 07:37:14.908
STEP: checking that the pod's command exits with no error 01/29/23 07:37:14.975
Jan 29 07:37:14.975: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-drszk" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Jan 29 07:37:15.033: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 58.023053ms
Jan 29 07:37:17.093: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.118242917s
Jan 29 07:37:19.094: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.11832765s
Jan 29 07:37:21.092: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.116836243s
Jan 29 07:37:23.093: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.118116586s
Jan 29 07:37:25.091: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.115990322s
... skipping 6 lines ...
Jan 29 07:37:39.092: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 24.116921318s
Jan 29 07:37:41.091: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 26.115911607s
Jan 29 07:37:43.093: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 28.118236827s
Jan 29 07:37:45.091: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 30.115963726s
Jan 29 07:37:47.093: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.117382354s
STEP: Saw pod success 01/29/23 07:37:47.093
Jan 29 07:37:47.093: INFO: Pod "azuredisk-volume-tester-drszk" satisfied condition "Succeeded or Failed"
Jan 29 07:37:47.093: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-drszk"
Jan 29 07:37:47.199: INFO: Pod azuredisk-volume-tester-drszk has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-drszk in namespace azuredisk-8081 01/29/23 07:37:47.199
STEP: validating provisioned PV 01/29/23 07:37:47.328
STEP: checking the PV 01/29/23 07:37:47.392
... skipping 57 lines ...
    STEP: setting up the StorageClass 01/29/23 07:37:14.782
    STEP: creating a StorageClass  01/29/23 07:37:14.782
    STEP: setting up the PVC and PV 01/29/23 07:37:14.844
    STEP: creating a PVC 01/29/23 07:37:14.844
    STEP: setting up the pod 01/29/23 07:37:14.908
    STEP: deploying the pod 01/29/23 07:37:14.908
    STEP: checking that the pod's command exits with no error 01/29/23 07:37:14.975
    Jan 29 07:37:14.975: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-drszk" in namespace "azuredisk-8081" to be "Succeeded or Failed"
    Jan 29 07:37:15.033: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 58.023053ms
    Jan 29 07:37:17.093: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.118242917s
    Jan 29 07:37:19.094: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.11832765s
    Jan 29 07:37:21.092: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.116836243s
    Jan 29 07:37:23.093: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.118116586s
    Jan 29 07:37:25.091: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.115990322s
... skipping 6 lines ...
    Jan 29 07:37:39.092: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 24.116921318s
    Jan 29 07:37:41.091: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 26.115911607s
    Jan 29 07:37:43.093: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 28.118236827s
    Jan 29 07:37:45.091: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Pending", Reason="", readiness=false. Elapsed: 30.115963726s
    Jan 29 07:37:47.093: INFO: Pod "azuredisk-volume-tester-drszk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.117382354s
    STEP: Saw pod success 01/29/23 07:37:47.093
    Jan 29 07:37:47.093: INFO: Pod "azuredisk-volume-tester-drszk" satisfied condition "Succeeded or Failed"
    Jan 29 07:37:47.093: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-drszk"
    Jan 29 07:37:47.199: INFO: Pod azuredisk-volume-tester-drszk has the following logs: hello world

    STEP: Deleting pod azuredisk-volume-tester-drszk in namespace azuredisk-8081 01/29/23 07:37:47.199
    STEP: validating provisioned PV 01/29/23 07:37:47.328
    STEP: checking the PV 01/29/23 07:37:47.392
... skipping 39 lines ...
Jan 29 07:38:31.321: INFO: PersistentVolumeClaim pvc-t9hhl found but phase is Pending instead of Bound.
Jan 29 07:38:33.389: INFO: PersistentVolumeClaim pvc-t9hhl found and phase=Bound (4.184642345s)
STEP: checking the PVC 01/29/23 07:38:33.389
STEP: validating provisioned PV 01/29/23 07:38:33.446
STEP: checking the PV 01/29/23 07:38:33.506
STEP: deploying the pod 01/29/23 07:38:33.506
STEP: checking that the pods command exits with no error 01/29/23 07:38:33.571
Jan 29 07:38:33.571: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-lkcbk" in namespace "azuredisk-2540" to be "Succeeded or Failed"
Jan 29 07:38:33.629: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 58.15138ms
Jan 29 07:38:35.688: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.116728065s
Jan 29 07:38:37.691: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.12031955s
Jan 29 07:38:39.691: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.120434324s
Jan 29 07:38:41.688: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.116997528s
Jan 29 07:38:43.689: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.117712702s
Jan 29 07:38:45.692: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 12.120556727s
Jan 29 07:38:47.691: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 14.119568616s
Jan 29 07:38:49.690: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 16.119411924s
Jan 29 07:38:51.691: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 18.119680597s
Jan 29 07:38:53.688: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 20.116473764s
Jan 29 07:38:55.691: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.119502163s
STEP: Saw pod success 01/29/23 07:38:55.691
Jan 29 07:38:55.691: INFO: Pod "azuredisk-volume-tester-lkcbk" satisfied condition "Succeeded or Failed"
Jan 29 07:38:55.691: INFO: deleting Pod "azuredisk-2540"/"azuredisk-volume-tester-lkcbk"
Jan 29 07:38:55.785: INFO: Pod azuredisk-volume-tester-lkcbk has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-lkcbk in namespace azuredisk-2540 01/29/23 07:38:55.785
Jan 29 07:38:55.850: INFO: deleting PVC "azuredisk-2540"/"pvc-t9hhl"
Jan 29 07:38:55.850: INFO: Deleting PersistentVolumeClaim "pvc-t9hhl"
... skipping 38 lines ...
    Jan 29 07:38:31.321: INFO: PersistentVolumeClaim pvc-t9hhl found but phase is Pending instead of Bound.
    Jan 29 07:38:33.389: INFO: PersistentVolumeClaim pvc-t9hhl found and phase=Bound (4.184642345s)
    STEP: checking the PVC 01/29/23 07:38:33.389
    STEP: validating provisioned PV 01/29/23 07:38:33.446
    STEP: checking the PV 01/29/23 07:38:33.506
    STEP: deploying the pod 01/29/23 07:38:33.506
    STEP: checking that the pods command exits with no error 01/29/23 07:38:33.571
    Jan 29 07:38:33.571: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-lkcbk" in namespace "azuredisk-2540" to be "Succeeded or Failed"
    Jan 29 07:38:33.629: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 58.15138ms
    Jan 29 07:38:35.688: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.116728065s
    Jan 29 07:38:37.691: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.12031955s
    Jan 29 07:38:39.691: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.120434324s
    Jan 29 07:38:41.688: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.116997528s
    Jan 29 07:38:43.689: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.117712702s
    Jan 29 07:38:45.692: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 12.120556727s
    Jan 29 07:38:47.691: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 14.119568616s
    Jan 29 07:38:49.690: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 16.119411924s
    Jan 29 07:38:51.691: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 18.119680597s
    Jan 29 07:38:53.688: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Pending", Reason="", readiness=false. Elapsed: 20.116473764s
    Jan 29 07:38:55.691: INFO: Pod "azuredisk-volume-tester-lkcbk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.119502163s
    STEP: Saw pod success 01/29/23 07:38:55.691
    Jan 29 07:38:55.691: INFO: Pod "azuredisk-volume-tester-lkcbk" satisfied condition "Succeeded or Failed"
    Jan 29 07:38:55.691: INFO: deleting Pod "azuredisk-2540"/"azuredisk-volume-tester-lkcbk"
    Jan 29 07:38:55.785: INFO: Pod azuredisk-volume-tester-lkcbk has the following logs: hello world

    STEP: Deleting pod azuredisk-volume-tester-lkcbk in namespace azuredisk-2540 01/29/23 07:38:55.785
    Jan 29 07:38:55.850: INFO: deleting PVC "azuredisk-2540"/"pvc-t9hhl"
    Jan 29 07:38:55.850: INFO: Deleting PersistentVolumeClaim "pvc-t9hhl"
... skipping 30 lines ...
STEP: setting up the StorageClass 01/29/23 07:39:37.633
STEP: creating a StorageClass  01/29/23 07:39:37.634
STEP: setting up the PVC and PV 01/29/23 07:39:37.695
STEP: creating a PVC 01/29/23 07:39:37.695
STEP: setting up the pod 01/29/23 07:39:37.759
STEP: deploying the pod 01/29/23 07:39:37.759
STEP: checking that the pod's command exits with no error 01/29/23 07:39:37.818
Jan 29 07:39:37.818: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-f5v68" in namespace "azuredisk-4728" to be "Succeeded or Failed"
Jan 29 07:39:37.875: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 57.001639ms
Jan 29 07:39:39.937: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 2.118667485s
Jan 29 07:39:41.939: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 4.120355396s
Jan 29 07:39:43.936: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 6.117123237s
Jan 29 07:39:45.933: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 8.114630705s
Jan 29 07:39:47.936: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 10.117939346s
... skipping 17 lines ...
Jan 29 07:40:23.933: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 46.11454251s
Jan 29 07:40:25.934: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 48.115528889s
Jan 29 07:40:27.939: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 50.120810704s
Jan 29 07:40:29.938: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 52.119302741s
Jan 29 07:40:31.935: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Succeeded", Reason="", readiness=false. Elapsed: 54.116731467s
STEP: Saw pod success 01/29/23 07:40:31.935
Jan 29 07:40:31.935: INFO: Pod "azuredisk-volume-tester-f5v68" satisfied condition "Succeeded or Failed"
Jan 29 07:40:31.935: INFO: deleting Pod "azuredisk-4728"/"azuredisk-volume-tester-f5v68"
Jan 29 07:40:32.031: INFO: Pod azuredisk-volume-tester-f5v68 has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-f5v68 in namespace azuredisk-4728 01/29/23 07:40:32.031
STEP: validating provisioned PV 01/29/23 07:40:32.17
STEP: checking the PV 01/29/23 07:40:32.229
... skipping 33 lines ...
    STEP: setting up the StorageClass 01/29/23 07:39:37.633
    STEP: creating a StorageClass  01/29/23 07:39:37.634
    STEP: setting up the PVC and PV 01/29/23 07:39:37.695
    STEP: creating a PVC 01/29/23 07:39:37.695
    STEP: setting up the pod 01/29/23 07:39:37.759
    STEP: deploying the pod 01/29/23 07:39:37.759
    STEP: checking that the pod's command exits with no error 01/29/23 07:39:37.818
    Jan 29 07:39:37.818: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-f5v68" in namespace "azuredisk-4728" to be "Succeeded or Failed"
    Jan 29 07:39:37.875: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 57.001639ms
    Jan 29 07:39:39.937: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 2.118667485s
    Jan 29 07:39:41.939: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 4.120355396s
    Jan 29 07:39:43.936: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 6.117123237s
    Jan 29 07:39:45.933: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 8.114630705s
    Jan 29 07:39:47.936: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 10.117939346s
... skipping 17 lines ...
    Jan 29 07:40:23.933: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 46.11454251s
    Jan 29 07:40:25.934: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 48.115528889s
    Jan 29 07:40:27.939: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 50.120810704s
    Jan 29 07:40:29.938: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Pending", Reason="", readiness=false. Elapsed: 52.119302741s
    Jan 29 07:40:31.935: INFO: Pod "azuredisk-volume-tester-f5v68": Phase="Succeeded", Reason="", readiness=false. Elapsed: 54.116731467s
    STEP: Saw pod success 01/29/23 07:40:31.935
    Jan 29 07:40:31.935: INFO: Pod "azuredisk-volume-tester-f5v68" satisfied condition "Succeeded or Failed"
    Jan 29 07:40:31.935: INFO: deleting Pod "azuredisk-4728"/"azuredisk-volume-tester-f5v68"
    Jan 29 07:40:32.031: INFO: Pod azuredisk-volume-tester-f5v68 has the following logs: hello world

    STEP: Deleting pod azuredisk-volume-tester-f5v68 in namespace azuredisk-4728 01/29/23 07:40:32.031
    STEP: validating provisioned PV 01/29/23 07:40:32.17
    STEP: checking the PV 01/29/23 07:40:32.229
... skipping 34 lines ...
STEP: setting up the PVC and PV 01/29/23 07:41:14.007
STEP: creating a PVC 01/29/23 07:41:14.007
STEP: setting up the pod 01/29/23 07:41:14.068
STEP: deploying the pod 01/29/23 07:41:14.068
STEP: checking that the pod has 'FailedMount' event 01/29/23 07:41:14.136
Jan 29 07:41:36.257: INFO: deleting Pod "azuredisk-5466"/"azuredisk-volume-tester-sst9h"
Jan 29 07:41:36.318: INFO: Error getting logs for pod azuredisk-volume-tester-sst9h: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-sst9h)
STEP: Deleting pod azuredisk-volume-tester-sst9h in namespace azuredisk-5466 01/29/23 07:41:36.318
STEP: validating provisioned PV 01/29/23 07:41:36.436
STEP: checking the PV 01/29/23 07:41:36.498
Jan 29 07:41:36.498: INFO: deleting PVC "azuredisk-5466"/"pvc-ww5h9"
Jan 29 07:41:36.498: INFO: Deleting PersistentVolumeClaim "pvc-ww5h9"
STEP: waiting for claim's PV "pvc-acd9c75b-38de-4a08-997d-89d4ad7126ac" to be deleted 01/29/23 07:41:36.561
... skipping 33 lines ...
    STEP: setting up the PVC and PV 01/29/23 07:41:14.007
    STEP: creating a PVC 01/29/23 07:41:14.007
    STEP: setting up the pod 01/29/23 07:41:14.068
    STEP: deploying the pod 01/29/23 07:41:14.068
    STEP: checking that the pod has 'FailedMount' event 01/29/23 07:41:14.136
    Jan 29 07:41:36.257: INFO: deleting Pod "azuredisk-5466"/"azuredisk-volume-tester-sst9h"
    Jan 29 07:41:36.318: INFO: Error getting logs for pod azuredisk-volume-tester-sst9h: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-sst9h)
    STEP: Deleting pod azuredisk-volume-tester-sst9h in namespace azuredisk-5466 01/29/23 07:41:36.318
    STEP: validating provisioned PV 01/29/23 07:41:36.436
    STEP: checking the PV 01/29/23 07:41:36.498
    Jan 29 07:41:36.498: INFO: deleting PVC "azuredisk-5466"/"pvc-ww5h9"
    Jan 29 07:41:36.498: INFO: Deleting PersistentVolumeClaim "pvc-ww5h9"
    STEP: waiting for claim's PV "pvc-acd9c75b-38de-4a08-997d-89d4ad7126ac" to be deleted 01/29/23 07:41:36.561
... skipping 30 lines ...
STEP: setting up the StorageClass 01/29/23 07:42:23.384
STEP: creating a StorageClass  01/29/23 07:42:23.384
STEP: setting up the PVC and PV 01/29/23 07:42:23.444
STEP: creating a PVC 01/29/23 07:42:23.445
STEP: setting up the pod 01/29/23 07:42:23.506
STEP: deploying the pod 01/29/23 07:42:23.506
STEP: checking that the pod's command exits with no error 01/29/23 07:42:23.593
Jan 29 07:42:23.593: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vf8l8" in namespace "azuredisk-2790" to be "Succeeded or Failed"
Jan 29 07:42:23.651: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 57.870532ms
Jan 29 07:42:25.710: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.117552441s
Jan 29 07:42:27.710: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.117103031s
Jan 29 07:42:29.722: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128971997s
Jan 29 07:42:31.709: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.1161883s
Jan 29 07:42:33.714: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.121294028s
... skipping 11 lines ...
Jan 29 07:42:57.710: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 34.11771168s
Jan 29 07:42:59.713: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 36.120355655s
Jan 29 07:43:01.710: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 38.117199684s
Jan 29 07:43:03.711: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 40.118372771s
Jan 29 07:43:05.717: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.124437304s
STEP: Saw pod success 01/29/23 07:43:05.717
Jan 29 07:43:05.717: INFO: Pod "azuredisk-volume-tester-vf8l8" satisfied condition "Succeeded or Failed"
Jan 29 07:43:05.717: INFO: deleting Pod "azuredisk-2790"/"azuredisk-volume-tester-vf8l8"
Jan 29 07:43:05.827: INFO: Pod azuredisk-volume-tester-vf8l8 has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-vf8l8 in namespace azuredisk-2790 01/29/23 07:43:05.827
STEP: validating provisioned PV 01/29/23 07:43:05.963
STEP: checking the PV 01/29/23 07:43:06.021
... skipping 33 lines ...
    STEP: setting up the StorageClass 01/29/23 07:42:23.384
    STEP: creating a StorageClass  01/29/23 07:42:23.384
    STEP: setting up the PVC and PV 01/29/23 07:42:23.444
    STEP: creating a PVC 01/29/23 07:42:23.445
    STEP: setting up the pod 01/29/23 07:42:23.506
    STEP: deploying the pod 01/29/23 07:42:23.506
    STEP: checking that the pod's command exits with no error 01/29/23 07:42:23.593
    Jan 29 07:42:23.593: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-vf8l8" in namespace "azuredisk-2790" to be "Succeeded or Failed"
    Jan 29 07:42:23.651: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 57.870532ms
    Jan 29 07:42:25.710: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.117552441s
    Jan 29 07:42:27.710: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.117103031s
    Jan 29 07:42:29.722: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.128971997s
    Jan 29 07:42:31.709: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.1161883s
    Jan 29 07:42:33.714: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.121294028s
... skipping 11 lines ...
    Jan 29 07:42:57.710: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 34.11771168s
    Jan 29 07:42:59.713: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 36.120355655s
    Jan 29 07:43:01.710: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 38.117199684s
    Jan 29 07:43:03.711: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Pending", Reason="", readiness=false. Elapsed: 40.118372771s
    Jan 29 07:43:05.717: INFO: Pod "azuredisk-volume-tester-vf8l8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 42.124437304s
    STEP: Saw pod success 01/29/23 07:43:05.717
    Jan 29 07:43:05.717: INFO: Pod "azuredisk-volume-tester-vf8l8" satisfied condition "Succeeded or Failed"
    Jan 29 07:43:05.717: INFO: deleting Pod "azuredisk-2790"/"azuredisk-volume-tester-vf8l8"
    Jan 29 07:43:05.827: INFO: Pod azuredisk-volume-tester-vf8l8 has the following logs: e2e-test

    STEP: Deleting pod azuredisk-volume-tester-vf8l8 in namespace azuredisk-2790 01/29/23 07:43:05.827
    STEP: validating provisioned PV 01/29/23 07:43:05.963
    STEP: checking the PV 01/29/23 07:43:06.021
... skipping 37 lines ...
STEP: creating volume in external rg azuredisk-csi-driver-test-aa444200-9fa8-11ed-bfb3-a2e29b6d687b 01/29/23 07:43:49.252
STEP: setting up the StorageClass 01/29/23 07:43:49.253
STEP: creating a StorageClass  01/29/23 07:43:49.253
STEP: setting up the PVC and PV 01/29/23 07:43:49.311
STEP: creating a PVC 01/29/23 07:43:49.311
STEP: deploying the pod 01/29/23 07:43:49.373
STEP: checking that the pod's command exits with no error 01/29/23 07:43:49.438
Jan 29 07:43:49.438: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-b5npr" in namespace "azuredisk-5356" to be "Succeeded or Failed"
Jan 29 07:43:49.496: INFO: Pod "azuredisk-volume-tester-b5npr": Phase="Pending", Reason="", readiness=false. Elapsed: 58.530801ms
Jan 29 07:43:51.557: INFO: Pod "azuredisk-volume-tester-b5npr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.119432005s
Jan 29 07:43:53.554: INFO: Pod "azuredisk-volume-tester-b5npr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.11657851s
Jan 29 07:43:55.565: INFO: Pod "azuredisk-volume-tester-b5npr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126974061s
Jan 29 07:43:57.557: INFO: Pod "azuredisk-volume-tester-b5npr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.119405586s
Jan 29 07:43:59.558: INFO: Pod "azuredisk-volume-tester-b5npr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.119769677s
... skipping 2 lines ...
Jan 29 07:44:05.562: INFO: Pod "azuredisk-volume-tester-b5npr": Phase="Pending", Reason="", readiness=false. Elapsed: 16.123751182s
Jan 29 07:44:07.559: INFO: Pod "azuredisk-volume-tester-b5npr": Phase="Pending", Reason="", readiness=false. Elapsed: 18.120859513s
Jan 29 07:44:09.557: INFO: Pod "azuredisk-volume-tester-b5npr": Phase="Pending", Reason="", readiness=false. Elapsed: 20.11910326s
Jan 29 07:44:11.556: INFO: Pod "azuredisk-volume-tester-b5npr": Phase="Pending", Reason="", readiness=false. Elapsed: 22.118704154s
Jan 29 07:44:13.623: INFO: Pod "azuredisk-volume-tester-b5npr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.185364962s
STEP: Saw pod success 01/29/23 07:44:13.623
Jan 29 07:44:13.624: INFO: Pod "azuredisk-volume-tester-b5npr" satisfied condition "Succeeded or Failed"
Jan 29 07:44:13.624: INFO: deleting Pod "azuredisk-5356"/"azuredisk-volume-tester-b5npr"
Jan 29 07:44:13.691: INFO: Pod azuredisk-volume-tester-b5npr has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-b5npr in namespace azuredisk-5356 01/29/23 07:44:13.692
STEP: validating provisioned PV 01/29/23 07:44:13.813
STEP: checking the PV 01/29/23 07:44:13.871
... skipping 18 lines ...