This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: [WIP] test
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2023-01-08 14:29
Elapsed2h15m
Revisionbe3b48204d407d6782b71100aa2e96d1f960c2aa
Refs 1685

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   194k      0 --:--:-- --:--:-- --:--:--  194k
Downloading https://get.helm.sh/helm-v3.10.3-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-e0a98c3315b0b433077ce4e28edfaaea8ca15ea6 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:v1.27.0-e0a98c3315b0b433077ce4e28edfaaea8ca15ea6 not found: manifest unknown: manifest tagged by "v1.27.0-e0a98c3315b0b433077ce4e28edfaaea8ca15ea6" 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-e0a98c3315b0b433077ce4e28edfaaea8ca15ea6 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=e0a98c3315b0b433077ce4e28edfaaea8ca15ea6 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-01-08T14:34:46Z -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 1751 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/08/23 14:44:34.035
STEP: creating a StorageClass  01/08/23 14:44:34.035
STEP: setting up the PVC and PV 01/08/23 14:44:34.091
STEP: creating a PVC 01/08/23 14:44:34.091
STEP: setting up the pod 01/08/23 14:44:34.147
STEP: deploying the pod 01/08/23 14:44:34.147
STEP: checking that the pod's command exits with no error 01/08/23 14:44:34.202
Jan  8 14:44:34.202: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-q92w8" in namespace "azuredisk-8081" to be "Succeeded or Failed"
Jan  8 14:44:34.256: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 54.370828ms
Jan  8 14:44:36.311: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.10908752s
Jan  8 14:44:38.313: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.110684187s
Jan  8 14:44:40.312: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.10976907s
Jan  8 14:44:42.310: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.108082978s
Jan  8 14:44:44.310: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.108306638s
... skipping 440 lines ...
Jan  8 14:59:26.311: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.109334254s
Jan  8 14:59:28.312: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.110306924s
Jan  8 14:59:30.311: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.109061834s
Jan  8 14:59:32.312: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.109596923s
Jan  8 14:59:34.311: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.109136296s
Jan  8 14:59:34.366: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.163797429s
Jan  8 14:59:34.367: INFO: Unexpected error: 
    <*pod.timeoutError | 0xc000b58180>: {
        msg: "timed out while waiting for pod azuredisk-8081/azuredisk-volume-tester-q92w8 to be Succeeded or Failed",
        observedObjects: [
            <*v1.Pod | 0xc000ac5b00>{
                TypeMeta: {Kind: "", APIVersion: ""},
                ObjectMeta: {
                    Name: "azuredisk-volume-tester-q92w8",
                    GenerateName: "azuredisk-volume-tester-",
... skipping 138 lines ...
Gomega truncated this representation as it exceeds 'format.MaxLength'.
Consider having the object provide a custom 'GomegaStringer' representation
or adjust the parameters in Gomega's 'format' package.

Learn more here: https://onsi.github.io/gomega/#adjusting-output

Jan  8 14:59:34.367: FAIL: timed out while waiting for pod azuredisk-8081/azuredisk-volume-tester-q92w8 to be Succeeded or Failed

Full Stack Trace
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForSuccess(0x2250591?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823 +0x5d
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedCmdVolumeTest).Run(0xc000bb1d38, {0x270a780, 0xc000209040}, 0x5?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_cmd_volume_tester.go:48 +0x1af
sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func2()
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:149 +0x705
Jan  8 14:59:34.368: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-q92w8"
Jan  8 14:59:34.481: INFO: Error getting logs for pod azuredisk-volume-tester-q92w8: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-q92w8)
STEP: Deleting pod azuredisk-volume-tester-q92w8 in namespace azuredisk-8081 01/08/23 14:59:34.481
STEP: validating provisioned PV 01/08/23 14:59:34.594
STEP: checking the PV 01/08/23 14:59:34.648
Jan  8 14:59:34.648: INFO: deleting PVC "azuredisk-8081"/"pvc-dgwk5"
Jan  8 14:59:34.648: INFO: Deleting PersistentVolumeClaim "pvc-dgwk5"
STEP: waiting for claim's PV "pvc-8b379bfa-ee2c-45aa-995a-dd8cc3654700" to be deleted 01/08/23 14:59:34.704
... skipping 7 lines ...
Jan  8 15:00:00.043: INFO: Waiting up to 5m0s for PersistentVolumeClaim azuredisk-8081 to be removed
Jan  8 15:00:00.097: INFO: Claim "azuredisk-8081" in namespace "pvc-dgwk5" doesn't exist in the system
Jan  8 15:00:00.097: INFO: deleting StorageClass azuredisk-8081-disk.csi.azure.com-dynamic-sc-cn774
STEP: dump namespace information after failure 01/08/23 15:00:00.153
STEP: Destroying namespace "azuredisk-8081" for this suite. 01/08/23 15:00:00.154
------------------------------
• [FAILED] [927.358 seconds]
Dynamic Provisioning
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:41
  [multi-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:48
    [It] should create a volume on demand with mount options [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:103
... skipping 19 lines ...
    STEP: setting up the StorageClass 01/08/23 14:44:34.035
    STEP: creating a StorageClass  01/08/23 14:44:34.035
    STEP: setting up the PVC and PV 01/08/23 14:44:34.091
    STEP: creating a PVC 01/08/23 14:44:34.091
    STEP: setting up the pod 01/08/23 14:44:34.147
    STEP: deploying the pod 01/08/23 14:44:34.147
    STEP: checking that the pod's command exits with no error 01/08/23 14:44:34.202
    Jan  8 14:44:34.202: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-q92w8" in namespace "azuredisk-8081" to be "Succeeded or Failed"
    Jan  8 14:44:34.256: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 54.370828ms
    Jan  8 14:44:36.311: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.10908752s
    Jan  8 14:44:38.313: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.110684187s
    Jan  8 14:44:40.312: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.10976907s
    Jan  8 14:44:42.310: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.108082978s
    Jan  8 14:44:44.310: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.108306638s
... skipping 440 lines ...
    Jan  8 14:59:26.311: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.109334254s
    Jan  8 14:59:28.312: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.110306924s
    Jan  8 14:59:30.311: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.109061834s
    Jan  8 14:59:32.312: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.109596923s
    Jan  8 14:59:34.311: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.109136296s
    Jan  8 14:59:34.366: INFO: Pod "azuredisk-volume-tester-q92w8": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.163797429s
    Jan  8 14:59:34.367: INFO: Unexpected error: 
        <*pod.timeoutError | 0xc000b58180>: {
            msg: "timed out while waiting for pod azuredisk-8081/azuredisk-volume-tester-q92w8 to be Succeeded or Failed",
            observedObjects: [
                <*v1.Pod | 0xc000ac5b00>{
                    TypeMeta: {Kind: "", APIVersion: ""},
                    ObjectMeta: {
                        Name: "azuredisk-volume-tester-q92w8",
                        GenerateName: "azuredisk-volume-tester-",
... skipping 138 lines ...
    Gomega truncated this representation as it exceeds 'format.MaxLength'.
    Consider having the object provide a custom 'GomegaStringer' representation
    or adjust the parameters in Gomega's 'format' package.

    Learn more here: https://onsi.github.io/gomega/#adjusting-output

    Jan  8 14:59:34.367: FAIL: timed out while waiting for pod azuredisk-8081/azuredisk-volume-tester-q92w8 to be Succeeded or Failed

    Full Stack Trace
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForSuccess(0x2250591?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823 +0x5d
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedCmdVolumeTest).Run(0xc000bb1d38, {0x270a780, 0xc000209040}, 0x5?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_cmd_volume_tester.go:48 +0x1af
    sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func2()
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:149 +0x705
    Jan  8 14:59:34.368: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-q92w8"
    Jan  8 14:59:34.481: INFO: Error getting logs for pod azuredisk-volume-tester-q92w8: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-q92w8)
    STEP: Deleting pod azuredisk-volume-tester-q92w8 in namespace azuredisk-8081 01/08/23 14:59:34.481
    STEP: validating provisioned PV 01/08/23 14:59:34.594
    STEP: checking the PV 01/08/23 14:59:34.648
    Jan  8 14:59:34.648: INFO: deleting PVC "azuredisk-8081"/"pvc-dgwk5"
    Jan  8 14:59:34.648: INFO: Deleting PersistentVolumeClaim "pvc-dgwk5"
    STEP: waiting for claim's PV "pvc-8b379bfa-ee2c-45aa-995a-dd8cc3654700" to be deleted 01/08/23 14:59:34.704
... skipping 8 lines ...
    Jan  8 15:00:00.097: INFO: Claim "azuredisk-8081" in namespace "pvc-dgwk5" doesn't exist in the system
    Jan  8 15:00:00.097: INFO: deleting StorageClass azuredisk-8081-disk.csi.azure.com-dynamic-sc-cn774
    STEP: dump namespace information after failure 01/08/23 15:00:00.153
    STEP: Destroying namespace "azuredisk-8081" for this suite. 01/08/23 15:00:00.154
  << End Captured GinkgoWriter Output

  Jan  8 14:59:34.368: timed out while waiting for pod azuredisk-8081/azuredisk-volume-tester-q92w8 to be Succeeded or Failed
  In [It] at: /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823

  There were additional failures detected after the initial failure:
    [PANICKED]
    Test Panicked
    In [DeferCleanup (Each)] at: /usr/local/go/src/runtime/panic.go:260

    runtime error: invalid memory address or nil pointer dereference

    Full Stack Trace
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo.func1()
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:274 +0x5c
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo(0xc00003c3c0)
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:271 +0x179
... skipping 25 lines ...
Jan  8 15:00:03.308: INFO: PersistentVolumeClaim pvc-hvfrz found but phase is Pending instead of Bound.
Jan  8 15:00:05.365: INFO: PersistentVolumeClaim pvc-hvfrz found and phase=Bound (4.166423716s)
STEP: checking the PVC 01/08/23 15:00:05.365
STEP: validating provisioned PV 01/08/23 15:00:05.421
STEP: checking the PV 01/08/23 15:00:05.475
STEP: deploying the pod 01/08/23 15:00:05.475
STEP: checking that the pods command exits with no error 01/08/23 15:00:05.532
Jan  8 15:00:05.532: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-pfrq5" in namespace "azuredisk-2540" to be "Succeeded or Failed"
Jan  8 15:00:05.587: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 54.762178ms
Jan  8 15:00:07.641: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.1083686s
Jan  8 15:00:09.640: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.107837633s
Jan  8 15:00:11.641: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.109089556s
Jan  8 15:00:13.641: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.108488565s
Jan  8 15:00:15.640: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.10782066s
... skipping 440 lines ...
Jan  8 15:14:57.642: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.109819046s
Jan  8 15:14:59.645: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.112656265s
Jan  8 15:15:01.643: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.110187616s
Jan  8 15:15:03.643: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.110381139s
Jan  8 15:15:05.644: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.11123391s
Jan  8 15:15:05.698: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.16582229s
Jan  8 15:15:05.700: INFO: Unexpected error: 
    <*pod.timeoutError | 0xc000213d10>: {
        msg: "timed out while waiting for pod azuredisk-2540/azuredisk-volume-tester-pfrq5 to be Succeeded or Failed",
        observedObjects: [
            <*v1.Pod | 0xc000a0a480>{
                TypeMeta: {Kind: "", APIVersion: ""},
                ObjectMeta: {
                    Name: "azuredisk-volume-tester-pfrq5",
                    GenerateName: "azuredisk-volume-tester-",
... skipping 138 lines ...
Gomega truncated this representation as it exceeds 'format.MaxLength'.
Consider having the object provide a custom 'GomegaStringer' representation
or adjust the parameters in Gomega's 'format' package.

Learn more here: https://onsi.github.io/gomega/#adjusting-output

Jan  8 15:15:05.700: FAIL: timed out while waiting for pod azuredisk-2540/azuredisk-volume-tester-pfrq5 to be Succeeded or Failed

Full Stack Trace
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForSuccess(0x224d359?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823 +0x5d
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedVolumeSubpathTester).Run(0xc000ac1f08, {0x270a780, 0xc000676000}, 0x11?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_volume_subpath_tester.go:47 +0x1af
sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func3()
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:184 +0x3cc
Jan  8 15:15:05.700: INFO: deleting Pod "azuredisk-2540"/"azuredisk-volume-tester-pfrq5"
Jan  8 15:15:05.796: INFO: Error getting logs for pod azuredisk-volume-tester-pfrq5: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-pfrq5)
STEP: Deleting pod azuredisk-volume-tester-pfrq5 in namespace azuredisk-2540 01/08/23 15:15:05.796
Jan  8 15:15:05.854: INFO: deleting PVC "azuredisk-2540"/"pvc-hvfrz"
Jan  8 15:15:05.854: INFO: Deleting PersistentVolumeClaim "pvc-hvfrz"
STEP: waiting for claim's PV "pvc-14feefe6-77cc-45f6-811f-282fac47b219" to be deleted 01/08/23 15:15:05.919
Jan  8 15:15:05.919: INFO: Waiting up to 10m0s for PersistentVolume pvc-14feefe6-77cc-45f6-811f-282fac47b219 to get deleted
Jan  8 15:15:05.973: INFO: PersistentVolume pvc-14feefe6-77cc-45f6-811f-282fac47b219 found and phase=Bound (53.896407ms)
... skipping 3 lines ...
Jan  8 15:15:21.147: INFO: Waiting up to 5m0s for PersistentVolumeClaim azuredisk-2540 to be removed
Jan  8 15:15:21.201: INFO: Claim "azuredisk-2540" in namespace "pvc-hvfrz" doesn't exist in the system
Jan  8 15:15:21.201: INFO: deleting StorageClass azuredisk-2540-disk.csi.azure.com-dynamic-sc-8mn9x
STEP: dump namespace information after failure 01/08/23 15:15:21.256
STEP: Destroying namespace "azuredisk-2540" for this suite. 01/08/23 15:15:21.257
------------------------------
• [FAILED] [921.101 seconds]
Dynamic Provisioning
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:41
  [multi-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:48
    [It] should create a pod with volume mount subpath [disk.csi.azure.com] [Windows]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:152
... skipping 15 lines ...
    Jan  8 15:00:03.308: INFO: PersistentVolumeClaim pvc-hvfrz found but phase is Pending instead of Bound.
    Jan  8 15:00:05.365: INFO: PersistentVolumeClaim pvc-hvfrz found and phase=Bound (4.166423716s)
    STEP: checking the PVC 01/08/23 15:00:05.365
    STEP: validating provisioned PV 01/08/23 15:00:05.421
    STEP: checking the PV 01/08/23 15:00:05.475
    STEP: deploying the pod 01/08/23 15:00:05.475
    STEP: checking that the pods command exits with no error 01/08/23 15:00:05.532
    Jan  8 15:00:05.532: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-pfrq5" in namespace "azuredisk-2540" to be "Succeeded or Failed"
    Jan  8 15:00:05.587: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 54.762178ms
    Jan  8 15:00:07.641: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.1083686s
    Jan  8 15:00:09.640: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.107837633s
    Jan  8 15:00:11.641: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.109089556s
    Jan  8 15:00:13.641: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 8.108488565s
    Jan  8 15:00:15.640: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 10.10782066s
... skipping 440 lines ...
    Jan  8 15:14:57.642: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.109819046s
    Jan  8 15:14:59.645: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.112656265s
    Jan  8 15:15:01.643: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.110187616s
    Jan  8 15:15:03.643: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.110381139s
    Jan  8 15:15:05.644: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.11123391s
    Jan  8 15:15:05.698: INFO: Pod "azuredisk-volume-tester-pfrq5": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.16582229s
    Jan  8 15:15:05.700: INFO: Unexpected error: 
        <*pod.timeoutError | 0xc000213d10>: {
            msg: "timed out while waiting for pod azuredisk-2540/azuredisk-volume-tester-pfrq5 to be Succeeded or Failed",
            observedObjects: [
                <*v1.Pod | 0xc000a0a480>{
                    TypeMeta: {Kind: "", APIVersion: ""},
                    ObjectMeta: {
                        Name: "azuredisk-volume-tester-pfrq5",
                        GenerateName: "azuredisk-volume-tester-",
... skipping 138 lines ...
    Gomega truncated this representation as it exceeds 'format.MaxLength'.
    Consider having the object provide a custom 'GomegaStringer' representation
    or adjust the parameters in Gomega's 'format' package.

    Learn more here: https://onsi.github.io/gomega/#adjusting-output

    Jan  8 15:15:05.700: FAIL: timed out while waiting for pod azuredisk-2540/azuredisk-volume-tester-pfrq5 to be Succeeded or Failed

    Full Stack Trace
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForSuccess(0x224d359?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823 +0x5d
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedVolumeSubpathTester).Run(0xc000ac1f08, {0x270a780, 0xc000676000}, 0x11?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_volume_subpath_tester.go:47 +0x1af
    sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func3()
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:184 +0x3cc
    Jan  8 15:15:05.700: INFO: deleting Pod "azuredisk-2540"/"azuredisk-volume-tester-pfrq5"
    Jan  8 15:15:05.796: INFO: Error getting logs for pod azuredisk-volume-tester-pfrq5: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-pfrq5)
    STEP: Deleting pod azuredisk-volume-tester-pfrq5 in namespace azuredisk-2540 01/08/23 15:15:05.796
    Jan  8 15:15:05.854: INFO: deleting PVC "azuredisk-2540"/"pvc-hvfrz"
    Jan  8 15:15:05.854: INFO: Deleting PersistentVolumeClaim "pvc-hvfrz"
    STEP: waiting for claim's PV "pvc-14feefe6-77cc-45f6-811f-282fac47b219" to be deleted 01/08/23 15:15:05.919
    Jan  8 15:15:05.919: INFO: Waiting up to 10m0s for PersistentVolume pvc-14feefe6-77cc-45f6-811f-282fac47b219 to get deleted
    Jan  8 15:15:05.973: INFO: PersistentVolume pvc-14feefe6-77cc-45f6-811f-282fac47b219 found and phase=Bound (53.896407ms)
... skipping 4 lines ...
    Jan  8 15:15:21.201: INFO: Claim "azuredisk-2540" in namespace "pvc-hvfrz" doesn't exist in the system
    Jan  8 15:15:21.201: INFO: deleting StorageClass azuredisk-2540-disk.csi.azure.com-dynamic-sc-8mn9x
    STEP: dump namespace information after failure 01/08/23 15:15:21.256
    STEP: Destroying namespace "azuredisk-2540" for this suite. 01/08/23 15:15:21.257
  << End Captured GinkgoWriter Output

  Jan  8 15:15:05.700: timed out while waiting for pod azuredisk-2540/azuredisk-volume-tester-pfrq5 to be Succeeded or Failed
  In [It] at: /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823

  There were additional failures detected after the initial failure:
    [PANICKED]
    Test Panicked
    In [DeferCleanup (Each)] at: /usr/local/go/src/runtime/panic.go:260

    runtime error: invalid memory address or nil pointer dereference

    Full Stack Trace
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo.func1()
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:274 +0x5c
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo(0xc00003c3c0)
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:271 +0x179
... skipping 18 lines ...
STEP: setting up the StorageClass 01/08/23 15:15:22.162
STEP: creating a StorageClass  01/08/23 15:15:22.163
STEP: setting up the PVC and PV 01/08/23 15:15:22.219
STEP: creating a PVC 01/08/23 15:15:22.219
STEP: setting up the pod 01/08/23 15:15:22.276
STEP: deploying the pod 01/08/23 15:15:22.276
STEP: checking that the pod's command exits with no error 01/08/23 15:15:22.332
Jan  8 15:15:22.332: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-79dbl" in namespace "azuredisk-4728" to be "Succeeded or Failed"
Jan  8 15:15:22.387: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 54.645621ms
Jan  8 15:15:24.444: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.111556291s
Jan  8 15:15:26.444: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.112127335s
Jan  8 15:15:28.443: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.110401613s
Jan  8 15:15:30.445: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.112289924s
Jan  8 15:15:32.443: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.111141555s
... skipping 440 lines ...
Jan  8 15:30:14.442: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.1096503s
Jan  8 15:30:16.441: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.108844274s
Jan  8 15:30:18.442: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.109860625s
Jan  8 15:30:20.443: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.110556607s
Jan  8 15:30:22.443: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.110213946s
Jan  8 15:30:22.496: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.164079552s
Jan  8 15:30:22.498: INFO: Unexpected error: 
    <*pod.timeoutError | 0xc000bbd380>: {
        msg: "timed out while waiting for pod azuredisk-4728/azuredisk-volume-tester-79dbl to be Succeeded or Failed",
        observedObjects: [
            <*v1.Pod | 0xc000a0a480>{
                TypeMeta: {Kind: "", APIVersion: ""},
                ObjectMeta: {
                    Name: "azuredisk-volume-tester-79dbl",
                    GenerateName: "azuredisk-volume-tester-",
... skipping 138 lines ...
Gomega truncated this representation as it exceeds 'format.MaxLength'.
Consider having the object provide a custom 'GomegaStringer' representation
or adjust the parameters in Gomega's 'format' package.

Learn more here: https://onsi.github.io/gomega/#adjusting-output

Jan  8 15:30:22.498: FAIL: timed out while waiting for pod azuredisk-4728/azuredisk-volume-tester-79dbl to be Succeeded or Failed

Full Stack Trace
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForSuccess(0x2250591?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823 +0x5d
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedCmdVolumeTest).Run(0xc000ae1d38, {0x270a780, 0xc0006776c0}, 0x11?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_cmd_volume_tester.go:48 +0x1af
sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func4()
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:220 +0x638
Jan  8 15:30:22.498: INFO: deleting Pod "azuredisk-4728"/"azuredisk-volume-tester-79dbl"
Jan  8 15:30:22.603: INFO: Error getting logs for pod azuredisk-volume-tester-79dbl: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-79dbl)
STEP: Deleting pod azuredisk-volume-tester-79dbl in namespace azuredisk-4728 01/08/23 15:30:22.604
STEP: validating provisioned PV 01/08/23 15:30:22.716
STEP: checking the PV 01/08/23 15:30:22.771
Jan  8 15:30:22.772: INFO: deleting PVC "azuredisk-4728"/"pvc-6sxjm"
Jan  8 15:30:22.772: INFO: Deleting PersistentVolumeClaim "pvc-6sxjm"
STEP: waiting for claim's PV "pvc-ad2a4ee8-79af-476a-9777-d3753a0989c3" to be deleted 01/08/23 15:30:22.828
... skipping 6 lines ...
Jan  8 15:30:43.110: INFO: Waiting up to 5m0s for PersistentVolumeClaim azuredisk-4728 to be removed
Jan  8 15:30:43.163: INFO: Claim "azuredisk-4728" in namespace "pvc-6sxjm" doesn't exist in the system
Jan  8 15:30:43.163: INFO: deleting StorageClass azuredisk-4728-disk.csi.azure.com-dynamic-sc-g9qt8
STEP: dump namespace information after failure 01/08/23 15:30:43.22
STEP: Destroying namespace "azuredisk-4728" for this suite. 01/08/23 15:30:43.221
------------------------------
• [FAILED] [921.964 seconds]
Dynamic Provisioning
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:41
  [multi-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:48
    [It] Should create and attach a volume with basic perfProfile [enableBursting][disk.csi.azure.com] [Windows]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:187
... skipping 8 lines ...
    STEP: setting up the StorageClass 01/08/23 15:15:22.162
    STEP: creating a StorageClass  01/08/23 15:15:22.163
    STEP: setting up the PVC and PV 01/08/23 15:15:22.219
    STEP: creating a PVC 01/08/23 15:15:22.219
    STEP: setting up the pod 01/08/23 15:15:22.276
    STEP: deploying the pod 01/08/23 15:15:22.276
    STEP: checking that the pod's command exits with no error 01/08/23 15:15:22.332
    Jan  8 15:15:22.332: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-79dbl" in namespace "azuredisk-4728" to be "Succeeded or Failed"
    Jan  8 15:15:22.387: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 54.645621ms
    Jan  8 15:15:24.444: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 2.111556291s
    Jan  8 15:15:26.444: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 4.112127335s
    Jan  8 15:15:28.443: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 6.110401613s
    Jan  8 15:15:30.445: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 8.112289924s
    Jan  8 15:15:32.443: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 10.111141555s
... skipping 440 lines ...
    Jan  8 15:30:14.442: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.1096503s
    Jan  8 15:30:16.441: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.108844274s
    Jan  8 15:30:18.442: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.109860625s
    Jan  8 15:30:20.443: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.110556607s
    Jan  8 15:30:22.443: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.110213946s
    Jan  8 15:30:22.496: INFO: Pod "azuredisk-volume-tester-79dbl": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.164079552s
    Jan  8 15:30:22.498: INFO: Unexpected error: 
        <*pod.timeoutError | 0xc000bbd380>: {
            msg: "timed out while waiting for pod azuredisk-4728/azuredisk-volume-tester-79dbl to be Succeeded or Failed",
            observedObjects: [
                <*v1.Pod | 0xc000a0a480>{
                    TypeMeta: {Kind: "", APIVersion: ""},
                    ObjectMeta: {
                        Name: "azuredisk-volume-tester-79dbl",
                        GenerateName: "azuredisk-volume-tester-",
... skipping 138 lines ...
    Gomega truncated this representation as it exceeds 'format.MaxLength'.
    Consider having the object provide a custom 'GomegaStringer' representation
    or adjust the parameters in Gomega's 'format' package.

    Learn more here: https://onsi.github.io/gomega/#adjusting-output

    Jan  8 15:30:22.498: FAIL: timed out while waiting for pod azuredisk-4728/azuredisk-volume-tester-79dbl to be Succeeded or Failed

    Full Stack Trace
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForSuccess(0x2250591?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823 +0x5d
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedCmdVolumeTest).Run(0xc000ae1d38, {0x270a780, 0xc0006776c0}, 0x11?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_cmd_volume_tester.go:48 +0x1af
    sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func4()
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:220 +0x638
    Jan  8 15:30:22.498: INFO: deleting Pod "azuredisk-4728"/"azuredisk-volume-tester-79dbl"
    Jan  8 15:30:22.603: INFO: Error getting logs for pod azuredisk-volume-tester-79dbl: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-79dbl)
    STEP: Deleting pod azuredisk-volume-tester-79dbl in namespace azuredisk-4728 01/08/23 15:30:22.604
    STEP: validating provisioned PV 01/08/23 15:30:22.716
    STEP: checking the PV 01/08/23 15:30:22.771
    Jan  8 15:30:22.772: INFO: deleting PVC "azuredisk-4728"/"pvc-6sxjm"
    Jan  8 15:30:22.772: INFO: Deleting PersistentVolumeClaim "pvc-6sxjm"
    STEP: waiting for claim's PV "pvc-ad2a4ee8-79af-476a-9777-d3753a0989c3" to be deleted 01/08/23 15:30:22.828
... skipping 7 lines ...
    Jan  8 15:30:43.163: INFO: Claim "azuredisk-4728" in namespace "pvc-6sxjm" doesn't exist in the system
    Jan  8 15:30:43.163: INFO: deleting StorageClass azuredisk-4728-disk.csi.azure.com-dynamic-sc-g9qt8
    STEP: dump namespace information after failure 01/08/23 15:30:43.22
    STEP: Destroying namespace "azuredisk-4728" for this suite. 01/08/23 15:30:43.221
  << End Captured GinkgoWriter Output

  Jan  8 15:30:22.498: timed out while waiting for pod azuredisk-4728/azuredisk-volume-tester-79dbl to be Succeeded or Failed
  In [It] at: /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823

  There were additional failures detected after the initial failure:
    [PANICKED]
    Test Panicked
    In [DeferCleanup (Each)] at: /usr/local/go/src/runtime/panic.go:260

    runtime error: invalid memory address or nil pointer dereference

    Full Stack Trace
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo.func1()
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:274 +0x5c
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo(0xc00003c3c0)
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:271 +0x179
... skipping 19 lines ...
STEP: creating a StorageClass  01/08/23 15:30:44.147
STEP: setting up the PVC and PV 01/08/23 15:30:44.203
STEP: creating a PVC 01/08/23 15:30:44.204
STEP: setting up the pod 01/08/23 15:30:44.261
STEP: deploying the pod 01/08/23 15:30:44.261
STEP: checking that the pod has 'FailedMount' event 01/08/23 15:30:44.317
Jan  8 15:35:44.481: INFO: Unexpected error: 
    <*errors.errorString | 0xc000284a40>: {
        s: "timed out waiting for the condition",
    }
Jan  8 15:35:44.482: FAIL: timed out waiting for the condition

Full Stack Trace
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForFailedMountError(0xc000e4a880)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:843 +0x33e
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedInvalidMountOptions).Run(0xc0009efd38, {0x270a780, 0xc000677520}, 0x7?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_invalid_mount_options.go:47 +0x1af
sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func5()
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:257 +0x5dc
Jan  8 15:35:44.482: INFO: deleting Pod "azuredisk-5466"/"azuredisk-volume-tester-7jr9v"
Jan  8 15:35:44.574: INFO: Error getting logs for pod azuredisk-volume-tester-7jr9v: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-7jr9v)
STEP: Deleting pod azuredisk-volume-tester-7jr9v in namespace azuredisk-5466 01/08/23 15:35:44.574
STEP: validating provisioned PV 01/08/23 15:35:44.685
STEP: checking the PV 01/08/23 15:35:44.74
Jan  8 15:35:44.740: INFO: deleting PVC "azuredisk-5466"/"pvc-brkrt"
Jan  8 15:35:44.740: INFO: Deleting PersistentVolumeClaim "pvc-brkrt"
STEP: waiting for claim's PV "pvc-d4607bcb-52ee-462c-b5a7-b254d46ce467" to be deleted 01/08/23 15:35:44.796
... skipping 7 lines ...
Jan  8 15:36:10.139: INFO: Waiting up to 5m0s for PersistentVolumeClaim azuredisk-5466 to be removed
Jan  8 15:36:10.193: INFO: Claim "azuredisk-5466" in namespace "pvc-brkrt" doesn't exist in the system
Jan  8 15:36:10.193: INFO: deleting StorageClass azuredisk-5466-disk.csi.azure.com-dynamic-sc-9rqk7
STEP: dump namespace information after failure 01/08/23 15:36:10.249
STEP: Destroying namespace "azuredisk-5466" for this suite. 01/08/23 15:36:10.249
------------------------------
• [FAILED] [327.029 seconds]
Dynamic Provisioning
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:41
  [multi-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:48
    [It] should receive FailedMount event with invalid mount options [kubernetes.io/azure-disk] [disk.csi.azure.com]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:223
... skipping 9 lines ...
    STEP: creating a StorageClass  01/08/23 15:30:44.147
    STEP: setting up the PVC and PV 01/08/23 15:30:44.203
    STEP: creating a PVC 01/08/23 15:30:44.204
    STEP: setting up the pod 01/08/23 15:30:44.261
    STEP: deploying the pod 01/08/23 15:30:44.261
    STEP: checking that the pod has 'FailedMount' event 01/08/23 15:30:44.317
    Jan  8 15:35:44.481: INFO: Unexpected error: 
        <*errors.errorString | 0xc000284a40>: {
            s: "timed out waiting for the condition",
        }
    Jan  8 15:35:44.482: FAIL: timed out waiting for the condition

    Full Stack Trace
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForFailedMountError(0xc000e4a880)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:843 +0x33e
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedInvalidMountOptions).Run(0xc0009efd38, {0x270a780, 0xc000677520}, 0x7?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_invalid_mount_options.go:47 +0x1af
    sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func5()
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:257 +0x5dc
    Jan  8 15:35:44.482: INFO: deleting Pod "azuredisk-5466"/"azuredisk-volume-tester-7jr9v"
    Jan  8 15:35:44.574: INFO: Error getting logs for pod azuredisk-volume-tester-7jr9v: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-7jr9v)
    STEP: Deleting pod azuredisk-volume-tester-7jr9v in namespace azuredisk-5466 01/08/23 15:35:44.574
    STEP: validating provisioned PV 01/08/23 15:35:44.685
    STEP: checking the PV 01/08/23 15:35:44.74
    Jan  8 15:35:44.740: INFO: deleting PVC "azuredisk-5466"/"pvc-brkrt"
    Jan  8 15:35:44.740: INFO: Deleting PersistentVolumeClaim "pvc-brkrt"
    STEP: waiting for claim's PV "pvc-d4607bcb-52ee-462c-b5a7-b254d46ce467" to be deleted 01/08/23 15:35:44.796
... skipping 16 lines ...

  There were additional failures detected after the initial failure:
    [PANICKED]
    Test Panicked
    In [DeferCleanup (Each)] at: /usr/local/go/src/runtime/panic.go:260

    runtime error: invalid memory address or nil pointer dereference

    Full Stack Trace
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo.func1()
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:274 +0x5c
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo(0xc00003c3c0)
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:271 +0x179
... skipping 18 lines ...
STEP: setting up the StorageClass 01/08/23 15:36:11.166
STEP: creating a StorageClass  01/08/23 15:36:11.166
STEP: setting up the PVC and PV 01/08/23 15:36:11.223
STEP: creating a PVC 01/08/23 15:36:11.223
STEP: setting up the pod 01/08/23 15:36:11.281
STEP: deploying the pod 01/08/23 15:36:11.281
STEP: checking that the pod's command exits with no error 01/08/23 15:36:11.336
Jan  8 15:36:11.336: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-lt2mr" in namespace "azuredisk-2790" to be "Succeeded or Failed"
Jan  8 15:36:11.390: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 53.851487ms
Jan  8 15:36:13.448: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.111073382s
Jan  8 15:36:15.446: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.109224339s
Jan  8 15:36:17.447: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.110026339s
Jan  8 15:36:19.446: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.109383799s
Jan  8 15:36:21.445: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.108959552s
... skipping 440 lines ...
Jan  8 15:51:03.446: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.109730568s
Jan  8 15:51:05.450: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.113814352s
Jan  8 15:51:07.445: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.10887429s
Jan  8 15:51:09.447: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.110462235s
Jan  8 15:51:11.449: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.112033536s
Jan  8 15:51:11.503: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.166331951s
Jan  8 15:51:11.504: INFO: Unexpected error: 
    <*pod.timeoutError | 0xc000a217d0>: {
        msg: "timed out while waiting for pod azuredisk-2790/azuredisk-volume-tester-lt2mr to be Succeeded or Failed",
        observedObjects: [
            <*v1.Pod | 0xc00065d680>{
                TypeMeta: {Kind: "", APIVersion: ""},
                ObjectMeta: {
                    Name: "azuredisk-volume-tester-lt2mr",
                    GenerateName: "azuredisk-volume-tester-",
... skipping 138 lines ...
Gomega truncated this representation as it exceeds 'format.MaxLength'.
Consider having the object provide a custom 'GomegaStringer' representation
or adjust the parameters in Gomega's 'format' package.

Learn more here: https://onsi.github.io/gomega/#adjusting-output

Jan  8 15:51:11.504: FAIL: timed out while waiting for pod azuredisk-2790/azuredisk-volume-tester-lt2mr to be Succeeded or Failed

Full Stack Trace
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForSuccess(0x2250591?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823 +0x5d
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedCmdVolumeTest).Run(0xc0006d9d38, {0x270a780, 0xc00049c9c0}, 0x7?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_cmd_volume_tester.go:48 +0x1af
sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func6()
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:288 +0x44b
Jan  8 15:51:11.505: INFO: deleting Pod "azuredisk-2790"/"azuredisk-volume-tester-lt2mr"
Jan  8 15:51:11.593: INFO: Error getting logs for pod azuredisk-volume-tester-lt2mr: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-lt2mr)
STEP: Deleting pod azuredisk-volume-tester-lt2mr in namespace azuredisk-2790 01/08/23 15:51:11.593
STEP: validating provisioned PV 01/08/23 15:51:11.703
STEP: checking the PV 01/08/23 15:51:11.757
Jan  8 15:51:11.757: INFO: deleting PVC "azuredisk-2790"/"pvc-8b6np"
Jan  8 15:51:11.757: INFO: Deleting PersistentVolumeClaim "pvc-8b6np"
STEP: waiting for claim's PV "pvc-d02a05bc-8499-447c-bcc9-66f45c081ece" to be deleted 01/08/23 15:51:11.812
... skipping 7 lines ...
Jan  8 15:51:37.149: INFO: Waiting up to 5m0s for PersistentVolumeClaim azuredisk-2790 to be removed
Jan  8 15:51:37.203: INFO: Claim "azuredisk-2790" in namespace "pvc-8b6np" doesn't exist in the system
Jan  8 15:51:37.203: INFO: deleting StorageClass azuredisk-2790-disk.csi.azure.com-dynamic-sc-rvm2d
STEP: dump namespace information after failure 01/08/23 15:51:37.26
STEP: Destroying namespace "azuredisk-2790" for this suite. 01/08/23 15:51:37.26
------------------------------
• [FAILED] [927.006 seconds]
Dynamic Provisioning
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:41
  [multi-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:48
    [It] should create a raw block volume on demand [kubernetes.io/azure-disk] [disk.csi.azure.com]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:260
... skipping 8 lines ...
    STEP: setting up the StorageClass 01/08/23 15:36:11.166
    STEP: creating a StorageClass  01/08/23 15:36:11.166
    STEP: setting up the PVC and PV 01/08/23 15:36:11.223
    STEP: creating a PVC 01/08/23 15:36:11.223
    STEP: setting up the pod 01/08/23 15:36:11.281
    STEP: deploying the pod 01/08/23 15:36:11.281
    STEP: checking that the pod's command exits with no error 01/08/23 15:36:11.336
    Jan  8 15:36:11.336: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-lt2mr" in namespace "azuredisk-2790" to be "Succeeded or Failed"
    Jan  8 15:36:11.390: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 53.851487ms
    Jan  8 15:36:13.448: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 2.111073382s
    Jan  8 15:36:15.446: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 4.109224339s
    Jan  8 15:36:17.447: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 6.110026339s
    Jan  8 15:36:19.446: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 8.109383799s
    Jan  8 15:36:21.445: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 10.108959552s
... skipping 440 lines ...
    Jan  8 15:51:03.446: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.109730568s
    Jan  8 15:51:05.450: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.113814352s
    Jan  8 15:51:07.445: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.10887429s
    Jan  8 15:51:09.447: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.110462235s
    Jan  8 15:51:11.449: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.112033536s
    Jan  8 15:51:11.503: INFO: Pod "azuredisk-volume-tester-lt2mr": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.166331951s
    Jan  8 15:51:11.504: INFO: Unexpected error: 
        <*pod.timeoutError | 0xc000a217d0>: {
            msg: "timed out while waiting for pod azuredisk-2790/azuredisk-volume-tester-lt2mr to be Succeeded or Failed",
            observedObjects: [
                <*v1.Pod | 0xc00065d680>{
                    TypeMeta: {Kind: "", APIVersion: ""},
                    ObjectMeta: {
                        Name: "azuredisk-volume-tester-lt2mr",
                        GenerateName: "azuredisk-volume-tester-",
... skipping 138 lines ...
    Gomega truncated this representation as it exceeds 'format.MaxLength'.
    Consider having the object provide a custom 'GomegaStringer' representation
    or adjust the parameters in Gomega's 'format' package.

    Learn more here: https://onsi.github.io/gomega/#adjusting-output

    Jan  8 15:51:11.504: FAIL: timed out while waiting for pod azuredisk-2790/azuredisk-volume-tester-lt2mr to be Succeeded or Failed

    Full Stack Trace
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForSuccess(0x2250591?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823 +0x5d
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedCmdVolumeTest).Run(0xc0006d9d38, {0x270a780, 0xc00049c9c0}, 0x7?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_cmd_volume_tester.go:48 +0x1af
    sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func6()
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:288 +0x44b
    Jan  8 15:51:11.505: INFO: deleting Pod "azuredisk-2790"/"azuredisk-volume-tester-lt2mr"
    Jan  8 15:51:11.593: INFO: Error getting logs for pod azuredisk-volume-tester-lt2mr: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-lt2mr)
    STEP: Deleting pod azuredisk-volume-tester-lt2mr in namespace azuredisk-2790 01/08/23 15:51:11.593
    STEP: validating provisioned PV 01/08/23 15:51:11.703
    STEP: checking the PV 01/08/23 15:51:11.757
    Jan  8 15:51:11.757: INFO: deleting PVC "azuredisk-2790"/"pvc-8b6np"
    Jan  8 15:51:11.757: INFO: Deleting PersistentVolumeClaim "pvc-8b6np"
    STEP: waiting for claim's PV "pvc-d02a05bc-8499-447c-bcc9-66f45c081ece" to be deleted 01/08/23 15:51:11.812
... skipping 8 lines ...
    Jan  8 15:51:37.203: INFO: Claim "azuredisk-2790" in namespace "pvc-8b6np" doesn't exist in the system
    Jan  8 15:51:37.203: INFO: deleting StorageClass azuredisk-2790-disk.csi.azure.com-dynamic-sc-rvm2d
    STEP: dump namespace information after failure 01/08/23 15:51:37.26
    STEP: Destroying namespace "azuredisk-2790" for this suite. 01/08/23 15:51:37.26
  << End Captured GinkgoWriter Output

  Jan  8 15:51:11.504: timed out while waiting for pod azuredisk-2790/azuredisk-volume-tester-lt2mr to be Succeeded or Failed
  In [It] at: /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823

  There were additional failures detected after the initial failure:
    [PANICKED]
    Test Panicked
    In [DeferCleanup (Each)] at: /usr/local/go/src/runtime/panic.go:260

    runtime error: invalid memory address or nil pointer dereference

    Full Stack Trace
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo.func1()
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:274 +0x5c
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo(0xc00003c3c0)
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:271 +0x179
... skipping 23 lines ...
STEP: creating volume in external rg azuredisk-csi-driver-test-56154025-8f6c-11ed-919b-92557cbc817b 01/08/23 15:51:39.675
STEP: setting up the StorageClass 01/08/23 15:51:39.675
STEP: creating a StorageClass  01/08/23 15:51:39.675
STEP: setting up the PVC and PV 01/08/23 15:51:39.731
STEP: creating a PVC 01/08/23 15:51:39.732
STEP: deploying the pod 01/08/23 15:51:39.799
STEP: checking that the pod's command exits with no error 01/08/23 15:51:39.855
Jan  8 15:51:39.855: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-f85mk" in namespace "azuredisk-5356" to be "Succeeded or Failed"
Jan  8 15:51:39.910: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 54.320749ms
Jan  8 15:51:41.965: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.109702709s
Jan  8 15:51:43.966: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.110391899s
Jan  8 15:51:45.965: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.109903524s
Jan  8 15:51:47.965: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.109205417s
Jan  8 15:51:49.965: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.109290343s
... skipping 440 lines ...
Jan  8 16:06:31.965: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.1093833s
Jan  8 16:06:33.968: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.113178817s
Jan  8 16:06:35.966: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.110595038s
Jan  8 16:06:37.967: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.111666871s
Jan  8 16:06:39.968: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.112656077s
Jan  8 16:06:40.023: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.167572154s
Jan  8 16:06:40.024: INFO: Unexpected error: 
    <*pod.timeoutError | 0xc000bbd350>: {
        msg: "timed out while waiting for pod azuredisk-5356/azuredisk-volume-tester-f85mk to be Succeeded or Failed",
        observedObjects: [
            <*v1.Pod | 0xc000e7ed80>{
                TypeMeta: {Kind: "", APIVersion: ""},
                ObjectMeta: {
                    Name: "azuredisk-volume-tester-f85mk",
                    GenerateName: "azuredisk-volume-tester-",
... skipping 138 lines ...
Gomega truncated this representation as it exceeds 'format.MaxLength'.
Consider having the object provide a custom 'GomegaStringer' representation
or adjust the parameters in Gomega's 'format' package.

Learn more here: https://onsi.github.io/gomega/#adjusting-output

Jan  8 16:06:40.024: FAIL: timed out while waiting for pod azuredisk-5356/azuredisk-volume-tester-f85mk to be Succeeded or Failed

Full Stack Trace
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForSuccess(0x2250591?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823 +0x5d
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedExternalRgVolumeTest).Run(0xc000e45cc8, {0x270a780, 0xc00049cb60}, 0x7?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_external_rg_volume_tester.go:103 +0x3c5
sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func7()
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:320 +0x57c
Jan  8 16:06:40.025: INFO: deleting Pod "azuredisk-5356"/"azuredisk-volume-tester-f85mk"
Jan  8 16:06:40.120: INFO: Error getting logs for pod azuredisk-volume-tester-f85mk: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-f85mk)
STEP: Deleting pod azuredisk-volume-tester-f85mk in namespace azuredisk-5356 01/08/23 16:06:40.12
STEP: validating provisioned PV 01/08/23 16:06:40.239
STEP: checking the PV 01/08/23 16:06:40.294
Jan  8 16:06:40.294: INFO: deleting PVC "azuredisk-5356"/"pvc-vtf2x"
Jan  8 16:06:40.294: INFO: Deleting PersistentVolumeClaim "pvc-vtf2x"
STEP: waiting for claim's PV "pvc-446ea8a3-b4e2-4cc4-bd97-9b059aebcb5e" to be deleted 01/08/23 16:06:40.354
... skipping 9 lines ...
Jan  8 16:07:10.815: INFO: Claim "azuredisk-5356" in namespace "pvc-vtf2x" doesn't exist in the system
Jan  8 16:07:10.815: INFO: deleting StorageClass azuredisk-5356-disk.csi.azure.com-dynamic-sc-84gsp
Jan  8 16:07:10.871: INFO: Deleting resource group azuredisk-csi-driver-test-56154025-8f6c-11ed-919b-92557cbc817b
STEP: dump namespace information after failure 01/08/23 16:07:27.473
STEP: Destroying namespace "azuredisk-5356" for this suite. 01/08/23 16:07:27.474
------------------------------
• [FAILED] [950.214 seconds]
Dynamic Provisioning
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:41
  [multi-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:48
    [It] should create a volume in separate resource group and bind it to a pod [kubernetes.io/azure-disk] [disk.csi.azure.com]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:291
... skipping 11 lines ...
    STEP: creating volume in external rg azuredisk-csi-driver-test-56154025-8f6c-11ed-919b-92557cbc817b 01/08/23 15:51:39.675
    STEP: setting up the StorageClass 01/08/23 15:51:39.675
    STEP: creating a StorageClass  01/08/23 15:51:39.675
    STEP: setting up the PVC and PV 01/08/23 15:51:39.731
    STEP: creating a PVC 01/08/23 15:51:39.732
    STEP: deploying the pod 01/08/23 15:51:39.799
    STEP: checking that the pod's command exits with no error 01/08/23 15:51:39.855
    Jan  8 15:51:39.855: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-f85mk" in namespace "azuredisk-5356" to be "Succeeded or Failed"
    Jan  8 15:51:39.910: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 54.320749ms
    Jan  8 15:51:41.965: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.109702709s
    Jan  8 15:51:43.966: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.110391899s
    Jan  8 15:51:45.965: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.109903524s
    Jan  8 15:51:47.965: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.109205417s
    Jan  8 15:51:49.965: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.109290343s
... skipping 440 lines ...
    Jan  8 16:06:31.965: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.1093833s
    Jan  8 16:06:33.968: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.113178817s
    Jan  8 16:06:35.966: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.110595038s
    Jan  8 16:06:37.967: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.111666871s
    Jan  8 16:06:39.968: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.112656077s
    Jan  8 16:06:40.023: INFO: Pod "azuredisk-volume-tester-f85mk": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.167572154s
    Jan  8 16:06:40.024: INFO: Unexpected error: 
        <*pod.timeoutError | 0xc000bbd350>: {
            msg: "timed out while waiting for pod azuredisk-5356/azuredisk-volume-tester-f85mk to be Succeeded or Failed",
            observedObjects: [
                <*v1.Pod | 0xc000e7ed80>{
                    TypeMeta: {Kind: "", APIVersion: ""},
                    ObjectMeta: {
                        Name: "azuredisk-volume-tester-f85mk",
                        GenerateName: "azuredisk-volume-tester-",
... skipping 138 lines ...
    Gomega truncated this representation as it exceeds 'format.MaxLength'.
    Consider having the object provide a custom 'GomegaStringer' representation
    or adjust the parameters in Gomega's 'format' package.

    Learn more here: https://onsi.github.io/gomega/#adjusting-output

    Jan  8 16:06:40.024: FAIL: timed out while waiting for pod azuredisk-5356/azuredisk-volume-tester-f85mk to be Succeeded or Failed

    Full Stack Trace
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForSuccess(0x2250591?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823 +0x5d
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedExternalRgVolumeTest).Run(0xc000e45cc8, {0x270a780, 0xc00049cb60}, 0x7?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_external_rg_volume_tester.go:103 +0x3c5
    sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func7()
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:320 +0x57c
    Jan  8 16:06:40.025: INFO: deleting Pod "azuredisk-5356"/"azuredisk-volume-tester-f85mk"
    Jan  8 16:06:40.120: INFO: Error getting logs for pod azuredisk-volume-tester-f85mk: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-f85mk)
    STEP: Deleting pod azuredisk-volume-tester-f85mk in namespace azuredisk-5356 01/08/23 16:06:40.12
    STEP: validating provisioned PV 01/08/23 16:06:40.239
    STEP: checking the PV 01/08/23 16:06:40.294
    Jan  8 16:06:40.294: INFO: deleting PVC "azuredisk-5356"/"pvc-vtf2x"
    Jan  8 16:06:40.294: INFO: Deleting PersistentVolumeClaim "pvc-vtf2x"
    STEP: waiting for claim's PV "pvc-446ea8a3-b4e2-4cc4-bd97-9b059aebcb5e" to be deleted 01/08/23 16:06:40.354
... skipping 10 lines ...
    Jan  8 16:07:10.815: INFO: deleting StorageClass azuredisk-5356-disk.csi.azure.com-dynamic-sc-84gsp
    Jan  8 16:07:10.871: INFO: Deleting resource group azuredisk-csi-driver-test-56154025-8f6c-11ed-919b-92557cbc817b
    STEP: dump namespace information after failure 01/08/23 16:07:27.473
    STEP: Destroying namespace "azuredisk-5356" for this suite. 01/08/23 16:07:27.474
  << End Captured GinkgoWriter Output

  Jan  8 16:06:40.025: timed out while waiting for pod azuredisk-5356/azuredisk-volume-tester-f85mk to be Succeeded or Failed
  In [It] at: /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823

  There were additional failures detected after the initial failure:
    [PANICKED]
    Test Panicked
    In [DeferCleanup (Each)] at: /usr/local/go/src/runtime/panic.go:260

    runtime error: invalid memory address or nil pointer dereference

    Full Stack Trace
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo.func1()
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:274 +0x5c
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo(0xc00003c3c0)
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:271 +0x179
... skipping 29 lines ...
STEP: creating volume in external rg azuredisk-csi-driver-test-8d41bad3-8f6e-11ed-919b-92557cbc817b 01/08/23 16:07:30.113
STEP: setting up the StorageClass 01/08/23 16:07:30.113
STEP: creating a StorageClass  01/08/23 16:07:30.113
STEP: setting up the PVC and PV 01/08/23 16:07:30.17
STEP: creating a PVC 01/08/23 16:07:30.17
STEP: deploying the pod 01/08/23 16:07:30.23
STEP: checking that the pod's command exits with no error 01/08/23 16:07:30.286
Jan  8 16:07:30.286: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-xt28p" in namespace "azuredisk-5194" to be "Succeeded or Failed"
Jan  8 16:07:30.341: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 54.860742ms
Jan  8 16:07:32.398: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.111508213s
Jan  8 16:07:34.401: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.114113175s
Jan  8 16:07:36.397: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.110294698s
Jan  8 16:07:38.398: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.111586117s
Jan  8 16:07:40.399: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.112375155s
... skipping 439 lines ...
Jan  8 16:22:22.397: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.110639722s
Jan  8 16:22:24.398: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.111235321s
Jan  8 16:22:26.396: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.109971529s
Jan  8 16:22:28.395: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.108903499s
Jan  8 16:22:30.396: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.109431709s
Jan  8 16:22:30.449: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.162255976s
Jan  8 16:22:30.450: INFO: Unexpected error: 
    <*pod.timeoutError | 0xc000ca4720>: {
        msg: "timed out while waiting for pod azuredisk-5194/azuredisk-volume-tester-xt28p to be Succeeded or Failed",
        observedObjects: [
            <*v1.Pod | 0xc000e24000>{
                TypeMeta: {Kind: "", APIVersion: ""},
                ObjectMeta: {
                    Name: "azuredisk-volume-tester-xt28p",
                    GenerateName: "azuredisk-volume-tester-",
... skipping 134 lines ...
Gomega truncated this representation as it exceeds 'format.MaxLength'.
Consider having the object provide a custom 'GomegaStringer' representation
or adjust the parameters in Gomega's 'format' package.

Learn more here: https://onsi.github.io/gomega/#adjusting-output

Jan  8 16:22:30.450: FAIL: timed out while waiting for pod azuredisk-5194/azuredisk-volume-tester-xt28p to be Succeeded or Failed

Full Stack Trace
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForSuccess(0x2250591?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823 +0x5d
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedExternalRgVolumeTest).Run(0xc000e5dcc8, {0x270a780, 0xc000b3ba00}, 0x7?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_external_rg_volume_tester.go:103 +0x3c5
sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func8()
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:361 +0x4dc
Jan  8 16:22:30.451: INFO: deleting Pod "azuredisk-5194"/"azuredisk-volume-tester-xt28p"
Jan  8 16:22:30.548: INFO: Error getting logs for pod azuredisk-volume-tester-xt28p: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-xt28p)
STEP: Deleting pod azuredisk-volume-tester-xt28p in namespace azuredisk-5194 01/08/23 16:22:30.548
STEP: validating provisioned PV 01/08/23 16:22:30.658
STEP: checking the PV 01/08/23 16:22:30.711
Jan  8 16:22:30.711: INFO: deleting PVC "azuredisk-5194"/"pvc-s66h4"
Jan  8 16:22:30.711: INFO: Deleting PersistentVolumeClaim "pvc-s66h4"
STEP: waiting for claim's PV "pvc-d984d210-0518-4a1b-b3b7-b7fef6523cf2" to be deleted 01/08/23 16:22:30.769
... skipping 22 lines ...
Jan  8 16:23:11.650: INFO: deleting StorageClass azuredisk-5194-disk.csi.azure.com-dynamic-sc-gwlhq
Jan  8 16:23:11.705: INFO: Deleting resource group azuredisk-csi-driver-test-8c84b2b6-8f6e-11ed-919b-92557cbc817b
Jan  8 16:23:28.430: INFO: Deleting resource group azuredisk-csi-driver-test-8d41bad3-8f6e-11ed-919b-92557cbc817b
STEP: dump namespace information after failure 01/08/23 16:23:44.081
STEP: Destroying namespace "azuredisk-5194" for this suite. 01/08/23 16:23:44.081
------------------------------
• [FAILED] [976.613 seconds]
Dynamic Provisioning
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:41
  [multi-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:48
    [It] should create multiple volumes, each in separate resource groups and attach them to a single pod [kubernetes.io/azure-disk] [disk.csi.azure.com]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:323
... skipping 17 lines ...
    STEP: creating volume in external rg azuredisk-csi-driver-test-8d41bad3-8f6e-11ed-919b-92557cbc817b 01/08/23 16:07:30.113
    STEP: setting up the StorageClass 01/08/23 16:07:30.113
    STEP: creating a StorageClass  01/08/23 16:07:30.113
    STEP: setting up the PVC and PV 01/08/23 16:07:30.17
    STEP: creating a PVC 01/08/23 16:07:30.17
    STEP: deploying the pod 01/08/23 16:07:30.23
    STEP: checking that the pod's command exits with no error 01/08/23 16:07:30.286
    Jan  8 16:07:30.286: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-xt28p" in namespace "azuredisk-5194" to be "Succeeded or Failed"
    Jan  8 16:07:30.341: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 54.860742ms
    Jan  8 16:07:32.398: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 2.111508213s
    Jan  8 16:07:34.401: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 4.114113175s
    Jan  8 16:07:36.397: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 6.110294698s
    Jan  8 16:07:38.398: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 8.111586117s
    Jan  8 16:07:40.399: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 10.112375155s
... skipping 439 lines ...
    Jan  8 16:22:22.397: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.110639722s
    Jan  8 16:22:24.398: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.111235321s
    Jan  8 16:22:26.396: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.109971529s
    Jan  8 16:22:28.395: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.108903499s
    Jan  8 16:22:30.396: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.109431709s
    Jan  8 16:22:30.449: INFO: Pod "azuredisk-volume-tester-xt28p": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.162255976s
    Jan  8 16:22:30.450: INFO: Unexpected error: 
        <*pod.timeoutError | 0xc000ca4720>: {
            msg: "timed out while waiting for pod azuredisk-5194/azuredisk-volume-tester-xt28p to be Succeeded or Failed",
            observedObjects: [
                <*v1.Pod | 0xc000e24000>{
                    TypeMeta: {Kind: "", APIVersion: ""},
                    ObjectMeta: {
                        Name: "azuredisk-volume-tester-xt28p",
                        GenerateName: "azuredisk-volume-tester-",
... skipping 134 lines ...
    Gomega truncated this representation as it exceeds 'format.MaxLength'.
    Consider having the object provide a custom 'GomegaStringer' representation
    or adjust the parameters in Gomega's 'format' package.

    Learn more here: https://onsi.github.io/gomega/#adjusting-output

    Jan  8 16:22:30.450: FAIL: timed out while waiting for pod azuredisk-5194/azuredisk-volume-tester-xt28p to be Succeeded or Failed

    Full Stack Trace
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForSuccess(0x2250591?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823 +0x5d
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedExternalRgVolumeTest).Run(0xc000e5dcc8, {0x270a780, 0xc000b3ba00}, 0x7?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_external_rg_volume_tester.go:103 +0x3c5
    sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func8()
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:361 +0x4dc
    Jan  8 16:22:30.451: INFO: deleting Pod "azuredisk-5194"/"azuredisk-volume-tester-xt28p"
    Jan  8 16:22:30.548: INFO: Error getting logs for pod azuredisk-volume-tester-xt28p: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-xt28p)
    STEP: Deleting pod azuredisk-volume-tester-xt28p in namespace azuredisk-5194 01/08/23 16:22:30.548
    STEP: validating provisioned PV 01/08/23 16:22:30.658
    STEP: checking the PV 01/08/23 16:22:30.711
    Jan  8 16:22:30.711: INFO: deleting PVC "azuredisk-5194"/"pvc-s66h4"
    Jan  8 16:22:30.711: INFO: Deleting PersistentVolumeClaim "pvc-s66h4"
    STEP: waiting for claim's PV "pvc-d984d210-0518-4a1b-b3b7-b7fef6523cf2" to be deleted 01/08/23 16:22:30.769
... skipping 23 lines ...
    Jan  8 16:23:11.705: INFO: Deleting resource group azuredisk-csi-driver-test-8c84b2b6-8f6e-11ed-919b-92557cbc817b
    Jan  8 16:23:28.430: INFO: Deleting resource group azuredisk-csi-driver-test-8d41bad3-8f6e-11ed-919b-92557cbc817b
    STEP: dump namespace information after failure 01/08/23 16:23:44.081
    STEP: Destroying namespace "azuredisk-5194" for this suite. 01/08/23 16:23:44.081
  << End Captured GinkgoWriter Output

  Jan  8 16:22:30.451: timed out while waiting for pod azuredisk-5194/azuredisk-volume-tester-xt28p to be Succeeded or Failed
  In [It] at: /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:823

  There were additional failures detected after the initial failure:
    [PANICKED]
    Test Panicked
    In [DeferCleanup (Each)] at: /usr/local/go/src/runtime/panic.go:260

    runtime error: invalid memory address or nil pointer dereference

    Full Stack Trace
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo.func1()
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:274 +0x5c
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo(0xc00003c3c0)
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:271 +0x179
... skipping 18 lines ...
STEP: setting up the StorageClass 01/08/23 16:23:45.026
STEP: creating a StorageClass  01/08/23 16:23:45.026
STEP: setting up the PVC and PV 01/08/23 16:23:45.084
STEP: creating a PVC 01/08/23 16:23:45.084
STEP: setting up the pod 01/08/23 16:23:45.179
STEP: deploying the pod 01/08/23 16:23:45.18
STEP: checking that the pod's command exits with an error 01/08/23 16:23:45.235
Jan  8 16:23:45.235: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-6bknk" in namespace "azuredisk-1353" to be "Error status code"
Jan  8 16:23:45.289: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 53.477799ms
Jan  8 16:23:47.345: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.109167272s
Jan  8 16:23:49.345: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.109238359s
Jan  8 16:23:51.344: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.108604182s
Jan  8 16:23:53.344: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.108114711s
Jan  8 16:23:55.343: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.107980461s
... skipping 149 lines ...
Jan  8 16:28:55.344: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 5m10.10838217s
Jan  8 16:28:57.343: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 5m12.107585744s
Jan  8 16:28:59.343: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 5m14.107278489s
Jan  8 16:29:01.345: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 5m16.109780345s
Jan  8 16:29:03.345: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 5m18.109121692s
Jan  8 16:29:05.343: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 5m20.107859546s
{"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:164","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Process did not finish before 2h0m0s timeout","severity":"error","time":"2023-01-08T16:29:07Z"}
++ early_exit_handler
++ '[' -n 170 ']'
++ kill -TERM 170
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 301 lines ...
Jan  8 16:38:37.344: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.108440824s
Jan  8 16:38:39.343: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.107441668s
Jan  8 16:38:41.345: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.109368222s
Jan  8 16:38:43.345: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.109536419s
Jan  8 16:38:45.345: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.109339604s
Jan  8 16:38:45.398: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.162212692s
Jan  8 16:38:45.399: INFO: Unexpected error: 
    <*pod.timeoutError | 0xc000c14930>: {
        msg: "timed out while waiting for pod azuredisk-1353/azuredisk-volume-tester-6bknk to be Error status code",
        observedObjects: [
            <*v1.Pod | 0xc00028e900>{
                TypeMeta: {Kind: "", APIVersion: ""},
                ObjectMeta: {
                    Name: "azuredisk-volume-tester-6bknk",
                    GenerateName: "azuredisk-volume-tester-",
... skipping 138 lines ...
Gomega truncated this representation as it exceeds 'format.MaxLength'.
Consider having the object provide a custom 'GomegaStringer' representation
or adjust the parameters in Gomega's 'format' package.

Learn more here: https://onsi.github.io/gomega/#adjusting-output

Jan  8 16:38:45.399: FAIL: timed out while waiting for pod azuredisk-1353/azuredisk-volume-tester-6bknk to be Error status code

Full Stack Trace
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForFailure(0x225055e?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:862 +0x77
sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedReadOnlyVolumeTest).Run(0xc000629d38, {0x270a780, 0xc000b3b860}, 0x7?)
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_read_only_volume_tester.go:56 +0x1da
sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func9()
	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:396 +0x58b
Jan  8 16:38:45.399: INFO: deleting Pod "azuredisk-1353"/"azuredisk-volume-tester-6bknk"
Jan  8 16:38:45.491: INFO: Error getting logs for pod azuredisk-volume-tester-6bknk: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-6bknk)
STEP: Deleting pod azuredisk-volume-tester-6bknk in namespace azuredisk-1353 01/08/23 16:38:45.491
STEP: validating provisioned PV 01/08/23 16:38:45.601
STEP: checking the PV 01/08/23 16:38:45.653
Jan  8 16:38:45.653: INFO: deleting PVC "azuredisk-1353"/"pvc-lkzxb"
Jan  8 16:38:45.653: INFO: Deleting PersistentVolumeClaim "pvc-lkzxb"
STEP: waiting for claim's PV "pvc-5ae548f6-e3a8-4723-96fa-2367d47751e2" to be deleted 01/08/23 16:38:45.708
... skipping 9 lines ...
Jan  8 16:39:21.160: INFO: Waiting up to 5m0s for PersistentVolumeClaim azuredisk-1353 to be removed
Jan  8 16:39:21.212: INFO: Claim "azuredisk-1353" in namespace "pvc-lkzxb" doesn't exist in the system
Jan  8 16:39:21.212: INFO: deleting StorageClass azuredisk-1353-disk.csi.azure.com-dynamic-sc-d8pqh
STEP: dump namespace information after failure 01/08/23 16:39:21.269
STEP: Destroying namespace "azuredisk-1353" for this suite. 01/08/23 16:39:21.269
------------------------------
• [FAILED] [937.177 seconds]
Dynamic Provisioning
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:41
  [multi-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:48
    [It] should create a volume on demand and mount it as readOnly in a pod [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:365
... skipping 8 lines ...
    STEP: setting up the StorageClass 01/08/23 16:23:45.026
    STEP: creating a StorageClass  01/08/23 16:23:45.026
    STEP: setting up the PVC and PV 01/08/23 16:23:45.084
    STEP: creating a PVC 01/08/23 16:23:45.084
    STEP: setting up the pod 01/08/23 16:23:45.179
    STEP: deploying the pod 01/08/23 16:23:45.18
    STEP: checking that the pod's command exits with an error 01/08/23 16:23:45.235
    Jan  8 16:23:45.235: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-6bknk" in namespace "azuredisk-1353" to be "Error status code"
    Jan  8 16:23:45.289: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 53.477799ms
    Jan  8 16:23:47.345: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.109167272s
    Jan  8 16:23:49.345: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.109238359s
    Jan  8 16:23:51.344: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.108604182s
    Jan  8 16:23:53.344: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.108114711s
    Jan  8 16:23:55.343: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.107980461s
... skipping 440 lines ...
    Jan  8 16:38:37.344: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m52.108440824s
    Jan  8 16:38:39.343: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m54.107441668s
    Jan  8 16:38:41.345: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m56.109368222s
    Jan  8 16:38:43.345: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 14m58.109536419s
    Jan  8 16:38:45.345: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.109339604s
    Jan  8 16:38:45.398: INFO: Pod "azuredisk-volume-tester-6bknk": Phase="Pending", Reason="", readiness=false. Elapsed: 15m0.162212692s
    Jan  8 16:38:45.399: INFO: Unexpected error: 
        <*pod.timeoutError | 0xc000c14930>: {
            msg: "timed out while waiting for pod azuredisk-1353/azuredisk-volume-tester-6bknk to be Error status code",
            observedObjects: [
                <*v1.Pod | 0xc00028e900>{
                    TypeMeta: {Kind: "", APIVersion: ""},
                    ObjectMeta: {
                        Name: "azuredisk-volume-tester-6bknk",
                        GenerateName: "azuredisk-volume-tester-",
... skipping 138 lines ...
    Gomega truncated this representation as it exceeds 'format.MaxLength'.
    Consider having the object provide a custom 'GomegaStringer' representation
    or adjust the parameters in Gomega's 'format' package.

    Learn more here: https://onsi.github.io/gomega/#adjusting-output

    Jan  8 16:38:45.399: FAIL: timed out while waiting for pod azuredisk-1353/azuredisk-volume-tester-6bknk to be Error status code

    Full Stack Trace
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*TestPod).WaitForFailure(0x225055e?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:862 +0x77
    sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*DynamicallyProvisionedReadOnlyVolumeTest).Run(0xc000629d38, {0x270a780, 0xc000b3b860}, 0x7?)
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/dynamically_provisioned_read_only_volume_tester.go:56 +0x1da
    sigs.k8s.io/azuredisk-csi-driver/test/e2e.(*dynamicProvisioningTestSuite).defineTests.func9()
    	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/dynamic_provisioning_test.go:396 +0x58b
    Jan  8 16:38:45.399: INFO: deleting Pod "azuredisk-1353"/"azuredisk-volume-tester-6bknk"
    Jan  8 16:38:45.491: INFO: Error getting logs for pod azuredisk-volume-tester-6bknk: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-6bknk)
    STEP: Deleting pod azuredisk-volume-tester-6bknk in namespace azuredisk-1353 01/08/23 16:38:45.491
    STEP: validating provisioned PV 01/08/23 16:38:45.601
    STEP: checking the PV 01/08/23 16:38:45.653
    Jan  8 16:38:45.653: INFO: deleting PVC "azuredisk-1353"/"pvc-lkzxb"
    Jan  8 16:38:45.653: INFO: Deleting PersistentVolumeClaim "pvc-lkzxb"
    STEP: waiting for claim's PV "pvc-5ae548f6-e3a8-4723-96fa-2367d47751e2" to be deleted 01/08/23 16:38:45.708
... skipping 10 lines ...
    Jan  8 16:39:21.212: INFO: Claim "azuredisk-1353" in namespace "pvc-lkzxb" doesn't exist in the system
    Jan  8 16:39:21.212: INFO: deleting StorageClass azuredisk-1353-disk.csi.azure.com-dynamic-sc-d8pqh
    STEP: dump namespace information after failure 01/08/23 16:39:21.269
    STEP: Destroying namespace "azuredisk-1353" for this suite. 01/08/23 16:39:21.269
  << End Captured GinkgoWriter Output

  Jan  8 16:38:45.399: timed out while waiting for pod azuredisk-1353/azuredisk-volume-tester-6bknk to be Error status code
  In [It] at: /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/testsuites.go:862

  There were additional failures detected after the initial failure:
    [PANICKED]
    Test Panicked
    In [DeferCleanup (Each)] at: /usr/local/go/src/runtime/panic.go:260

    runtime error: invalid memory address or nil pointer dereference

    Full Stack Trace
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo.func1()
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:274 +0x5c
      k8s.io/kubernetes/test/e2e/framework.(*Framework).dumpNamespaceInfo(0xc00003c3c0)
      	/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:271 +0x179
... skipping 163 lines ...
Jan  8 16:43:56.434: INFO: Pod "azuredisk-volume-tester-pn6d8": Phase="Pending", Reason="", readiness=false. Elapsed: 4m34.106543833s
Jan  8 16:43:58.435: INFO: Pod "azuredisk-volume-tester-pn6d8": Phase="Pending", Reason="", readiness=false. Elapsed: 4m36.107244996s
Jan  8 16:44:00.435: INFO: Pod "azuredisk-volume-tester-pn6d8": Phase="Pending", Reason="", readiness=false. Elapsed: 4m38.10760513s
Jan  8 16:44:02.435: INFO: Pod "azuredisk-volume-tester-pn6d8": Phase="Pending", Reason="", readiness=false. Elapsed: 4m40.107066865s
Jan  8 16:44:04.436: INFO: Pod "azuredisk-volume-tester-pn6d8": Phase="Pending", Reason="", readiness=false. Elapsed: 4m42.10841525s
Jan  8 16:44:06.435: INFO: Pod "azuredisk-volume-tester-pn6d8": Phase="Pending", Reason="", readiness=false. Elapsed: 4m44.10774125s
{"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:254","func":"k8s.io/test-infra/prow/entrypoint.gracefullyTerminate","level":"error","msg":"Process did not exit before 15m0s grace period","severity":"error","time":"2023-01-08T16:44:07Z"}
{"component":"entrypoint","error":"os: process already finished","file":"k8s.io/test-infra/prow/entrypoint/run.go:256","func":"k8s.io/test-infra/prow/entrypoint.gracefullyTerminate","level":"error","msg":"Could not kill process after grace period","severity":"error","time":"2023-01-08T16:44:07Z"}