kubernetes-sigs/azuredisk-csi-driver PR #1739 pull-azuredisk-csi-driver-e2e-migration-mainv2 #1630709651228069888
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | alice-zheyan-yu: [V2] fix: enhance UpdateCRIWithRetry to fix the cachedClient Get not found… |
| Result | ABORTED |
| Tests | 0 failed / 16 succeeded |
| Started | |
| Elapsed | 39m29s |
| Revision | 250b874cb812582c5397de01d413d7e68d630b67 |
| Refs |
1739 |
AzureDisk CSI Driver End-to-End Tests [AfterSuite]
AzureDisk CSI Driver End-to-End Tests [BeforeSuite]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a deployment object, write and read to it, delete the pod and write and read to it again [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a pod with multiple volumes [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a raw block volume and a filesystem volume on demand and bind to the same pod [kubernetes.io/azure-disk] [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a raw block volume on demand [kubernetes.io/azure-disk] [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a statefulset object, write and read to it, delete the pod and write and read to it again [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a volume on demand and mount it as readOnly in a pod [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a volume on demand with mount options [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create multiple PV objects, bind to PVCs and attach all to a single pod [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create multiple PV objects, bind to PVCs and attach all to different pods on the same node [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should delete AzVolumeAttachment after pod deleted when maxMountReplicaCount == 0 [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should delete PV with reclaimPolicy "Delete" [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should detach disk after pod deleted when maxMountReplicaCount = 0 [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should receive FailedMount event with invalid mount options [kubernetes.io/azure-disk] [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should create an inline volume by in-tree driver [kubernetes.io/azure-disk]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [multi-az] Should schedule and reschedule a pod with a persistent volume request on failover. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [multi-az] Should schedule and start a pod with a persistent volume requests. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [multi-az] Should schedule and start a pod with multiple persistent volume requests and reschedule on failover.
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [multi-az] Should schedule and start a pod with multiple persistent volume requests with replicas and reschedule on deletion.
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [multi-az] Should schedule and start a pod with multiple persistent volume requests. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [multi-az] Should schedule and start a pod with no persistent volume requests. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [single-az] Should schedule and reschedule a pod with a persistent volume request on failover. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [single-az] Should schedule and start a pod with a persistent volume requests. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [single-az] Should schedule and start a pod with multiple persistent volume requests and reschedule on failover.
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [single-az] Should schedule and start a pod with multiple persistent volume requests with replicas and reschedule on deletion.
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [single-az] Should schedule and start a pod with multiple persistent volume requests. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] AzDiskSchedulerExtender [single-az] Should schedule and start a pod with no persistent volume requests. [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Controller AzDriverNode [single-az] Should create AzDriverNode resource and report heartbeat.
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment If a replica is deleted, should create another replica to replace the previous one
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment If failover happens, should turn replica to primary and create an additional replica for replacement
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment Should create replica azVolumeAttachment object when maxShares > 1
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment Should delete AzVolumeAttachment object properly
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment Should initialize AzVolumeAttachment object's status and append finalizer and create labels
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment number of replicas should converge to assigned maxMountReplicaCount value
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment should garbage collect replica AzVolumeAttachment if no promotion or new primary creation happens in a given period of time
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumeAttachment should not delete replica AzVolumeAttachment if new primary creation happens within a given period of time after primary failure
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumes Should delete AzVolume object
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumes Should delete AzVolumeAttachment objects with deletion of AzVolume
AzureDisk CSI Driver End-to-End Tests [It] Controller AzVolumes Should initialize AzVolume object
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should create and attach a volume with advanced perfProfile [enableBursting][disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should create and attach a volume with basic perfProfile [enableBursting][disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should create replicas on node with matching pod affinity
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should create replicas on node with matching pod node affinity
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should create replicas on node with matching pod node selector
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should create replicas spread across zones for zrs
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should not create replicas on node with matching pod anti-affinity
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should not create replicas on node with non-tolerable taint
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should test an increase in replicas when scaling up
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should test pod failover and check for correct number of replicas
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should test pod failover with cordoning a node
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] Should test pod failover with cordoning a node using ZRS
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should check failed replica attachments are recreated after space is made from a volume detaching.
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should clone a volume from an existing volume and read from it [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should clone a volume of larger size than the source volume and make sure the filesystem is appropriately adjusted [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a block volume on demand and dynamically resize it without detaching [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a deployment object, write and read to it, delete the pod and write and read to it again [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a pod with multiple volumes [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a pod with volume mount subpath [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a pod, write and read to it, take a volume snapshot, and create another pod from the snapshot [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a pod, write to its pv, take a volume snapshot, overwrite data in original pv, create another pod from the snapshot, and read unaltered original data from original pv[disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a raw block volume and a filesystem volume on demand and bind to the same pod [kubernetes.io/azure-disk] [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a raw block volume on demand [kubernetes.io/azure-disk] [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a statefulset object, write and read to it, delete the pod and write and read to it again [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a volume azuredisk with tag [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a volume in separate resource group and bind it to a pod [kubernetes.io/azure-disk] [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a volume on demand and dynamically resize it without detaching [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a volume on demand and mount it as readOnly in a pod [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a volume on demand and resize it [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create a volume on demand with mount options [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create multiple PV objects, bind to PVCs and attach all to a single pod [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create multiple PV objects, bind to PVCs and attach all to different pods on the same node [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should create multiple volumes, each in separate resource groups and attach them to a single pod [kubernetes.io/azure-disk] [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should delete AzVolumeAttachment after pod deleted when maxMountReplicaCount == 0 [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should delete PV with reclaimPolicy "Delete" [kubernetes.io/azure-disk] [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should demote AzVolumeAttachment after pod deleted when maxMountReplicaCount > 0 [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should detach disk after pod deleted when maxMountReplicaCount = 0 [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should receive FailedMount event with invalid mount options [kubernetes.io/azure-disk] [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should retain PV with reclaimPolicy "Retain" [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should succeed when attaching a shared block volume to multiple pods [disk.csi.azure.com][shared disk]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [multi-az] should succeed with advanced perfProfile [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should create and attach a volume with advanced perfProfile [enableBursting][disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should create and attach a volume with basic perfProfile [enableBursting][disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should create replicas on node with matching pod affinity
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should create replicas on node with matching pod node affinity
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should create replicas on node with matching pod node selector
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should create replicas spread across zones for zrs
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should not create replicas on node with matching pod anti-affinity
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should not create replicas on node with non-tolerable taint
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should test an increase in replicas when scaling up
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should test pod failover and check for correct number of replicas
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should test pod failover with cordoning a node
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] Should test pod failover with cordoning a node using ZRS
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should check failed replica attachments are recreated after space is made from a volume detaching.
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should clone a volume from an existing volume and read from it [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should clone a volume of larger size than the source volume and make sure the filesystem is appropriately adjusted [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a block volume on demand and dynamically resize it without detaching [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a pod with volume mount subpath [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a pod, write and read to it, take a volume snapshot, and create another pod from the snapshot [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a pod, write to its pv, take a volume snapshot, overwrite data in original pv, create another pod from the snapshot, and read unaltered original data from original pv[disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a volume azuredisk with tag [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a volume in separate resource group and bind it to a pod [kubernetes.io/azure-disk] [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a volume on demand and dynamically resize it without detaching [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create a volume on demand and resize it [disk.csi.azure.com] [Windows] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should create multiple volumes, each in separate resource groups and attach them to a single pod [kubernetes.io/azure-disk] [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should demote AzVolumeAttachment after pod deleted when maxMountReplicaCount > 0 [disk.csi.azure.com] [csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should retain PV with reclaimPolicy "Retain" [disk.csi.azure.com]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should succeed when attaching a shared block volume to multiple pods [disk.csi.azure.com][shared disk]
AzureDisk CSI Driver End-to-End Tests [It] Dynamic Provisioning [single-az] should succeed with advanced perfProfile [disk.csi.azure.com] [Windows]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should succeed when attaching a shared block volume to multiple pods [disk.csi.azure.com][shared disk]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should succeed when creating a PremiumV2_LRS disk [disk.csi.azure.com][windows]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should succeed when creating a shared disk [disk.csi.azure.com][windows]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should succeed when creating a single pod and with replica attachments [disk.csi.azure.com][csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should succeed when reattaching a disk to a new node on DanglingAttachError [disk.csi.azure.com][csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should use a pre-provisioned volume and mount it as readOnly in a pod [disk.csi.azure.com][windows][csi-azuredisk-scheduler-extender]
AzureDisk CSI Driver End-to-End Tests [It] Pre-Provisioned [single-az] should use a pre-provisioned volume and retain PV with reclaimPolicy "Retain" [disk.csi.azure.com][windows]
... skipping 106 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11345 100 11345 0 0 191k 0 --:--:-- --:--:-- --:--:-- 194k Downloading https://get.helm.sh/helm-v3.11.1-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-a39ff78f6156932a4db851c58bd7b4fb923bd0a5 || make container-all push-manifest Error response from daemon: manifest for k8sprow.azurecr.io/azuredisk-csi:latest-v2-a39ff78f6156932a4db851c58bd7b4fb923bd0a5 not found: manifest unknown: manifest tagged by "latest-v2-a39ff78f6156932a4db851c58bd7b4fb923bd0a5" 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-a39ff78f6156932a4db851c58bd7b4fb923bd0a5 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=a39ff78f6156932a4db851c58bd7b4fb923bd0a5 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2023-02-28T23:28:26Z -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 1499 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 292 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m02/28/23 23:36:23.782[0m [1mSTEP:[0m creating a StorageClass [38;5;243m02/28/23 23:36:23.783[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m02/28/23 23:36:23.815[0m [1mSTEP:[0m creating a PVC [38;5;243m02/28/23 23:36:23.815[0m [1mSTEP:[0m setting up the pod [38;5;243m02/28/23 23:36:23.856[0m [1mSTEP:[0m deploying the pod [38;5;243m02/28/23 23:36:23.856[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/28/23 23:36:23.889[0m Feb 28 23:36:23.889: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-8lp8k" in namespace "azuredisk-8987" to be "Succeeded or Failed" Feb 28 23:36:23.927: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 38.048794ms Feb 28 23:36:25.961: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07177627s Feb 28 23:36:27.961: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.071746444s Feb 28 23:36:29.961: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.071763436s Feb 28 23:36:31.959: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.070153293s Feb 28 23:36:33.960: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.070410356s Feb 28 23:36:35.959: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 12.07012241s Feb 28 23:36:37.961: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 14.071863885s Feb 28 23:36:39.961: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 16.071609368s Feb 28 23:36:41.961: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 18.071767358s Feb 28 23:36:43.959: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 20.070147744s Feb 28 23:36:45.959: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.070231394s [1mSTEP:[0m Saw pod success [38;5;243m02/28/23 23:36:45.959[0m Feb 28 23:36:45.960: INFO: Pod "azuredisk-volume-tester-8lp8k" satisfied condition "Succeeded or Failed" Feb 28 23:36:45.960: INFO: deleting Pod "azuredisk-8987"/"azuredisk-volume-tester-8lp8k" Feb 28 23:36:46.016: INFO: Pod azuredisk-volume-tester-8lp8k has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-8lp8k in namespace azuredisk-8987 [38;5;243m02/28/23 23:36:46.016[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/28/23 23:36:46.082[0m [1mSTEP:[0m checking the PV [38;5;243m02/28/23 23:36:46.114[0m ... skipping 33 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m02/28/23 23:36:23.782[0m [1mSTEP:[0m creating a StorageClass [38;5;243m02/28/23 23:36:23.783[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m02/28/23 23:36:23.815[0m [1mSTEP:[0m creating a PVC [38;5;243m02/28/23 23:36:23.815[0m [1mSTEP:[0m setting up the pod [38;5;243m02/28/23 23:36:23.856[0m [1mSTEP:[0m deploying the pod [38;5;243m02/28/23 23:36:23.856[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/28/23 23:36:23.889[0m Feb 28 23:36:23.889: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-8lp8k" in namespace "azuredisk-8987" to be "Succeeded or Failed" Feb 28 23:36:23.927: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 38.048794ms Feb 28 23:36:25.961: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07177627s Feb 28 23:36:27.961: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.071746444s Feb 28 23:36:29.961: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.071763436s Feb 28 23:36:31.959: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.070153293s Feb 28 23:36:33.960: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.070410356s Feb 28 23:36:35.959: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 12.07012241s Feb 28 23:36:37.961: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 14.071863885s Feb 28 23:36:39.961: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 16.071609368s Feb 28 23:36:41.961: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 18.071767358s Feb 28 23:36:43.959: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Pending", Reason="", readiness=false. Elapsed: 20.070147744s Feb 28 23:36:45.959: INFO: Pod "azuredisk-volume-tester-8lp8k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.070231394s [1mSTEP:[0m Saw pod success [38;5;243m02/28/23 23:36:45.959[0m Feb 28 23:36:45.960: INFO: Pod "azuredisk-volume-tester-8lp8k" satisfied condition "Succeeded or Failed" Feb 28 23:36:45.960: INFO: deleting Pod "azuredisk-8987"/"azuredisk-volume-tester-8lp8k" Feb 28 23:36:46.016: INFO: Pod azuredisk-volume-tester-8lp8k has the following logs: hello world [1mSTEP:[0m Deleting pod azuredisk-volume-tester-8lp8k in namespace azuredisk-8987 [38;5;243m02/28/23 23:36:46.016[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/28/23 23:36:46.082[0m [1mSTEP:[0m checking the PV [38;5;243m02/28/23 23:36:46.114[0m ... skipping 142 lines ... [1mSTEP:[0m setting up the PVC and PV [38;5;243m02/28/23 23:37:29.142[0m [1mSTEP:[0m creating a PVC [38;5;243m02/28/23 23:37:29.142[0m [1mSTEP:[0m setting up the pod [38;5;243m02/28/23 23:37:29.176[0m [1mSTEP:[0m deploying the pod [38;5;243m02/28/23 23:37:29.176[0m [1mSTEP:[0m checking that the pod has 'FailedMount' event [38;5;243m02/28/23 23:37:29.208[0m Feb 28 23:37:47.274: INFO: deleting Pod "azuredisk-6500"/"azuredisk-volume-tester-x9qqs" Feb 28 23:37:47.306: INFO: Error getting logs for pod azuredisk-volume-tester-x9qqs: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-x9qqs) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-x9qqs in namespace azuredisk-6500 [38;5;243m02/28/23 23:37:47.306[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/28/23 23:37:47.37[0m [1mSTEP:[0m checking the PV [38;5;243m02/28/23 23:37:47.401[0m Feb 28 23:37:47.401: INFO: deleting PVC "azuredisk-6500"/"pvc-zpmcs" Feb 28 23:37:47.401: INFO: Deleting PersistentVolumeClaim "pvc-zpmcs" [1mSTEP:[0m waiting for claim's PV "pvc-f322c57f-5935-4c08-bf41-831b1a2e5ec8" to be deleted [38;5;243m02/28/23 23:37:47.436[0m ... skipping 53 lines ... [1mSTEP:[0m setting up the PVC and PV [38;5;243m02/28/23 23:37:29.142[0m [1mSTEP:[0m creating a PVC [38;5;243m02/28/23 23:37:29.142[0m [1mSTEP:[0m setting up the pod [38;5;243m02/28/23 23:37:29.176[0m [1mSTEP:[0m deploying the pod [38;5;243m02/28/23 23:37:29.176[0m [1mSTEP:[0m checking that the pod has 'FailedMount' event [38;5;243m02/28/23 23:37:29.208[0m Feb 28 23:37:47.274: INFO: deleting Pod "azuredisk-6500"/"azuredisk-volume-tester-x9qqs" Feb 28 23:37:47.306: INFO: Error getting logs for pod azuredisk-volume-tester-x9qqs: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-x9qqs) [1mSTEP:[0m Deleting pod azuredisk-volume-tester-x9qqs in namespace azuredisk-6500 [38;5;243m02/28/23 23:37:47.306[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/28/23 23:37:47.37[0m [1mSTEP:[0m checking the PV [38;5;243m02/28/23 23:37:47.401[0m Feb 28 23:37:47.401: INFO: deleting PVC "azuredisk-6500"/"pvc-zpmcs" Feb 28 23:37:47.401: INFO: Deleting PersistentVolumeClaim "pvc-zpmcs" [1mSTEP:[0m waiting for claim's PV "pvc-f322c57f-5935-4c08-bf41-831b1a2e5ec8" to be deleted [38;5;243m02/28/23 23:37:47.436[0m ... skipping 50 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m02/28/23 23:40:14.173[0m [1mSTEP:[0m creating a StorageClass [38;5;243m02/28/23 23:40:14.173[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m02/28/23 23:40:14.205[0m [1mSTEP:[0m creating a PVC [38;5;243m02/28/23 23:40:14.205[0m [1mSTEP:[0m setting up the pod [38;5;243m02/28/23 23:40:14.238[0m [1mSTEP:[0m deploying the pod [38;5;243m02/28/23 23:40:14.238[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/28/23 23:40:14.271[0m Feb 28 23:40:14.271: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-gn5bx" in namespace "azuredisk-3428" to be "Succeeded or Failed" Feb 28 23:40:14.303: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 31.64317ms Feb 28 23:40:16.336: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06454049s Feb 28 23:40:18.337: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.065475856s Feb 28 23:40:20.336: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.064683139s Feb 28 23:40:22.337: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066177711s Feb 28 23:40:24.336: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.06470339s Feb 28 23:40:26.336: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.065145221s Feb 28 23:40:28.336: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 14.065291509s Feb 28 23:40:30.335: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.063417186s Feb 28 23:40:32.337: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.065472988s Feb 28 23:40:34.337: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 20.066114463s Feb 28 23:40:36.336: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.064994961s [1mSTEP:[0m Saw pod success [38;5;243m02/28/23 23:40:36.336[0m Feb 28 23:40:36.336: INFO: Pod "azuredisk-volume-tester-gn5bx" satisfied condition "Succeeded or Failed" Feb 28 23:40:36.336: INFO: deleting Pod "azuredisk-3428"/"azuredisk-volume-tester-gn5bx" Feb 28 23:40:36.390: INFO: Pod azuredisk-volume-tester-gn5bx has the following logs: e2e-test [1mSTEP:[0m Deleting pod azuredisk-volume-tester-gn5bx in namespace azuredisk-3428 [38;5;243m02/28/23 23:40:36.39[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/28/23 23:40:36.46[0m [1mSTEP:[0m checking the PV [38;5;243m02/28/23 23:40:36.492[0m ... skipping 33 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m02/28/23 23:40:14.173[0m [1mSTEP:[0m creating a StorageClass [38;5;243m02/28/23 23:40:14.173[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m02/28/23 23:40:14.205[0m [1mSTEP:[0m creating a PVC [38;5;243m02/28/23 23:40:14.205[0m [1mSTEP:[0m setting up the pod [38;5;243m02/28/23 23:40:14.238[0m [1mSTEP:[0m deploying the pod [38;5;243m02/28/23 23:40:14.238[0m [1mSTEP:[0m checking that the pod's command exits with no error [38;5;243m02/28/23 23:40:14.271[0m Feb 28 23:40:14.271: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-gn5bx" in namespace "azuredisk-3428" to be "Succeeded or Failed" Feb 28 23:40:14.303: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 31.64317ms Feb 28 23:40:16.336: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06454049s Feb 28 23:40:18.337: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 4.065475856s Feb 28 23:40:20.336: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 6.064683139s Feb 28 23:40:22.337: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 8.066177711s Feb 28 23:40:24.336: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 10.06470339s Feb 28 23:40:26.336: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 12.065145221s Feb 28 23:40:28.336: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 14.065291509s Feb 28 23:40:30.335: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 16.063417186s Feb 28 23:40:32.337: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 18.065472988s Feb 28 23:40:34.337: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Pending", Reason="", readiness=false. Elapsed: 20.066114463s Feb 28 23:40:36.336: INFO: Pod "azuredisk-volume-tester-gn5bx": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.064994961s [1mSTEP:[0m Saw pod success [38;5;243m02/28/23 23:40:36.336[0m Feb 28 23:40:36.336: INFO: Pod "azuredisk-volume-tester-gn5bx" satisfied condition "Succeeded or Failed" Feb 28 23:40:36.336: INFO: deleting Pod "azuredisk-3428"/"azuredisk-volume-tester-gn5bx" Feb 28 23:40:36.390: INFO: Pod azuredisk-volume-tester-gn5bx has the following logs: e2e-test [1mSTEP:[0m Deleting pod azuredisk-volume-tester-gn5bx in namespace azuredisk-3428 [38;5;243m02/28/23 23:40:36.39[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/28/23 23:40:36.46[0m [1mSTEP:[0m checking the PV [38;5;243m02/28/23 23:40:36.492[0m ... skipping 104 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m02/28/23 23:41:18.84[0m [1mSTEP:[0m creating a StorageClass [38;5;243m02/28/23 23:41:18.84[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m02/28/23 23:41:18.872[0m [1mSTEP:[0m creating a PVC [38;5;243m02/28/23 23:41:18.872[0m [1mSTEP:[0m setting up the pod [38;5;243m02/28/23 23:41:18.906[0m [1mSTEP:[0m deploying the pod [38;5;243m02/28/23 23:41:18.906[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m02/28/23 23:41:18.938[0m Feb 28 23:41:18.938: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-77rgg" in namespace "azuredisk-1905" to be "Error status code" Feb 28 23:41:18.970: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 32.185132ms Feb 28 23:41:21.004: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06604206s Feb 28 23:41:23.004: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.066112247s Feb 28 23:41:25.004: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.066195656s Feb 28 23:41:27.002: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.064338828s Feb 28 23:41:29.003: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.06547196s Feb 28 23:41:31.003: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.065145076s Feb 28 23:41:33.004: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.065787405s Feb 28 23:41:35.003: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.065319064s Feb 28 23:41:37.004: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 18.06577106s Feb 28 23:41:39.004: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 20.066371293s Feb 28 23:41:41.003: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Failed", Reason="", readiness=false. Elapsed: 22.064911538s [1mSTEP:[0m Saw pod failure [38;5;243m02/28/23 23:41:41.003[0m Feb 28 23:41:41.003: INFO: Pod "azuredisk-volume-tester-77rgg" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m02/28/23 23:41:41.003[0m Feb 28 23:41:41.038: INFO: deleting Pod "azuredisk-1905"/"azuredisk-volume-tester-77rgg" Feb 28 23:41:41.072: INFO: Pod azuredisk-volume-tester-77rgg has the following logs: touch: /mnt/test-1/data: Read-only file system [1mSTEP:[0m Deleting pod azuredisk-volume-tester-77rgg in namespace azuredisk-1905 [38;5;243m02/28/23 23:41:41.072[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/28/23 23:41:41.141[0m ... skipping 34 lines ... [1mSTEP:[0m setting up the StorageClass [38;5;243m02/28/23 23:41:18.84[0m [1mSTEP:[0m creating a StorageClass [38;5;243m02/28/23 23:41:18.84[0m [1mSTEP:[0m setting up the PVC and PV [38;5;243m02/28/23 23:41:18.872[0m [1mSTEP:[0m creating a PVC [38;5;243m02/28/23 23:41:18.872[0m [1mSTEP:[0m setting up the pod [38;5;243m02/28/23 23:41:18.906[0m [1mSTEP:[0m deploying the pod [38;5;243m02/28/23 23:41:18.906[0m [1mSTEP:[0m checking that the pod's command exits with an error [38;5;243m02/28/23 23:41:18.938[0m Feb 28 23:41:18.938: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-77rgg" in namespace "azuredisk-1905" to be "Error status code" Feb 28 23:41:18.970: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 32.185132ms Feb 28 23:41:21.004: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06604206s Feb 28 23:41:23.004: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.066112247s Feb 28 23:41:25.004: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.066195656s Feb 28 23:41:27.002: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.064338828s Feb 28 23:41:29.003: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.06547196s Feb 28 23:41:31.003: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.065145076s Feb 28 23:41:33.004: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.065787405s Feb 28 23:41:35.003: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.065319064s Feb 28 23:41:37.004: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 18.06577106s Feb 28 23:41:39.004: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Pending", Reason="", readiness=false. Elapsed: 20.066371293s Feb 28 23:41:41.003: INFO: Pod "azuredisk-volume-tester-77rgg": Phase="Failed", Reason="", readiness=false. Elapsed: 22.064911538s [1mSTEP:[0m Saw pod failure [38;5;243m02/28/23 23:41:41.003[0m Feb 28 23:41:41.003: INFO: Pod "azuredisk-volume-tester-77rgg" satisfied condition "Error status code" [1mSTEP:[0m checking that pod logs contain expected message [38;5;243m02/28/23 23:41:41.003[0m Feb 28 23:41:41.038: INFO: deleting Pod "azuredisk-1905"/"azuredisk-volume-tester-77rgg" Feb 28 23:41:41.072: INFO: Pod azuredisk-volume-tester-77rgg has the following logs: touch: /mnt/test-1/data: Read-only file system [1mSTEP:[0m Deleting pod azuredisk-volume-tester-77rgg in namespace azuredisk-1905 [38;5;243m02/28/23 23:41:41.072[0m [1mSTEP:[0m validating provisioned PV [38;5;243m02/28/23 23:41:41.141[0m ... skipping 371 lines ... Feb 28 23:47:44.920: INFO: Pod "azuredisk-volume-tester-b6smr-644fc8784f-m8tbh": Phase="Pending", Reason="", readiness=false. Elapsed: 31.761928ms Feb 28 23:47:46.954: INFO: Pod "azuredisk-volume-tester-b6smr-644fc8784f-m8tbh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065345701s Feb 28 23:47:48.954: INFO: Pod "azuredisk-volume-tester-b6smr-644fc8784f-m8tbh": Phase="Pending", Reason="", readiness=false. Elapsed: 4.066178111s Feb 28 23:47:50.953: INFO: Pod "azuredisk-volume-tester-b6smr-644fc8784f-m8tbh": Phase="Pending", Reason="", readiness=false. Elapsed: 6.064393229s Feb 28 23:47:52.954: INFO: Pod "azuredisk-volume-tester-b6smr-644fc8784f-m8tbh": Phase="Pending", Reason="", readiness=false. Elapsed: 8.065494262s Feb 28 23:47:54.954: INFO: Pod "azuredisk-volume-tester-b6smr-644fc8784f-m8tbh": Phase="Pending", Reason="", readiness=false. Elapsed: 10.065852198s {"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-02-28T23:47:56Z"} ++ early_exit_handler ++ '[' -n 170 ']' ++ kill -TERM 170 ++ cleanup_dind ++ [[ true == \t\r\u\e ]] ++ echo 'Cleaning up after docker' ... skipping 4 lines ...