kubernetes-sigs/azuredisk-csi-driver PR #1693 pull-azuredisk-csi-driver-e2e-windows-containerd-mainv2 #1615847243099672576
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | hccheng72: [V2] fix: prevent requesting replica attachment in a row for one volume |
| Result | ABORTED |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 1h17m |
| Revision | d8ba0aca670d0c02f92f6a79df1d42fdac692933 |
| Refs |
1693 |
... skipping 108 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11345 100 11345 0 0 167k 0 --:--:-- --:--:-- --:--:-- 167k Downloading https://get.helm.sh/helm-v3.11.0-linux-amd64.tar.gz Verifying checksum... Done. Preparing to install helm into /usr/local/bin helm installed into /usr/local/bin/helm docker pull k8sprow.azurecr.io/azuredisk-csi:latest-v2-e549890dfb2509639488eabe74ec6eabdacdbd4d || make container-all push-manifest Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:latest-v2-e549890dfb2509639488eabe74ec6eabdacdbd4d not found: manifest unknown: manifest tagged by "latest-v2-e549890dfb2509639488eabe74ec6eabdacdbd4d" is not found make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=latest-v2-e549890dfb2509639488eabe74ec6eabdacdbd4d -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=e549890dfb2509639488eabe74ec6eabdacdbd4d -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-01-18T23:14:58Z -extldflags "-static"" -tags azurediskv2 -mod vendor -o _output/amd64/azurediskpluginv2.exe ./pkg/azurediskplugin docker buildx rm container-builder || true ERROR: no builder "container-builder" found docker buildx create --use --name=container-builder container-builder # enable qemu for arm64 build # https://github.com/docker/buildx/issues/464#issuecomment-741507760 docker run --privileged --rm tonistiigi/binfmt --uninstall qemu-aarch64 Unable to find image 'tonistiigi/binfmt:latest' locally ... skipping 1708 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 occurs 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 occurs 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 359 lines ... - volumeName - volume_context - volume_id type: object status: description: status represents the current state of AzVolumeAttachment. includes error, state, and attachment status Required properties: detail: description: Status summarizes the current attachment state of the volume attachment Nil Status indicates that the volume has not yet been attached to the node properties: ... skipping 7 lines ... role: description: The current attachment role. type: string required: - role type: object error: description: Error occurred during attach/detach of volume properties: code: type: string message: type: string parameters: ... skipping 90 lines ... - volumeName - volume_context - volume_id type: object status: description: status represents the current state of AzVolumeAttachment. includes error, state, and attachment status properties: annotation: additionalProperties: type: string description: Annotations contains additional resource information to guide driver actions ... skipping 13 lines ... role: description: The current attachment role. type: string required: - role type: object error: description: Error occurred during attach/detach of volume properties: code: type: string message: type: string parameters: ... skipping 169 lines ... - maxMountReplicaCount - volumeCapability - volumeName type: object status: description: status represents the current state of AzVolume. includes error, state, and volume status properties: detail: description: Current status detail of the AzVolume Nil detail indicates that the volume has not been created properties: accessible_topology: ... skipping 28 lines ... type: string required: - capacity_bytes - node_expansion_required - volume_id type: object error: description: Error occurred during creation/deletion of volume properties: code: type: string message: type: string parameters: ... skipping 154 lines ... - maxMountReplicaCount - volumeCapability - volumeName type: object status: description: status represents the current state of AzVolume. includes error, state, and volume status properties: annotation: additionalProperties: type: string description: Annotations contains additional resource information to guide driver actions ... skipping 34 lines ... type: string required: - capacity_bytes - node_expansion_required - volume_id type: object error: description: Error occurred during creation/deletion of volume properties: code: type: string message: type: string parameters: ... skipping 883 lines ... image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.5.0" args: - "-csi-address=$(ADDRESS)" - "-v=2" - "-leader-election" - "--leader-election-namespace=kube-system" - '-handle-volume-inuse-error=false' - '-feature-gates=RecoverVolumeExpansionFailure=true' - "-timeout=240s" env: - name: ADDRESS value: /csi/csi.sock volumeMounts: ... skipping 283 lines ... Jan 18 23:29:56.283: INFO: >>> kubeConfig: /root/tmp2701827191/kubeconfig/kubeconfig.southcentralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m01/18/23 23:29:56.284[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m01/18/23 23:29:56.569[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m01/18/23 23:29:56.641[0m I0118 23:29:56.712739 16055 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m01/18/23 23:29:56.75[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/18/23 23:29:56.796[0m Jan 18 23:29:56.796: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-bmvbw" in namespace "azuredisk-2344" to be "Succeeded or Failed" Jan 18 23:29:56.838: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Pending", Reason="", readiness=false. Elapsed: 41.856411ms Jan 18 23:29:58.877: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.08093057s Jan 18 23:30:00.875: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.079352307s Jan 18 23:30:02.878: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.082338034s Jan 18 23:30:04.877: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.081483073s Jan 18 23:30:06.877: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.080858222s ... skipping 4 lines ... Jan 18 23:30:16.877: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Running", Reason="", readiness=true. Elapsed: 20.081090104s Jan 18 23:30:18.877: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Running", Reason="", readiness=true. Elapsed: 22.080797106s Jan 18 23:30:20.876: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Running", Reason="", readiness=true. Elapsed: 24.080221413s Jan 18 23:30:22.876: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Running", Reason="", readiness=false. Elapsed: 26.080441343s Jan 18 23:30:24.876: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.079821838s [1mSTEP:[0m Saw pod success [38;5;243m01/18/23 23:30:24.876[0m Jan 18 23:30:24.876: INFO: Pod "azuredisk-volume-tester-bmvbw" satisfied condition "Succeeded or Failed" Jan 18 23:30:24.876: INFO: deleting Pod "azuredisk-2344"/"azuredisk-volume-tester-bmvbw" Jan 18 23:30:24.954: INFO: Pod azuredisk-volume-tester-bmvbw has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-bmvbw in namespace azuredisk-2344 [38;5;243m01/18/23 23:30:24.954[0m [1mSTEP:[0m Destroying namespace "azuredisk-2344" for this suite. [38;5;243m01/18/23 23:30:25.007[0m [38;5;243m------------------------------[0m ... skipping 10 lines ... Jan 18 23:29:56.283: INFO: >>> kubeConfig: /root/tmp2701827191/kubeconfig/kubeconfig.southcentralus.json [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m01/18/23 23:29:56.284[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m01/18/23 23:29:56.569[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m01/18/23 23:29:56.641[0m I0118 23:29:56.712739 16055 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m01/18/23 23:29:56.75[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/18/23 23:29:56.796[0m Jan 18 23:29:56.796: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-bmvbw" in namespace "azuredisk-2344" to be "Succeeded or Failed" Jan 18 23:29:56.838: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Pending", Reason="", readiness=false. Elapsed: 41.856411ms Jan 18 23:29:58.877: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.08093057s Jan 18 23:30:00.875: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.079352307s Jan 18 23:30:02.878: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.082338034s Jan 18 23:30:04.877: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.081483073s Jan 18 23:30:06.877: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.080858222s ... skipping 4 lines ... Jan 18 23:30:16.877: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Running", Reason="", readiness=true. Elapsed: 20.081090104s Jan 18 23:30:18.877: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Running", Reason="", readiness=true. Elapsed: 22.080797106s Jan 18 23:30:20.876: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Running", Reason="", readiness=true. Elapsed: 24.080221413s Jan 18 23:30:22.876: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Running", Reason="", readiness=false. Elapsed: 26.080441343s Jan 18 23:30:24.876: INFO: Pod "azuredisk-volume-tester-bmvbw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.079821838s [1mSTEP:[0m Saw pod success [38;5;243m01/18/23 23:30:24.876[0m Jan 18 23:30:24.876: INFO: Pod "azuredisk-volume-tester-bmvbw" satisfied condition "Succeeded or Failed" Jan 18 23:30:24.876: INFO: deleting Pod "azuredisk-2344"/"azuredisk-volume-tester-bmvbw" Jan 18 23:30:24.954: INFO: Pod azuredisk-volume-tester-bmvbw has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-bmvbw in namespace azuredisk-2344 [38;5;243m01/18/23 23:30:24.954[0m [1mSTEP:[0m Destroying namespace "azuredisk-2344" for this suite. [38;5;243m01/18/23 23:30:25.007[0m [38;5;243m<< End Captured GinkgoWriter Output[0m ... skipping 158 lines ... Jan 18 23:35:14.968: INFO: PersistentVolumeClaim pvc-kwptr found but phase is Pending instead of Bound. Jan 18 23:35:17.007: INFO: PersistentVolumeClaim pvc-kwptr found but phase is Pending instead of Bound. Jan 18 23:35:19.046: INFO: PersistentVolumeClaim pvc-kwptr found but phase is Pending instead of Bound. Jan 18 23:35:21.086: INFO: PersistentVolumeClaim pvc-kwptr found but phase is Pending instead of Bound. Jan 18 23:35:23.125: INFO: PersistentVolumeClaim pvc-kwptr found but phase is Pending instead of Bound. Jan 18 23:35:25.164: INFO: PersistentVolumeClaim pvc-kwptr found but phase is Pending instead of Bound. Jan 18 23:35:27.165: INFO: Unexpected error: <*errors.errorString | 0xc000252f20>: { s: "PersistentVolumeClaims [pvc-kwptr] not all in phase Bound within 5m0s", } Jan 18 23:35:27.165: FAIL: PersistentVolumeClaims [pvc-kwptr] not all in phase Bound within 5m0s Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/resources.(*TestPersistentVolumeClaim).WaitForBound(_) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/pvc.go:132 +0x19d sigs.k8s.io/azuredisk-csi-driver/test/resources.(*VolumeDetails).SetupDynamicPersistentVolumeClaim(0xc000777890, {0x26fb380?, 0xc000102340}, 0xc000c4c840, {0x7fcde03e43d8, 0xc0003e9d20}, 0x7a?) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/volumes.go:103 +0x6d4 sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*AzDiskSchedulerExtenderPodSchedulingWithPVTest).Run(0xc000777c78, {0x26fb380, 0xc000102340}, 0x7?, {0x220ec17?, 0x0?}) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/azdiskschedulerextender_pod_scheduling_with_pv_tester.go:39 +0x108 sigs.k8s.io/azuredisk-csi-driver/test/e2e.schedulerExtenderTests.func3() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:114 +0x48e [1mSTEP:[0m dump namespace information after failure [38;5;243m01/18/23 23:35:27.166[0m [1mSTEP:[0m Destroying namespace "azuredisk-1095" for this suite. [38;5;243m01/18/23 23:35:27.166[0m [38;5;243m------------------------------[0m [38;5;9m• [FAILED] [302.159 seconds][0m AzDiskSchedulerExtender [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:41[0m [single-az] [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:43[0m [38;5;9m[1m[It] Should schedule and start a pod with a persistent volume requests. [Windows][0m [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:89[0m ... skipping 156 lines ... Jan 18 23:35:14.968: INFO: PersistentVolumeClaim pvc-kwptr found but phase is Pending instead of Bound. Jan 18 23:35:17.007: INFO: PersistentVolumeClaim pvc-kwptr found but phase is Pending instead of Bound. Jan 18 23:35:19.046: INFO: PersistentVolumeClaim pvc-kwptr found but phase is Pending instead of Bound. Jan 18 23:35:21.086: INFO: PersistentVolumeClaim pvc-kwptr found but phase is Pending instead of Bound. Jan 18 23:35:23.125: INFO: PersistentVolumeClaim pvc-kwptr found but phase is Pending instead of Bound. Jan 18 23:35:25.164: INFO: PersistentVolumeClaim pvc-kwptr found but phase is Pending instead of Bound. Jan 18 23:35:27.165: INFO: Unexpected error: <*errors.errorString | 0xc000252f20>: { s: "PersistentVolumeClaims [pvc-kwptr] not all in phase Bound within 5m0s", } Jan 18 23:35:27.165: FAIL: PersistentVolumeClaims [pvc-kwptr] not all in phase Bound within 5m0s Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/resources.(*TestPersistentVolumeClaim).WaitForBound(_) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/pvc.go:132 +0x19d sigs.k8s.io/azuredisk-csi-driver/test/resources.(*VolumeDetails).SetupDynamicPersistentVolumeClaim(0xc000777890, {0x26fb380?, 0xc000102340}, 0xc000c4c840, {0x7fcde03e43d8, 0xc0003e9d20}, 0x7a?) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/volumes.go:103 +0x6d4 ... skipping 10 lines ... [1mThere were additional failures detected after the initial failure:[0m [38;5;13m[PANICKED][0m [38;5;13mTest Panicked[0m [38;5;13mIn [1m[DeferCleanup (Each)][0m[38;5;13m at: [1m/usr/local/go/src/runtime/panic.go:260[0m [38;5;13mruntime error: invalid memory address or nil pointer dereference[0m [38;5;13mFull Stack Trace[0m 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(0xc00019a5a0) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:271 +0x179 ... skipping 315 lines ... I0118 23:45:19.765991 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0118 23:45:21.766478 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0118 23:45:23.766444 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0118 23:45:25.766135 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0118 23:45:27.766231 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0118 23:45:27.803623 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready Jan 18 23:45:27.803: INFO: Unexpected error: <*errors.errorString | 0xc000406f80>: { s: "timed out waiting for the condition", } Jan 18 23:45:27.803: FAIL: timed out waiting for the condition Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/resources.(*TestStatefulset).Create(0xc000d925f0) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/statefulset.go:121 +0x12e sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*AzDiskSchedulerExtenderPodSchedulingOnFailover).Run(0xc000ecfb70, {0x26fb380, 0xc000503520}, 0x7?, {0x220ec17, 0x20}) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/azdiskschedulerextender_pod_scheduling_on_failover.go:55 +0x2c5 sigs.k8s.io/azuredisk-csi-driver/test/e2e.schedulerExtenderTests.func4() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:151 +0x5ee Jan 18 23:45:27.804: INFO: deleting StatefulSet "azuredisk-3570"/"azuredisk-volume-tester-p5fw9" Jan 18 23:45:27.883: INFO: Unexpected error: <*errors.errorString | 0xc00059e580>: { s: "resource name may not be empty", } Jan 18 23:45:27.883: FAIL: resource name may not be empty Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/resources.(*TestStatefulset).Cleanup(0xc000d925f0, 0xd18c2e2800) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/statefulset.go:225 +0x4d6 panic({0x203b9a0, 0xc0002633b0}) /usr/local/go/src/runtime/panic.go:884 +0x212 k8s.io/kubernetes/test/e2e/framework.Fail({0x2218fdb, 0x23}, {0xc000ecebc0?, 0x2218fdb?, 0xc000ecebe8?}) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/log.go:61 +0x145 k8s.io/kubernetes/test/e2e/framework.ExpectNoErrorWithOffset(0x1, {0x26bff40, 0xc000406f80}, {0x0?, 0x0?, 0x0?}) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/expect.go:76 +0x267 k8s.io/kubernetes/test/e2e/framework.ExpectNoError(...) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/expect.go:43 sigs.k8s.io/azuredisk-csi-driver/test/resources.(*TestStatefulset).Create(0xc000d925f0) ... skipping 3 lines ... sigs.k8s.io/azuredisk-csi-driver/test/e2e.schedulerExtenderTests.func4() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:151 +0x5ee Jan 18 23:45:27.884: INFO: deleting StorageClass azuredisk-3570-disk.csi.azure.com-dynamic-sc-z4tvk [1mSTEP:[0m dump namespace information after failure [38;5;243m01/18/23 23:45:27.944[0m [1mSTEP:[0m Destroying namespace "azuredisk-3570" for this suite. [38;5;243m01/18/23 23:45:27.944[0m [38;5;243m------------------------------[0m [38;5;9m• [FAILED] [600.777 seconds][0m AzDiskSchedulerExtender [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:41[0m [single-az] [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:43[0m [38;5;9m[1m[It] Should schedule and reschedule a pod with a persistent volume request on failover. [Windows][0m [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:117[0m ... skipping 309 lines ... I0118 23:45:19.765991 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0118 23:45:21.766478 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0118 23:45:23.766444 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0118 23:45:25.766135 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0118 23:45:27.766231 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0118 23:45:27.803623 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready Jan 18 23:45:27.803: INFO: Unexpected error: <*errors.errorString | 0xc000406f80>: { s: "timed out waiting for the condition", } Jan 18 23:45:27.803: FAIL: timed out waiting for the condition Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/resources.(*TestStatefulset).Create(0xc000d925f0) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/statefulset.go:121 +0x12e sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*AzDiskSchedulerExtenderPodSchedulingOnFailover).Run(0xc000ecfb70, {0x26fb380, 0xc000503520}, 0x7?, {0x220ec17, 0x20}) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/azdiskschedulerextender_pod_scheduling_on_failover.go:55 +0x2c5 sigs.k8s.io/azuredisk-csi-driver/test/e2e.schedulerExtenderTests.func4() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:151 +0x5ee Jan 18 23:45:27.804: INFO: deleting StatefulSet "azuredisk-3570"/"azuredisk-volume-tester-p5fw9" Jan 18 23:45:27.883: INFO: Unexpected error: <*errors.errorString | 0xc00059e580>: { s: "resource name may not be empty", } Jan 18 23:45:27.883: FAIL: resource name may not be empty Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/resources.(*TestStatefulset).Cleanup(0xc000d925f0, 0xd18c2e2800) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/statefulset.go:225 +0x4d6 panic({0x203b9a0, 0xc0002633b0}) /usr/local/go/src/runtime/panic.go:884 +0x212 k8s.io/kubernetes/test/e2e/framework.Fail({0x2218fdb, 0x23}, {0xc000ecebc0?, 0x2218fdb?, 0xc000ecebe8?}) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/log.go:61 +0x145 k8s.io/kubernetes/test/e2e/framework.ExpectNoErrorWithOffset(0x1, {0x26bff40, 0xc000406f80}, {0x0?, 0x0?, 0x0?}) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/expect.go:76 +0x267 k8s.io/kubernetes/test/e2e/framework.ExpectNoError(...) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/expect.go:43 sigs.k8s.io/azuredisk-csi-driver/test/resources.(*TestStatefulset).Create(0xc000d925f0) ... skipping 12 lines ... [1mThere were additional failures detected after the initial failure:[0m [38;5;13m[PANICKED][0m [38;5;13mTest Panicked[0m [38;5;13mIn [1m[DeferCleanup (Each)][0m[38;5;13m at: [1m/usr/local/go/src/runtime/panic.go:260[0m [38;5;13mruntime error: invalid memory address or nil pointer dereference[0m [38;5;13mFull Stack Trace[0m 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(0xc00019a5a0) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:271 +0x179 ... skipping 162 lines ... Jan 18 23:50:17.867: INFO: PersistentVolumeClaim pvc-5jbnf found but phase is Pending instead of Bound. Jan 18 23:50:19.905: INFO: PersistentVolumeClaim pvc-5jbnf found but phase is Pending instead of Bound. Jan 18 23:50:21.944: INFO: PersistentVolumeClaim pvc-5jbnf found but phase is Pending instead of Bound. Jan 18 23:50:23.981: INFO: PersistentVolumeClaim pvc-5jbnf found but phase is Pending instead of Bound. Jan 18 23:50:26.019: INFO: PersistentVolumeClaim pvc-5jbnf found but phase is Pending instead of Bound. Jan 18 23:50:28.057: INFO: PersistentVolumeClaim pvc-5jbnf found but phase is Pending instead of Bound. Jan 18 23:50:30.057: INFO: Unexpected error: <*errors.errorString | 0xc000e2b6f0>: { s: "PersistentVolumeClaims [pvc-5jbnf] not all in phase Bound within 5m0s", } Jan 18 23:50:30.058: FAIL: PersistentVolumeClaims [pvc-5jbnf] not all in phase Bound within 5m0s Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/resources.(*TestPersistentVolumeClaim).WaitForBound(_) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/pvc.go:132 +0x19d sigs.k8s.io/azuredisk-csi-driver/test/resources.(*VolumeDetails).SetupDynamicPersistentVolumeClaim(0xc000d2f698, {0x26fb380?, 0xc000102340}, 0xc000d56160, {0x7fcde03e43d8, 0xc0002520a0}, 0x7a?) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/volumes.go:103 +0x6d4 ... skipping 3 lines ... /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/azdiskschedulerextender_pod_scheduling_with_multiple_pv_tester.go:36 +0x65 sigs.k8s.io/azuredisk-csi-driver/test/e2e.schedulerExtenderTests.func5() /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:181 +0x6f7 [1mSTEP:[0m dump namespace information after failure [38;5;243m01/18/23 23:50:30.059[0m [1mSTEP:[0m Destroying namespace "azuredisk-9916" for this suite. [38;5;243m01/18/23 23:50:30.059[0m [38;5;243m------------------------------[0m [38;5;9m• [FAILED] [302.115 seconds][0m AzDiskSchedulerExtender [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:41[0m [single-az] [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:43[0m [38;5;9m[1m[It] Should schedule and start a pod with multiple persistent volume requests. [Windows][0m [38;5;243m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/azdiskschedulerextender_test.go:154[0m ... skipping 156 lines ... Jan 18 23:50:17.867: INFO: PersistentVolumeClaim pvc-5jbnf found but phase is Pending instead of Bound. Jan 18 23:50:19.905: INFO: PersistentVolumeClaim pvc-5jbnf found but phase is Pending instead of Bound. Jan 18 23:50:21.944: INFO: PersistentVolumeClaim pvc-5jbnf found but phase is Pending instead of Bound. Jan 18 23:50:23.981: INFO: PersistentVolumeClaim pvc-5jbnf found but phase is Pending instead of Bound. Jan 18 23:50:26.019: INFO: PersistentVolumeClaim pvc-5jbnf found but phase is Pending instead of Bound. Jan 18 23:50:28.057: INFO: PersistentVolumeClaim pvc-5jbnf found but phase is Pending instead of Bound. Jan 18 23:50:30.057: INFO: Unexpected error: <*errors.errorString | 0xc000e2b6f0>: { s: "PersistentVolumeClaims [pvc-5jbnf] not all in phase Bound within 5m0s", } Jan 18 23:50:30.058: FAIL: PersistentVolumeClaims [pvc-5jbnf] not all in phase Bound within 5m0s Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/resources.(*TestPersistentVolumeClaim).WaitForBound(_) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/pvc.go:132 +0x19d sigs.k8s.io/azuredisk-csi-driver/test/resources.(*VolumeDetails).SetupDynamicPersistentVolumeClaim(0xc000d2f698, {0x26fb380?, 0xc000102340}, 0xc000d56160, {0x7fcde03e43d8, 0xc0002520a0}, 0x7a?) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/volumes.go:103 +0x6d4 ... skipping 12 lines ... [1mThere were additional failures detected after the initial failure:[0m [38;5;13m[PANICKED][0m [38;5;13mTest Panicked[0m [38;5;13mIn [1m[DeferCleanup (Each)][0m[38;5;13m at: [1m/usr/local/go/src/runtime/panic.go:260[0m [38;5;13mruntime error: invalid memory address or nil pointer dereference[0m [38;5;13mFull Stack Trace[0m 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(0xc00019a5a0) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:271 +0x179 ... skipping 621 lines ... I0119 00:00:26.626503 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0119 00:00:28.598886 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0119 00:00:28.625618 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0119 00:00:30.599288 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0119 00:00:30.625638 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0119 00:00:30.636133 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready Jan 19 00:00:30.636: INFO: Unexpected error: <*errors.errorString | 0xc000406f80>: { s: "timed out waiting for the condition", } Jan 19 00:00:30.636: FAIL: timed out waiting for the condition Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/resources.(*TestStatefulset).Create(0xc0000c5090) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/statefulset.go:121 +0x12e sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*AzDiskSchedulerExtenderPodSchedulingOnFailoverMultiplePV).Run.func1(0xc0000c5090) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/azdiskschedulerextender_pod_scheduling_on_failover_multiple_pv_perf_tester.go:66 +0x8f created by sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*AzDiskSchedulerExtenderPodSchedulingOnFailoverMultiplePV).Run /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/azdiskschedulerextender_pod_scheduling_on_failover_multiple_pv_perf_tester.go:62 +0x20d I0119 00:00:30.663059 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready Jan 19 00:00:30.663: INFO: Unexpected error: <*errors.errorString | 0xc000406f80>: { s: "timed out waiting for the condition", } Jan 19 00:00:30.663: FAIL: timed out waiting for the condition Full Stack Trace sigs.k8s.io/azuredisk-csi-driver/test/resources.(*TestStatefulset).Create(0xc0000c5680) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/resources/statefulset.go:121 +0x12e sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites.(*AzDiskSchedulerExtenderPodSchedulingOnFailoverMultiplePV).Run.func1(0xc0000c5680) /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/testsuites/azdiskschedulerextender_pod_scheduling_on_failover_multiple_pv_perf_tester.go:66 +0x8f ... skipping 489 lines ... I0119 00:09:46.902952 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0119 00:09:46.902954 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0119 00:09:48.900907 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0119 00:09:48.901327 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0119 00:09:50.901933 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready I0119 00:09:50.902569 16055 statefulset.go:175] 0/1 replicas in the StatefulSet are ready {"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:168","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2023-01-19T00:09:52Z"} ++ early_exit_handler ++ '[' -n 163 ']' ++ kill -TERM 163 ++ cleanup_dind ++ [[ true == \t\r\u\e ]] ++ echo 'Cleaning up after docker' ... skipping 3 lines ...