kubernetes-sigs/azuredisk-csi-driver PR #1666 pull-azuredisk-csi-driver-e2e-capz-mainv2 #1616505850619236352
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | alice-zheyan-yu: [V2] feat: fetch VMs to recover AzVolumeAttachment |
| Result | ABORTED |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 59m18s |
| Revision | 3c9841e0e8a2720e25692fb457a0736f981f613b |
| Refs |
1666 |
... skipping 783 lines ... certificate.cert-manager.io "selfsigned-cert" deleted # Create secret for AzureClusterIdentity ./hack/create-identity-secret.sh make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make[2]: Nothing to be done for 'kubectl'. make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' Error from server (NotFound): secrets "cluster-identity-secret" not found secret/cluster-identity-secret created secret/cluster-identity-secret labeled # Create customized cloud provider configs ./hack/create-custom-cloud-provider-config.sh make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make[2]: Nothing to be done for 'kubectl'. ... skipping 222 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11345 100 11345 0 0 187k 0 --:--:-- --:--:-- --:--:-- 187k 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 capzci.azurecr.io/azuredisk-csi:latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228 || make container-all push-manifest Error response from daemon: manifest for capzci.azurecr.io/azuredisk-csi:latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228 not found: manifest unknown: manifest tagged by "latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228" 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-170b3ae022589c5c949eadbdc4736c1b28944228 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=170b3ae022589c5c949eadbdc4736c1b28944228 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-01-20T19:00:54Z -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 697 lines ... } } ] } make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker pull capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228 || make azdiskschedulerextender-all push-manifest-azdiskschedulerextender Error response from daemon: manifest for capzci.azurecr.io/azdiskschedulerextender-csi:latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228 not found: manifest unknown: manifest tagged by "latest-v2-170b3ae022589c5c949eadbdc4736c1b28944228" is not found make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver' docker buildx rm container-builder || true container-builder removed docker buildx create --use --name=container-builder container-builder # enable qemu for arm64 build ... skipping 1033 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 1069 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 295 lines ... Jan 20 19:13:50.348: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-xcxbx] to have phase Bound Jan 20 19:13:50.458: INFO: PersistentVolumeClaim pvc-xcxbx found and phase=Bound (109.959665ms) [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:13:50.458[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:13:50.567[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:13:50.676[0m [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:13:50.676[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/20/23 19:13:50.788[0m Jan 20 19:13:50.788: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-24f6m" in namespace "azuredisk-34" to be "Error status code" Jan 20 19:13:50.898: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 109.112825ms Jan 20 19:13:53.008: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219254522s Jan 20 19:13:55.007: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.218742059s Jan 20 19:13:57.007: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.218802899s Jan 20 19:13:59.007: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.219025334s Jan 20 19:14:01.007: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.218406752s Jan 20 19:14:03.015: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 12.226495994s Jan 20 19:14:05.015: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 14.226505808s Jan 20 19:14:07.015: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Failed", Reason="", readiness=false. Elapsed: 16.226697798s [1mSTEP:[0m Saw pod failure [38;5;243m01/20/23 19:14:07.015[0m Jan 20 19:14:07.015: INFO: Pod "azuredisk-volume-tester-24f6m" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/20/23 19:14:07.015[0m Jan 20 19:14:07.143: INFO: deleting Pod "azuredisk-34"/"azuredisk-volume-tester-24f6m" Jan 20 19:14:07.254: INFO: Pod azuredisk-volume-tester-24f6m has the following logs: /bin/sh: can't create /mnt/test-1/data: Read-only file system [1mSTEP:[0m Deleting pod azuredisk-volume-tester-24f6m in namespace azuredisk-34 [38;5;243m01/20/23 19:14:07.254[0m Jan 20 19:14:07.378: INFO: deleting PVC "azuredisk-34"/"pvc-xcxbx" ... skipping 36 lines ... Jan 20 19:13:50.348: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-xcxbx] to have phase Bound Jan 20 19:13:50.458: INFO: PersistentVolumeClaim pvc-xcxbx found and phase=Bound (109.959665ms) [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:13:50.458[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:13:50.567[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:13:50.676[0m [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:13:50.676[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m01/20/23 19:13:50.788[0m Jan 20 19:13:50.788: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-24f6m" in namespace "azuredisk-34" to be "Error status code" Jan 20 19:13:50.898: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 109.112825ms Jan 20 19:13:53.008: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 2.219254522s Jan 20 19:13:55.007: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 4.218742059s Jan 20 19:13:57.007: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 6.218802899s Jan 20 19:13:59.007: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 8.219025334s Jan 20 19:14:01.007: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 10.218406752s Jan 20 19:14:03.015: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 12.226495994s Jan 20 19:14:05.015: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Pending", Reason="", readiness=false. Elapsed: 14.226505808s Jan 20 19:14:07.015: INFO: Pod "azuredisk-volume-tester-24f6m": Phase="Failed", Reason="", readiness=false. Elapsed: 16.226697798s [1mSTEP:[0m Saw pod failure [38;5;243m01/20/23 19:14:07.015[0m Jan 20 19:14:07.015: INFO: Pod "azuredisk-volume-tester-24f6m" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m01/20/23 19:14:07.015[0m Jan 20 19:14:07.143: INFO: deleting Pod "azuredisk-34"/"azuredisk-volume-tester-24f6m" Jan 20 19:14:07.254: INFO: Pod azuredisk-volume-tester-24f6m has the following logs: /bin/sh: can't create /mnt/test-1/data: Read-only file system [1mSTEP:[0m Deleting pod azuredisk-volume-tester-24f6m in namespace azuredisk-34 [38;5;243m01/20/23 19:14:07.254[0m Jan 20 19:14:07.378: INFO: deleting PVC "azuredisk-34"/"pvc-xcxbx" ... skipping 65 lines ... Jan 20 19:14:44.644: INFO: PersistentVolumeClaim pvc-cwk4q found and phase=Bound (109.645033ms) [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:14:44.644[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:14:44.753[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:14:44.863[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m01/20/23 19:14:45.033[0m [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:14:59.244[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:14:59.354[0m Jan 20 19:14:59.354: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-bpw2j" in namespace "azuredisk-3975" to be "Succeeded or Failed" Jan 20 19:14:59.463: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 108.751661ms Jan 20 19:15:01.573: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.218438287s Jan 20 19:15:03.573: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.218580099s Jan 20 19:15:05.573: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.219198338s Jan 20 19:15:07.575: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.220996468s Jan 20 19:15:09.574: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.220169601s ... skipping 10 lines ... Jan 20 19:15:31.574: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 32.220265801s Jan 20 19:15:33.573: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 34.218314738s Jan 20 19:15:35.580: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 36.225539162s Jan 20 19:15:37.580: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 38.225941805s Jan 20 19:15:39.580: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.225343872s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:15:39.58[0m Jan 20 19:15:39.580: INFO: Pod "azuredisk-volume-tester-bpw2j" satisfied condition "Succeeded or Failed" Jan 20 19:15:39.580: INFO: deleting Pod "azuredisk-3975"/"azuredisk-volume-tester-bpw2j" Jan 20 19:15:39.699: INFO: Pod azuredisk-volume-tester-bpw2j has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-bpw2j in namespace azuredisk-3975 [38;5;243m01/20/23 19:15:39.699[0m Jan 20 19:15:40.074: INFO: deleting PVC "azuredisk-3975"/"pvc-cwk4q" Jan 20 19:15:40.074: INFO: Deleting PersistentVolumeClaim "pvc-cwk4q" ... skipping 36 lines ... Jan 20 19:14:44.644: INFO: PersistentVolumeClaim pvc-cwk4q found and phase=Bound (109.645033ms) [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:14:44.644[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:14:44.753[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:14:44.863[0m [1mSTEP:[0m attaching disk to node#0 [38;5;243m01/20/23 19:14:45.033[0m [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:14:59.244[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:14:59.354[0m Jan 20 19:14:59.354: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-bpw2j" in namespace "azuredisk-3975" to be "Succeeded or Failed" Jan 20 19:14:59.463: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 108.751661ms Jan 20 19:15:01.573: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 2.218438287s Jan 20 19:15:03.573: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 4.218580099s Jan 20 19:15:05.573: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 6.219198338s Jan 20 19:15:07.575: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 8.220996468s Jan 20 19:15:09.574: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 10.220169601s ... skipping 10 lines ... Jan 20 19:15:31.574: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 32.220265801s Jan 20 19:15:33.573: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 34.218314738s Jan 20 19:15:35.580: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 36.225539162s Jan 20 19:15:37.580: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Pending", Reason="", readiness=false. Elapsed: 38.225941805s Jan 20 19:15:39.580: INFO: Pod "azuredisk-volume-tester-bpw2j": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.225343872s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:15:39.58[0m Jan 20 19:15:39.580: INFO: Pod "azuredisk-volume-tester-bpw2j" satisfied condition "Succeeded or Failed" Jan 20 19:15:39.580: INFO: deleting Pod "azuredisk-3975"/"azuredisk-volume-tester-bpw2j" Jan 20 19:15:39.699: INFO: Pod azuredisk-volume-tester-bpw2j has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-bpw2j in namespace azuredisk-3975 [38;5;243m01/20/23 19:15:39.699[0m Jan 20 19:15:40.074: INFO: deleting PVC "azuredisk-3975"/"pvc-cwk4q" Jan 20 19:15:40.074: INFO: Deleting PersistentVolumeClaim "pvc-cwk4q" ... skipping 391 lines ... [38;5;243m<< End Captured GinkgoWriter Output[0m [38;5;14mtest case is only available for csi driver[0m [38;5;14mIn [1m[It][0m[38;5;14m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:395[0m [1mThere were additional failures detected after the initial failure:[0m [38;5;9m[FAILED][0m [38;5;9mpre-provisioning disk got deleted with the deletion of pv: Retriable: false, RetryAfter: 0s, HTTPStatusCode: 404, RawError: { "error": { "code": "NotFound", "message": "Disk shared-disk-replicas is not found." } }[0m [38;5;9mIn [1m[AfterEach][0m[38;5;9m at: [1m/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:490[0m [38;5;243m------------------------------[0m ... skipping 4 lines ... Jan 20 19:24:05.513: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m01/20/23 19:24:05.515[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m01/20/23 19:24:05.841[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m01/20/23 19:24:06.057[0m I0120 19:24:06.272599 42271 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:24:06.43[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:24:06.543[0m Jan 20 19:24:06.543: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-x7wg4" in namespace "azuredisk-7990" to be "Succeeded or Failed" Jan 20 19:24:06.652: INFO: Pod "azuredisk-volume-tester-x7wg4": Phase="Pending", Reason="", readiness=false. Elapsed: 108.45182ms Jan 20 19:24:08.766: INFO: Pod "azuredisk-volume-tester-x7wg4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.223214987s Jan 20 19:24:10.767: INFO: Pod "azuredisk-volume-tester-x7wg4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.224187146s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:24:10.768[0m Jan 20 19:24:10.768: INFO: Pod "azuredisk-volume-tester-x7wg4" satisfied condition "Succeeded or Failed" Jan 20 19:24:10.768: INFO: deleting Pod "azuredisk-7990"/"azuredisk-volume-tester-x7wg4" Jan 20 19:24:10.889: INFO: Pod azuredisk-volume-tester-x7wg4 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-x7wg4 in namespace azuredisk-7990 [38;5;243m01/20/23 19:24:10.889[0m [1mSTEP:[0m Destroying namespace "azuredisk-7990" for this suite. [38;5;243m01/20/23 19:24:11.011[0m [38;5;243m------------------------------[0m ... skipping 10 lines ... Jan 20 19:24:05.513: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig [1mSTEP:[0m Building a namespace api object, basename azuredisk [38;5;243m01/20/23 19:24:05.515[0m [1mSTEP:[0m Waiting for a default service account to be provisioned in namespace [38;5;243m01/20/23 19:24:05.841[0m [1mSTEP:[0m Waiting for kube-root-ca.crt to be provisioned in namespace [38;5;243m01/20/23 19:24:06.057[0m I0120 19:24:06.272599 42271 azuredisk_driver.go:52] Using azure disk driver: disk.csi.azure.com [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:24:06.43[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:24:06.543[0m Jan 20 19:24:06.543: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-x7wg4" in namespace "azuredisk-7990" to be "Succeeded or Failed" Jan 20 19:24:06.652: INFO: Pod "azuredisk-volume-tester-x7wg4": Phase="Pending", Reason="", readiness=false. Elapsed: 108.45182ms Jan 20 19:24:08.766: INFO: Pod "azuredisk-volume-tester-x7wg4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.223214987s Jan 20 19:24:10.767: INFO: Pod "azuredisk-volume-tester-x7wg4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.224187146s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:24:10.768[0m Jan 20 19:24:10.768: INFO: Pod "azuredisk-volume-tester-x7wg4" satisfied condition "Succeeded or Failed" Jan 20 19:24:10.768: INFO: deleting Pod "azuredisk-7990"/"azuredisk-volume-tester-x7wg4" Jan 20 19:24:10.889: INFO: Pod azuredisk-volume-tester-x7wg4 has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-x7wg4 in namespace azuredisk-7990 [38;5;243m01/20/23 19:24:10.889[0m [1mSTEP:[0m Destroying namespace "azuredisk-7990" for this suite. [38;5;243m01/20/23 19:24:11.011[0m [38;5;243m<< End Captured GinkgoWriter Output[0m ... skipping 17 lines ... Jan 20 19:24:14.322: INFO: PersistentVolumeClaim pvc-65r8h found but phase is Pending instead of Bound. Jan 20 19:24:16.431: INFO: PersistentVolumeClaim pvc-65r8h found and phase=Bound (4.328323133s) [1mSTEP:[0m checking the PVC [38;5;243m01/20/23 19:24:16.432[0m [1mSTEP:[0m validating provisioned PV [38;5;243m01/20/23 19:24:16.541[0m [1mSTEP:[0m checking the PV [38;5;243m01/20/23 19:24:16.65[0m [1mSTEP:[0m deploying the pod [38;5;243m01/20/23 19:24:16.807[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m01/20/23 19:24:16.917[0m Jan 20 19:24:16.917: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-x8vxw" in namespace "azuredisk-5345" to be "Succeeded or Failed" Jan 20 19:24:17.026: INFO: Pod "azuredisk-volume-tester-x8vxw": Phase="Pending", Reason="", readiness=false. Elapsed: 108.263214ms Jan 20 19:24:19.135: INFO: Pod "azuredisk-volume-tester-x8vxw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.217671701s Jan 20 19:24:21.135: INFO: Pod "azuredisk-volume-tester-x8vxw": Phase="Pending", Reason="", readiness=false. Elapsed: 4.217242818s Jan 20 19:24:23.137: INFO: Pod "azuredisk-volume-tester-x8vxw": Phase="Pending", Reason="", readiness=false. Elapsed: 6.2193161s Jan 20 19:24:25.134: INFO: Pod "azuredisk-volume-tester-x8vxw": Phase="Pending", Reason="", readiness=false. Elapsed: 8.217067565s Jan 20 19:24:27.141: INFO: Pod "azuredisk-volume-tester-x8vxw": Phase="Pending", Reason="", readiness=false. Elapsed: 10.223609011s Jan 20 19:24:29.141: INFO: Pod "azuredisk-volume-tester-x8vxw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.223401286s [1mSTEP:[0m Saw pod success [38;5;243m01/20/23 19:24:29.141[0m Jan 20 19:24:29.141: INFO: Pod "azuredisk-volume-tester-x8vxw" satisfied condition "Succeeded or Failed" Jan 20 19:24:29.141: INFO: deleting Pod "azuredisk-5345"/"azuredisk-volume-tester-x8vxw" Jan 20 19:24:29.252: INFO: Pod azuredisk-volume-tester-x8vxw has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-x8vxw in namespace azuredisk-5345 [38;5;243m01/20/23 19:24:29.252[0m Jan 20 19:24:29.373: INFO: deleting PVC "azuredisk-5345"/"pvc-65r8h" Jan 20 19:24:29.373: INFO: Deleting PersistentVolumeClaim "pvc-65r8h" [1mSTEP:[0m waiting for claim's PV "pvc-215e289c-17b9-476c-8002-d134221adc75" to be deleted [38;5;243m01/20/23 19:24:29.482[0m Jan 20 19:24:29.482: INFO: Waiting up to 10m0s for PersistentVolume pvc-215e289c-17b9-476c-8002-d134221adc75 to get deleted Jan 20 19:24:29.591: INFO: PersistentVolume pvc-215e289c-17b9-476c-8002-d134221adc75 found and phase=Released (108.54481ms) Jan 20 19:24:34.700: INFO: PersistentVolume pvc-215e289c-17b9-476c-8002-d134221adc75 found and phase=Released (5.217353504s) Jan 20 19:24:39.810: INFO: PersistentVolume pvc-215e289c-17b9-476c-8002-d134221adc75 found and phase=Released (10.327761664s) {"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-20T19:24:42Z"} ++ early_exit_handler ++ '[' -n 149 ']' ++ kill -TERM 149 ++ cleanup_dind ++ [[ true == \t\r\u\e ]] ++ echo 'Cleaning up after docker' ... skipping 4 lines ...