kubernetes-sigs/azurefile-csi-driver PR #1013 pull-azurefile-csi-driver-e2e-capz #1525726560051531776
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | andyzhangx: feat: add fsGroupChangePolicy for nfs protocol |
| Result | ABORTED |
| Tests | 0 failed / 31 succeeded |
| Started | |
| Elapsed | 48m30s |
| Revision | 79af3e5b54439ecf3a3cc6e38ad29409f9fb9fa3 |
| Refs |
1013 |
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning [env] should retain PV with reclaimPolicy "Retain" [file.csi.azure.com] [disk]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a NFS volume on demand on a storage account with private endpoint [file.csi.azure.com] [nfs]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a NFS volume on demand with mount options [file.csi.azure.com] [nfs]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a deployment object, write and read to it, delete the pod and write and read to it again [kubernetes.io/azure-file] [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a pod with multiple NFS volumes [file.csi.azure.com]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a pod with multiple volumes [kubernetes.io/azure-file] [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a pod with volume mount subpath [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a pod, write and read to it, take a volume snapshot, and validate whether it is ready to use [file.csi.azure.com]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a statefulset object, write and read to it, delete the pod and write and read to it again [file.csi.azure.com]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a storage account with tags [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a vhd disk volume on demand [kubernetes.io/azure-file] [file.csi.azure.com][disk]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a vhd disk volume on demand and mount it as readOnly in a pod [file.csi.azure.com][disk]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a volume on demand and mount it as readOnly in a pod [kubernetes.io/azure-file] [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a volume on demand and resize it [kubernetes.io/azure-file] [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a volume on demand with mount options (Bring Your Own Key) [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a volume on demand with mount options [kubernetes.io/azure-file] [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a volume on demand with useDataPlaneAPI [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create an CSI inline volume [file.csi.azure.com]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create multiple PV objects, bind to PVCs and attach all to different pods on the same node [file.csi.azure.com][disk]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create multiple PV objects, bind to PVCs and attach all to different pods on the same node [kubernetes.io/azure-file] [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should delete PV with reclaimPolicy "Delete" [file.csi.azure.com] [disk]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should delete PV with reclaimPolicy "Delete" [kubernetes.io/azure-file] [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should mount on-prem smb server [file.csi.azure.com]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should receive FailedMount event with invalid mount options [file.csi.azure.com] [disk]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should receive FailedMount event with invalid mount options [file.csi.azure.com] [disk]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should retain PV with reclaimPolicy "Retain" [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Pre-Provisioned should use a pre-provisioned volume and mount it as readOnly in a pod [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Pre-Provisioned should use a pre-provisioned volume and mount it by multiple pods [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Pre-Provisioned should use a pre-provisioned volume and retain PV with reclaimPolicy "Retain" [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Pre-Provisioned should use existing credentials in k8s cluster [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Pre-Provisioned should use provided credentials [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a deployment object, write and read to it, delete the pod and write and read to it again [file.csi.azure.com] [disk]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a volume after driver restart [kubernetes.io/azure-file] [file.csi.azure.com]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create an inline volume by in-tree driver [kubernetes.io/azure-file]
... skipping 671 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 # Deploy CAPI curl --retry 3 -sSL https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.1.2/cluster-api-components.yaml | /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/envsubst-v2.0.0-20210730161058-179042472c46 | kubectl apply -f - namespace/capi-system created customresourcedefinition.apiextensions.k8s.io/clusterclasses.cluster.x-k8s.io created ... skipping 132 lines ... # Wait for the kubeconfig to become available. timeout --foreground 300 bash -c "while ! kubectl get secrets | grep capz-3iodo5-kubeconfig; do sleep 1; done" capz-3iodo5-kubeconfig cluster.x-k8s.io/secret 1 1s # Get kubeconfig and store it locally. kubectl get secrets capz-3iodo5-kubeconfig -o json | jq -r .data.value | base64 --decode > ./kubeconfig timeout --foreground 600 bash -c "while ! kubectl --kubeconfig=./kubeconfig get nodes | grep control-plane; do sleep 1; done" error: the server doesn't have a resource type "nodes" capz-3iodo5-control-plane-wv6gj NotReady <none> 4s v1.22.1 run "kubectl --kubeconfig=./kubeconfig ..." to work with the new target cluster make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' Waiting for 1 control plane machine(s), 2 worker machine(s), and windows machine(s) to become Ready node/capz-3iodo5-control-plane-wv6gj condition met node/capz-3iodo5-md-0-6w6rt condition met ... skipping 35 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11156 100 11156 0 0 201k 0 --:--:-- --:--:-- --:--:-- 205k Downloading https://get.helm.sh/helm-v3.8.2-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/azurefile-csi:e2e-d99f5d84281f07b5e3460fbb6f18ec7695b93915 || make container-all push-manifest Error response from daemon: manifest for capzci.azurecr.io/azurefile-csi:e2e-d99f5d84281f07b5e3460fbb6f18ec7695b93915 not found: manifest unknown: manifest tagged by "e2e-d99f5d84281f07b5e3460fbb6f18ec7695b93915" is not found make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azurefile-csi-driver' CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.driverVersion=e2e-d99f5d84281f07b5e3460fbb6f18ec7695b93915 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.gitCommit=d99f5d84281f07b5e3460fbb6f18ec7695b93915 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.buildDate=2022-05-15T06:48:47Z -s -w -extldflags '-static'" -mod vendor -o _output/amd64/azurefileplugin.exe ./pkg/azurefileplugin 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 1784 lines ... type: string type: object oneOf: - required: ["persistentVolumeClaimName"] - required: ["volumeSnapshotContentName"] volumeSnapshotClassName: description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.' type: string required: - source type: object status: description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object. ... skipping 2 lines ... description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.' type: string creationTime: description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it may indicate that the creation time of the snapshot is unknown. format: date-time type: string error: description: error is the last observed error during snapshot creation, if any. This field could be helpful to upper level controllers(i.e., application controller) to decide whether they should continue on waiting for the snapshot to be created based on the type of error reported. The snapshot controller will keep retrying when an error occurrs during the snapshot creation. Upon success, this error field will be cleared. properties: message: description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.' type: string time: description: time is the timestamp when the error was encountered. format: date-time type: string type: object readyToUse: description: readyToUse indicates if the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown. type: boolean restoreSize: type: string description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown. pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$ x-kubernetes-int-or-string: true type: object required: - spec type: object ... skipping 60 lines ... type: string volumeSnapshotContentName: description: volumeSnapshotContentName specifies the name of a pre-existing VolumeSnapshotContent object representing an existing volume snapshot. This field should be set if the snapshot already exists and only needs a representation in Kubernetes. This field is immutable. type: string type: object volumeSnapshotClassName: description: 'VolumeSnapshotClassName is the name of the VolumeSnapshotClass requested by the VolumeSnapshot. VolumeSnapshotClassName may be left nil to indicate that the default SnapshotClass should be used. A given cluster may have multiple default Volume SnapshotClasses: one default per CSI Driver. If a VolumeSnapshot does not specify a SnapshotClass, VolumeSnapshotSource will be checked to figure out what the associated CSI Driver is, and the default VolumeSnapshotClass associated with that CSI Driver will be used. If more than one VolumeSnapshotClass exist for a given CSI Driver and more than one have been marked as default, CreateSnapshot will fail and generate an event. Empty string is not allowed for this field.' type: string required: - source type: object status: description: status represents the current information of a snapshot. Consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object. ... skipping 2 lines ... description: 'boundVolumeSnapshotContentName is the name of the VolumeSnapshotContent object to which this VolumeSnapshot object intends to bind to. If not specified, it indicates that the VolumeSnapshot object has not been successfully bound to a VolumeSnapshotContent object yet. NOTE: To avoid possible security issues, consumers must verify binding between VolumeSnapshot and VolumeSnapshotContent objects is successful (by validating that both VolumeSnapshot and VolumeSnapshotContent point at each other) before using this object.' type: string creationTime: description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it may indicate that the creation time of the snapshot is unknown. format: date-time type: string error: description: error is the last observed error during snapshot creation, if any. This field could be helpful to upper level controllers(i.e., application controller) to decide whether they should continue on waiting for the snapshot to be created based on the type of error reported. The snapshot controller will keep retrying when an error occurrs during the snapshot creation. Upon success, this error field will be cleared. properties: message: description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.' type: string time: description: time is the timestamp when the error was encountered. format: date-time type: string type: object readyToUse: description: readyToUse indicates if the snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown. type: boolean restoreSize: type: string description: restoreSize represents the minimum size of volume required to create a volume from this snapshot. In dynamic snapshot creation case, this field will be filled in by the snapshot controller with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown. pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$ x-kubernetes-int-or-string: true type: object required: - spec type: object ... skipping 254 lines ... description: status represents the current information of a snapshot. properties: creationTime: description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it indicates the creation time is unknown. The format of this field is a Unix nanoseconds time encoded as an int64. On Unix, the command `date +%s%N` returns the current time in nanoseconds since 1970-01-01 00:00:00 UTC. format: int64 type: integer error: description: error is the last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared. properties: message: description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.' type: string time: description: time is the timestamp when the error was encountered. format: date-time type: string type: object readyToUse: description: readyToUse indicates if a snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown. type: boolean restoreSize: description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown. format: int64 minimum: 0 type: integer snapshotHandle: description: snapshotHandle is the CSI "snapshot_id" of a snapshot on the underlying storage system. If not specified, it indicates that dynamic snapshot creation has either failed or it is still in progress. type: string type: object required: - spec type: object served: true ... skipping 108 lines ... description: status represents the current information of a snapshot. properties: creationTime: description: creationTime is the timestamp when the point-in-time snapshot is taken by the underlying storage system. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "creation_time" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "creation_time" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. If not specified, it indicates the creation time is unknown. The format of this field is a Unix nanoseconds time encoded as an int64. On Unix, the command `date +%s%N` returns the current time in nanoseconds since 1970-01-01 00:00:00 UTC. format: int64 type: integer error: description: error is the last observed error during snapshot creation, if any. Upon success after retry, this error field will be cleared. properties: message: description: 'message is a string detailing the encountered error during snapshot creation if specified. NOTE: message may be logged, and it should not contain sensitive information.' type: string time: description: time is the timestamp when the error was encountered. format: date-time type: string type: object readyToUse: description: readyToUse indicates if a snapshot is ready to be used to restore a volume. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "ready_to_use" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "ready_to_use" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it, otherwise, this field will be set to "True". If not specified, it means the readiness of a snapshot is unknown. type: boolean restoreSize: description: restoreSize represents the complete size of the snapshot in bytes. In dynamic snapshot creation case, this field will be filled in by the CSI snapshotter sidecar with the "size_bytes" value returned from CSI "CreateSnapshot" gRPC call. For a pre-existing snapshot, this field will be filled with the "size_bytes" value returned from the CSI "ListSnapshots" gRPC call if the driver supports it. When restoring a volume from this snapshot, the size of the volume MUST NOT be smaller than the restoreSize if it is specified, otherwise the restoration will fail. If not specified, it indicates that the size is unknown. format: int64 minimum: 0 type: integer snapshotHandle: description: snapshotHandle is the CSI "snapshot_id" of a snapshot on the underlying storage system. If not specified, it indicates that dynamic snapshot creation has either failed or it is still in progress. type: string type: object required: - spec type: object served: true ... skipping 938 lines ... image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.4.0" args: - "-csi-address=$(ADDRESS)" - "-v=2" - "-leader-election" - "--leader-election-namespace=kube-system" - '-handle-volume-inuse-error=false' - '-timeout=120s' - '-feature-gates=RecoverVolumeExpansionFailure=true' env: - name: ADDRESS value: /csi/csi.sock imagePullPolicy: IfNotPresent ... skipping 209 lines ... Git Commit: N/A Go Version: go1.18.1 Platform: linux/amd64 Streaming logs below: [1mSTEP[0m: Building a namespace api object, basename azurefile W0515 07:01:42.721960 36277 azure.go:78] InitializeCloudFromSecret: failed to get cloud config from secret /: failed to get secret /: resource name may not be empty I0515 07:01:42.724019 36277 driver.go:93] Enabling controller service capability: CREATE_DELETE_VOLUME I0515 07:01:42.724044 36277 driver.go:93] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME I0515 07:01:42.724049 36277 driver.go:93] Enabling controller service capability: CREATE_DELETE_SNAPSHOT I0515 07:01:42.724055 36277 driver.go:93] Enabling controller service capability: EXPAND_VOLUME I0515 07:01:42.724058 36277 driver.go:93] Enabling controller service capability: SINGLE_NODE_MULTI_WRITER I0515 07:01:42.724065 36277 driver.go:112] Enabling volume access mode: SINGLE_NODE_WRITER ... skipping 23 lines ... May 15 07:02:04.892: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-drrf9] to have phase Bound May 15 07:02:04.921: INFO: PersistentVolumeClaim pvc-drrf9 found and phase=Bound (28.89289ms) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with an error May 15 07:02:05.009: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-4xqng" in namespace "azurefile-8081" to be "Error status code" May 15 07:02:05.041: INFO: Pod "azurefile-volume-tester-4xqng": Phase="Pending", Reason="", readiness=false. Elapsed: 32.005993ms May 15 07:02:07.072: INFO: Pod "azurefile-volume-tester-4xqng": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06285227s May 15 07:02:09.104: INFO: Pod "azurefile-volume-tester-4xqng": Phase="Failed", Reason="", readiness=false. Elapsed: 4.095019198s [1mSTEP[0m: Saw pod failure May 15 07:02:09.104: INFO: Pod "azurefile-volume-tester-4xqng" satisfied condition "Error status code" [1mSTEP[0m: checking that pod logs contain expected message May 15 07:02:09.150: INFO: deleting Pod "azurefile-8081"/"azurefile-volume-tester-4xqng" May 15 07:02:09.181: INFO: Pod azurefile-volume-tester-4xqng has the following logs: /bin/sh: can't create /mnt/test-1/data: Read-only file system [1mSTEP[0m: Deleting pod azurefile-volume-tester-4xqng in namespace azurefile-8081 May 15 07:02:09.219: INFO: deleting PVC "azurefile-8081"/"pvc-drrf9" ... skipping 37 lines ... May 15 07:02:10.893: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-sj9lv] to have phase Bound May 15 07:02:10.921: INFO: PersistentVolumeClaim pvc-sj9lv found and phase=Bound (28.668749ms) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:02:11.008: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-kc5mg" in namespace "azurefile-2540" to be "Succeeded or Failed" May 15 07:02:11.039: INFO: Pod "azurefile-volume-tester-kc5mg": Phase="Pending", Reason="", readiness=false. Elapsed: 31.00381ms May 15 07:02:13.075: INFO: Pod "azurefile-volume-tester-kc5mg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.066756219s [1mSTEP[0m: Saw pod success May 15 07:02:13.075: INFO: Pod "azurefile-volume-tester-kc5mg" satisfied condition "Succeeded or Failed" [1mSTEP[0m: setting up the PV [1mSTEP[0m: creating a PV [1mSTEP[0m: setting up the PVC [1mSTEP[0m: creating a PVC [1mSTEP[0m: waiting for PVC to be in phase "Bound" May 15 07:02:13.134: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-4jbwq] to have phase Bound May 15 07:02:13.162: INFO: PersistentVolumeClaim pvc-4jbwq found and phase=Bound (28.004187ms) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:02:13.250: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-hdzkg" in namespace "azurefile-2540" to be "Succeeded or Failed" May 15 07:02:13.279: INFO: Pod "azurefile-volume-tester-hdzkg": Phase="Pending", Reason="", readiness=false. Elapsed: 28.694529ms May 15 07:02:15.311: INFO: Pod "azurefile-volume-tester-hdzkg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.060272268s [1mSTEP[0m: Saw pod success May 15 07:02:15.311: INFO: Pod "azurefile-volume-tester-hdzkg" satisfied condition "Succeeded or Failed" [1mSTEP[0m: setting up the PV [1mSTEP[0m: creating a PV [1mSTEP[0m: setting up the PVC [1mSTEP[0m: creating a PVC [1mSTEP[0m: waiting for PVC to be in phase "Bound" May 15 07:02:15.371: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-zl75v] to have phase Bound May 15 07:02:15.399: INFO: PersistentVolumeClaim pvc-zl75v found and phase=Bound (28.138538ms) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:02:15.487: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-5c2nr" in namespace "azurefile-2540" to be "Succeeded or Failed" May 15 07:02:15.516: INFO: Pod "azurefile-volume-tester-5c2nr": Phase="Pending", Reason="", readiness=false. Elapsed: 28.759405ms May 15 07:02:17.547: INFO: Pod "azurefile-volume-tester-5c2nr": Phase="Running", Reason="", readiness=true. Elapsed: 2.060019282s May 15 07:02:19.578: INFO: Pod "azurefile-volume-tester-5c2nr": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.090690289s [1mSTEP[0m: Saw pod success May 15 07:02:19.578: INFO: Pod "azurefile-volume-tester-5c2nr" satisfied condition "Succeeded or Failed" [1mSTEP[0m: setting up the PV [1mSTEP[0m: creating a PV [1mSTEP[0m: setting up the PVC [1mSTEP[0m: creating a PVC [1mSTEP[0m: waiting for PVC to be in phase "Bound" May 15 07:02:19.636: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-5zmwz] to have phase Bound May 15 07:02:19.664: INFO: PersistentVolumeClaim pvc-5zmwz found and phase=Bound (27.874071ms) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:02:19.757: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-56b5n" in namespace "azurefile-2540" to be "Succeeded or Failed" May 15 07:02:19.794: INFO: Pod "azurefile-volume-tester-56b5n": Phase="Pending", Reason="", readiness=false. Elapsed: 36.028595ms May 15 07:02:21.824: INFO: Pod "azurefile-volume-tester-56b5n": Phase="Running", Reason="", readiness=true. Elapsed: 2.066590031s May 15 07:02:23.855: INFO: Pod "azurefile-volume-tester-56b5n": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.09708633s [1mSTEP[0m: Saw pod success May 15 07:02:23.855: INFO: Pod "azurefile-volume-tester-56b5n" satisfied condition "Succeeded or Failed" [1mSTEP[0m: setting up the PV [1mSTEP[0m: creating a PV [1mSTEP[0m: setting up the PVC [1mSTEP[0m: creating a PVC [1mSTEP[0m: waiting for PVC to be in phase "Bound" May 15 07:02:23.913: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-9fxxn] to have phase Bound May 15 07:02:23.943: INFO: PersistentVolumeClaim pvc-9fxxn found and phase=Bound (29.575623ms) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:02:24.031: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-5vs9x" in namespace "azurefile-2540" to be "Succeeded or Failed" May 15 07:02:24.061: INFO: Pod "azurefile-volume-tester-5vs9x": Phase="Pending", Reason="", readiness=false. Elapsed: 30.24386ms May 15 07:02:26.092: INFO: Pod "azurefile-volume-tester-5vs9x": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.061001411s [1mSTEP[0m: Saw pod success May 15 07:02:26.092: INFO: Pod "azurefile-volume-tester-5vs9x" satisfied condition "Succeeded or Failed" [1mSTEP[0m: setting up the PV [1mSTEP[0m: creating a PV [1mSTEP[0m: setting up the PVC [1mSTEP[0m: creating a PVC [1mSTEP[0m: waiting for PVC to be in phase "Bound" May 15 07:02:26.152: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-7j564] to have phase Bound May 15 07:02:26.180: INFO: PersistentVolumeClaim pvc-7j564 found and phase=Bound (27.768968ms) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:02:26.270: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-s82d5" in namespace "azurefile-2540" to be "Succeeded or Failed" May 15 07:02:26.298: INFO: Pod "azurefile-volume-tester-s82d5": Phase="Pending", Reason="", readiness=false. Elapsed: 27.979286ms May 15 07:02:28.332: INFO: Pod "azurefile-volume-tester-s82d5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.061999289s [1mSTEP[0m: Saw pod success May 15 07:02:28.332: INFO: Pod "azurefile-volume-tester-s82d5" satisfied condition "Succeeded or Failed" May 15 07:02:28.332: INFO: deleting Pod "azurefile-2540"/"azurefile-volume-tester-s82d5" May 15 07:02:28.369: INFO: Pod azurefile-volume-tester-s82d5 has the following logs: hello world [1mSTEP[0m: Deleting pod azurefile-volume-tester-s82d5 in namespace azurefile-2540 May 15 07:02:28.409: INFO: deleting PVC "azurefile-2540"/"pvc-7j564" May 15 07:02:28.409: INFO: Deleting PersistentVolumeClaim "pvc-7j564" ... skipping 143 lines ... May 15 07:02:32.519: INFO: PersistentVolumeClaim pvc-5c4rw found but phase is Pending instead of Bound. May 15 07:02:34.549: INFO: PersistentVolumeClaim pvc-5c4rw found and phase=Bound (2.058149629s) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:02:34.638: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-dr7m9" in namespace "azurefile-5466" to be "Succeeded or Failed" May 15 07:02:34.667: INFO: Pod "azurefile-volume-tester-dr7m9": Phase="Pending", Reason="", readiness=false. Elapsed: 28.57915ms May 15 07:02:36.697: INFO: Pod "azurefile-volume-tester-dr7m9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.058889946s [1mSTEP[0m: Saw pod success May 15 07:02:36.697: INFO: Pod "azurefile-volume-tester-dr7m9" satisfied condition "Succeeded or Failed" May 15 07:02:36.697: INFO: deleting Pod "azurefile-5466"/"azurefile-volume-tester-dr7m9" May 15 07:02:36.728: INFO: Pod azurefile-volume-tester-dr7m9 has the following logs: hello world [1mSTEP[0m: Deleting pod azurefile-volume-tester-dr7m9 in namespace azurefile-5466 May 15 07:02:36.768: INFO: deleting PVC "azurefile-5466"/"pvc-5c4rw" May 15 07:02:36.768: INFO: Deleting PersistentVolumeClaim "pvc-5c4rw" ... skipping 33 lines ... May 15 07:02:38.420: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-sz8q7] to have phase Bound May 15 07:02:38.448: INFO: PersistentVolumeClaim pvc-sz8q7 found and phase=Bound (27.708155ms) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:02:38.534: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-x4z75" in namespace "azurefile-2790" to be "Succeeded or Failed" May 15 07:02:38.567: INFO: Pod "azurefile-volume-tester-x4z75": Phase="Pending", Reason="", readiness=false. Elapsed: 32.567539ms May 15 07:02:40.597: INFO: Pod "azurefile-volume-tester-x4z75": Phase="Running", Reason="", readiness=true. Elapsed: 2.062775181s May 15 07:02:42.630: INFO: Pod "azurefile-volume-tester-x4z75": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.095323471s [1mSTEP[0m: Saw pod success May 15 07:02:42.630: INFO: Pod "azurefile-volume-tester-x4z75" satisfied condition "Succeeded or Failed" May 15 07:02:42.630: INFO: deleting Pod "azurefile-2790"/"azurefile-volume-tester-x4z75" May 15 07:02:42.663: INFO: Pod azurefile-volume-tester-x4z75 has the following logs: hello world [1mSTEP[0m: Deleting pod azurefile-volume-tester-x4z75 in namespace azurefile-2790 May 15 07:02:42.717: INFO: deleting PVC "azurefile-2790"/"pvc-sz8q7" May 15 07:02:42.717: INFO: Deleting PersistentVolumeClaim "pvc-sz8q7" ... skipping 134 lines ... May 15 07:04:46.343: INFO: PersistentVolumeClaim pvc-wmhqc found but phase is Pending instead of Bound. May 15 07:04:48.375: INFO: PersistentVolumeClaim pvc-wmhqc found and phase=Bound (1m37.452916667s) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:04:48.462: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-b6kjs" in namespace "azurefile-5194" to be "Succeeded or Failed" May 15 07:04:48.490: INFO: Pod "azurefile-volume-tester-b6kjs": Phase="Pending", Reason="", readiness=false. Elapsed: 27.772437ms May 15 07:04:50.519: INFO: Pod "azurefile-volume-tester-b6kjs": Phase="Pending", Reason="", readiness=false. Elapsed: 2.057343591s May 15 07:04:52.548: INFO: Pod "azurefile-volume-tester-b6kjs": Phase="Pending", Reason="", readiness=false. Elapsed: 4.086568746s May 15 07:04:54.578: INFO: Pod "azurefile-volume-tester-b6kjs": Phase="Pending", Reason="", readiness=false. Elapsed: 6.116474636s May 15 07:04:56.609: INFO: Pod "azurefile-volume-tester-b6kjs": Phase="Pending", Reason="", readiness=false. Elapsed: 8.146798891s May 15 07:04:58.638: INFO: Pod "azurefile-volume-tester-b6kjs": Phase="Pending", Reason="", readiness=false. Elapsed: 10.176481391s May 15 07:05:00.668: INFO: Pod "azurefile-volume-tester-b6kjs": Phase="Pending", Reason="", readiness=false. Elapsed: 12.206457144s May 15 07:05:02.697: INFO: Pod "azurefile-volume-tester-b6kjs": Phase="Pending", Reason="", readiness=false. Elapsed: 14.235439281s May 15 07:05:04.727: INFO: Pod "azurefile-volume-tester-b6kjs": Phase="Pending", Reason="", readiness=false. Elapsed: 16.265167433s May 15 07:05:06.760: INFO: Pod "azurefile-volume-tester-b6kjs": Phase="Succeeded", Reason="", readiness=false. Elapsed: 18.298064375s [1mSTEP[0m: Saw pod success May 15 07:05:06.760: INFO: Pod "azurefile-volume-tester-b6kjs" satisfied condition "Succeeded or Failed" May 15 07:05:06.760: INFO: deleting Pod "azurefile-5194"/"azurefile-volume-tester-b6kjs" May 15 07:05:06.802: INFO: Pod azurefile-volume-tester-b6kjs has the following logs: hello world [1mSTEP[0m: Deleting pod azurefile-volume-tester-b6kjs in namespace azurefile-5194 May 15 07:05:06.838: INFO: deleting PVC "azurefile-5194"/"pvc-wmhqc" May 15 07:05:06.838: INFO: Deleting PersistentVolumeClaim "pvc-wmhqc" ... skipping 35 lines ... May 15 07:05:12.717: INFO: PersistentVolumeClaim pvc-dhhf4 found but phase is Pending instead of Bound. May 15 07:05:14.747: INFO: PersistentVolumeClaim pvc-dhhf4 found and phase=Bound (2.058249938s) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:05:14.834: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-2gknj" in namespace "azurefile-1353" to be "Succeeded or Failed" May 15 07:05:14.862: INFO: Pod "azurefile-volume-tester-2gknj": Phase="Pending", Reason="", readiness=false. Elapsed: 27.786984ms May 15 07:05:16.893: INFO: Pod "azurefile-volume-tester-2gknj": Phase="Running", Reason="", readiness=true. Elapsed: 2.058744455s May 15 07:05:18.924: INFO: Pod "azurefile-volume-tester-2gknj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.089791705s [1mSTEP[0m: Saw pod success May 15 07:05:18.924: INFO: Pod "azurefile-volume-tester-2gknj" satisfied condition "Succeeded or Failed" May 15 07:05:18.924: INFO: deleting Pod "azurefile-1353"/"azurefile-volume-tester-2gknj" May 15 07:05:18.955: INFO: Pod azurefile-volume-tester-2gknj has the following logs: hello world [1mSTEP[0m: Deleting pod azurefile-volume-tester-2gknj in namespace azurefile-1353 May 15 07:05:19.004: INFO: deleting PVC "azurefile-1353"/"pvc-dhhf4" May 15 07:05:19.004: INFO: Deleting PersistentVolumeClaim "pvc-dhhf4" ... skipping 128 lines ... May 15 07:07:07.204: INFO: PersistentVolumeClaim pvc-zhnf4 found but phase is Pending instead of Bound. May 15 07:07:09.232: INFO: PersistentVolumeClaim pvc-zhnf4 found and phase=Bound (20.32349573s) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with an error May 15 07:07:09.320: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-tg8rf" in namespace "azurefile-156" to be "Error status code" May 15 07:07:09.348: INFO: Pod "azurefile-volume-tester-tg8rf": Phase="Pending", Reason="", readiness=false. Elapsed: 27.92656ms May 15 07:07:11.378: INFO: Pod "azurefile-volume-tester-tg8rf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.057492793s May 15 07:07:13.408: INFO: Pod "azurefile-volume-tester-tg8rf": Phase="Failed", Reason="", readiness=false. Elapsed: 4.08815124s [1mSTEP[0m: Saw pod failure May 15 07:07:13.408: INFO: Pod "azurefile-volume-tester-tg8rf" satisfied condition "Error status code" [1mSTEP[0m: checking that pod logs contain expected message May 15 07:07:13.447: INFO: deleting Pod "azurefile-156"/"azurefile-volume-tester-tg8rf" May 15 07:07:13.479: INFO: Pod azurefile-volume-tester-tg8rf has the following logs: touch: /mnt/test-1/data: Read-only file system [1mSTEP[0m: Deleting pod azurefile-volume-tester-tg8rf in namespace azurefile-156 May 15 07:07:13.518: INFO: deleting PVC "azurefile-156"/"pvc-zhnf4" ... skipping 193 lines ... May 15 07:09:06.845: INFO: PersistentVolumeClaim pvc-w5g8z found but phase is Pending instead of Bound. May 15 07:09:08.875: INFO: PersistentVolumeClaim pvc-w5g8z found and phase=Bound (2.058895128s) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:09:08.961: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-h9n46" in namespace "azurefile-2546" to be "Succeeded or Failed" May 15 07:09:08.991: INFO: Pod "azurefile-volume-tester-h9n46": Phase="Pending", Reason="", readiness=false. Elapsed: 30.193013ms May 15 07:09:11.021: INFO: Pod "azurefile-volume-tester-h9n46": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.059966945s [1mSTEP[0m: Saw pod success May 15 07:09:11.021: INFO: Pod "azurefile-volume-tester-h9n46" satisfied condition "Succeeded or Failed" [1mSTEP[0m: resizing the pvc [1mSTEP[0m: sleep 30s waiting for resize complete [1mSTEP[0m: checking the resizing result [1mSTEP[0m: checking the resizing PV result [1mSTEP[0m: checking the resizing azurefile result May 15 07:09:41.573: INFO: deleting Pod "azurefile-2546"/"azurefile-volume-tester-h9n46" ... skipping 40 lines ... May 15 07:09:47.572: INFO: PersistentVolumeClaim pvc-m8lxn found but phase is Pending instead of Bound. May 15 07:09:49.600: INFO: PersistentVolumeClaim pvc-m8lxn found and phase=Bound (2.055805868s) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:09:49.686: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-vtv59" in namespace "azurefile-1598" to be "Succeeded or Failed" May 15 07:09:49.714: INFO: Pod "azurefile-volume-tester-vtv59": Phase="Pending", Reason="", readiness=false. Elapsed: 27.747026ms May 15 07:09:51.743: INFO: Pod "azurefile-volume-tester-vtv59": Phase="Pending", Reason="", readiness=false. Elapsed: 2.056716131s May 15 07:09:53.772: INFO: Pod "azurefile-volume-tester-vtv59": Phase="Pending", Reason="", readiness=false. Elapsed: 4.08587652s May 15 07:09:55.801: INFO: Pod "azurefile-volume-tester-vtv59": Phase="Pending", Reason="", readiness=false. Elapsed: 6.114978161s May 15 07:09:57.830: INFO: Pod "azurefile-volume-tester-vtv59": Phase="Pending", Reason="", readiness=false. Elapsed: 8.144042623s May 15 07:09:59.860: INFO: Pod "azurefile-volume-tester-vtv59": Phase="Pending", Reason="", readiness=false. Elapsed: 10.174170787s May 15 07:10:01.891: INFO: Pod "azurefile-volume-tester-vtv59": Phase="Pending", Reason="", readiness=false. Elapsed: 12.20446579s May 15 07:10:03.922: INFO: Pod "azurefile-volume-tester-vtv59": Phase="Succeeded", Reason="", readiness=false. Elapsed: 14.235313131s [1mSTEP[0m: Saw pod success May 15 07:10:03.922: INFO: Pod "azurefile-volume-tester-vtv59" satisfied condition "Succeeded or Failed" May 15 07:10:03.922: INFO: deleting Pod "azurefile-1598"/"azurefile-volume-tester-vtv59" May 15 07:10:03.953: INFO: Pod azurefile-volume-tester-vtv59 has the following logs: hello world [1mSTEP[0m: Deleting pod azurefile-volume-tester-vtv59 in namespace azurefile-1598 May 15 07:10:03.988: INFO: deleting PVC "azurefile-1598"/"pvc-m8lxn" May 15 07:10:03.988: INFO: Deleting PersistentVolumeClaim "pvc-m8lxn" ... skipping 37 lines ... [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pod has 'FailedMount' event May 15 07:10:14.058: INFO: deleting Pod "azurefile-3410"/"azurefile-volume-tester-rb8sp" May 15 07:10:14.088: INFO: Error getting logs for pod azurefile-volume-tester-rb8sp: the server rejected our request for an unknown reason (get pods azurefile-volume-tester-rb8sp) [1mSTEP[0m: Deleting pod azurefile-volume-tester-rb8sp in namespace azurefile-3410 May 15 07:10:14.118: INFO: deleting PVC "azurefile-3410"/"pvc-6flbn" May 15 07:10:14.118: INFO: Deleting PersistentVolumeClaim "pvc-6flbn" [1mSTEP[0m: waiting for claim's PV "pvc-9def447a-5309-414f-802e-e02606d7006f" to be deleted May 15 07:10:14.212: INFO: Waiting up to 10m0s for PersistentVolume pvc-9def447a-5309-414f-802e-e02606d7006f to get deleted May 15 07:10:14.240: INFO: PersistentVolume pvc-9def447a-5309-414f-802e-e02606d7006f found and phase=Bound (28.227964ms) ... skipping 58 lines ... [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pod has 'FailedMount' event May 15 07:12:25.126: INFO: deleting Pod "azurefile-8582"/"azurefile-volume-tester-r8v4x" May 15 07:12:25.183: INFO: Error getting logs for pod azurefile-volume-tester-r8v4x: the server rejected our request for an unknown reason (get pods azurefile-volume-tester-r8v4x) [1mSTEP[0m: Deleting pod azurefile-volume-tester-r8v4x in namespace azurefile-8582 May 15 07:12:25.213: INFO: deleting PVC "azurefile-8582"/"pvc-4q8nk" May 15 07:12:25.213: INFO: Deleting PersistentVolumeClaim "pvc-4q8nk" [1mSTEP[0m: waiting for claim's PV "pvc-c9b85b5c-92e8-40fc-85cd-0539519f0f2b" to be deleted May 15 07:12:25.304: INFO: Waiting up to 10m0s for PersistentVolume pvc-c9b85b5c-92e8-40fc-85cd-0539519f0f2b to get deleted May 15 07:12:25.335: INFO: PersistentVolume pvc-c9b85b5c-92e8-40fc-85cd-0539519f0f2b found and phase=Bound (30.810616ms) ... skipping 140 lines ... May 15 07:15:55.872: INFO: PersistentVolumeClaim pvc-2fxb7 found but phase is Pending instead of Bound. May 15 07:15:57.901: INFO: PersistentVolumeClaim pvc-2fxb7 found and phase=Bound (2.057173818s) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with an error May 15 07:15:57.988: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-l7qc6" in namespace "azurefile-3086" to be "Error status code" May 15 07:15:58.017: INFO: Pod "azurefile-volume-tester-l7qc6": Phase="Pending", Reason="", readiness=false. Elapsed: 28.497266ms May 15 07:16:00.046: INFO: Pod "azurefile-volume-tester-l7qc6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.057982506s May 15 07:16:02.075: INFO: Pod "azurefile-volume-tester-l7qc6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.087299109s May 15 07:16:04.106: INFO: Pod "azurefile-volume-tester-l7qc6": Phase="Failed", Reason="", readiness=false. Elapsed: 6.117503307s [1mSTEP[0m: Saw pod failure May 15 07:16:04.106: INFO: Pod "azurefile-volume-tester-l7qc6" satisfied condition "Error status code" [1mSTEP[0m: checking that pod logs contain expected message May 15 07:16:04.137: INFO: deleting Pod "azurefile-3086"/"azurefile-volume-tester-l7qc6" May 15 07:16:04.167: INFO: Pod azurefile-volume-tester-l7qc6 has the following logs: touch: /mnt/test-1/data: Read-only file system [1mSTEP[0m: Deleting pod azurefile-volume-tester-l7qc6 in namespace azurefile-3086 May 15 07:16:04.206: INFO: deleting PVC "azurefile-3086"/"pvc-2fxb7" ... skipping 198 lines ... May 15 07:16:32.758: INFO: PersistentVolumeClaim pvc-z8tkz found but phase is Pending instead of Bound. May 15 07:16:34.788: INFO: PersistentVolumeClaim pvc-z8tkz found and phase=Bound (2.058240764s) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:16:34.875: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-rgb5h" in namespace "azurefile-9183" to be "Succeeded or Failed" May 15 07:16:34.903: INFO: Pod "azurefile-volume-tester-rgb5h": Phase="Pending", Reason="", readiness=false. Elapsed: 28.088525ms May 15 07:16:36.934: INFO: Pod "azurefile-volume-tester-rgb5h": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058724479s May 15 07:16:38.965: INFO: Pod "azurefile-volume-tester-rgb5h": Phase="Running", Reason="", readiness=true. Elapsed: 4.090140032s May 15 07:16:40.995: INFO: Pod "azurefile-volume-tester-rgb5h": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.120479501s [1mSTEP[0m: Saw pod success May 15 07:16:40.995: INFO: Pod "azurefile-volume-tester-rgb5h" satisfied condition "Succeeded or Failed" May 15 07:16:40.995: INFO: deleting Pod "azurefile-9183"/"azurefile-volume-tester-rgb5h" May 15 07:16:41.042: INFO: Pod azurefile-volume-tester-rgb5h has the following logs: hello world [1mSTEP[0m: Deleting pod azurefile-volume-tester-rgb5h in namespace azurefile-9183 May 15 07:16:41.082: INFO: deleting PVC "azurefile-9183"/"pvc-z8tkz" May 15 07:16:41.082: INFO: Deleting PersistentVolumeClaim "pvc-z8tkz" ... skipping 80 lines ... May 15 07:17:12.990: INFO: PersistentVolumeClaim pvc-2h9xn found but phase is Pending instead of Bound. May 15 07:17:15.019: INFO: PersistentVolumeClaim pvc-2h9xn found and phase=Bound (2.056840445s) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pod's command exits with no error May 15 07:17:15.108: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-752wm" in namespace "azurefile-7578" to be "Succeeded or Failed" May 15 07:17:15.138: INFO: Pod "azurefile-volume-tester-752wm": Phase="Pending", Reason="", readiness=false. Elapsed: 29.965032ms May 15 07:17:17.168: INFO: Pod "azurefile-volume-tester-752wm": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.060267964s [1mSTEP[0m: Saw pod success May 15 07:17:17.168: INFO: Pod "azurefile-volume-tester-752wm" satisfied condition "Succeeded or Failed" [1mSTEP[0m: creating volume snapshot class [1mSTEP[0m: setting up the VolumeSnapshotClass [1mSTEP[0m: creating a VolumeSnapshotClass [1mSTEP[0m: taking snapshots [1mSTEP[0m: creating a VolumeSnapshot for pvc-2h9xn [1mSTEP[0m: waiting for VolumeSnapshot to be ready to use - volume-snapshot-nhkqv ... skipping 33 lines ... check the driver pods if restarts ... ====================================================================================== 2022/05/15 07:17:38 Check successfully May 15 07:17:38.203: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig 2022/05/15 07:17:38 run script: test/utils/get_storage_account_secret_name.sh 2022/05/15 07:17:38 got output: azure-storage-account-f51f42e42739d4651816fbf-secret , error: <nil> 2022/05/15 07:17:38 got storage account secret name: azure-storage-account-f51f42e42739d4651816fbf-secret [1mSTEP[0m: setting up the StorageClass [1mSTEP[0m: creating a StorageClass [1mSTEP[0m: setting up the PVC and PV [1mSTEP[0m: creating a PVC [1mSTEP[0m: waiting for PVC to be in phase "Bound" May 15 07:17:38.477: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-746gj] to have phase Bound May 15 07:17:38.505: INFO: PersistentVolumeClaim pvc-746gj found but phase is Pending instead of Bound. May 15 07:17:40.535: INFO: PersistentVolumeClaim pvc-746gj found and phase=Bound (2.058179796s) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:17:40.622: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-hd6fw" in namespace "azurefile-1968" to be "Succeeded or Failed" May 15 07:17:40.652: INFO: Pod "azurefile-volume-tester-hd6fw": Phase="Pending", Reason="", readiness=false. Elapsed: 30.723585ms May 15 07:17:42.683: INFO: Pod "azurefile-volume-tester-hd6fw": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061869685s May 15 07:17:44.715: INFO: Pod "azurefile-volume-tester-hd6fw": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.093475078s [1mSTEP[0m: Saw pod success May 15 07:17:44.715: INFO: Pod "azurefile-volume-tester-hd6fw" satisfied condition "Succeeded or Failed" May 15 07:17:44.715: INFO: deleting Pod "azurefile-1968"/"azurefile-volume-tester-hd6fw" May 15 07:17:44.746: INFO: Pod azurefile-volume-tester-hd6fw has the following logs: hello world [1mSTEP[0m: Deleting pod azurefile-volume-tester-hd6fw in namespace azurefile-1968 May 15 07:17:44.782: INFO: deleting PVC "azurefile-1968"/"pvc-746gj" May 15 07:17:44.782: INFO: Deleting PersistentVolumeClaim "pvc-746gj" ... skipping 45 lines ... May 15 07:18:10.939: INFO: PersistentVolumeClaim pvc-s8lwc found but phase is Pending instead of Bound. May 15 07:18:12.969: INFO: PersistentVolumeClaim pvc-s8lwc found and phase=Bound (22.356758805s) [1mSTEP[0m: checking the PVC [1mSTEP[0m: validating provisioned PV [1mSTEP[0m: checking the PV [1mSTEP[0m: deploying the pod [1mSTEP[0m: checking that the pods command exits with no error May 15 07:18:13.057: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-d87p2" in namespace "azurefile-4657" to be "Succeeded or Failed" May 15 07:18:13.085: INFO: Pod "azurefile-volume-tester-d87p2": Phase="Pending", Reason="", readiness=false. Elapsed: 27.695097ms May 15 07:18:15.116: INFO: Pod "azurefile-volume-tester-d87p2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.058579988s [1mSTEP[0m: Saw pod success May 15 07:18:15.116: INFO: Pod "azurefile-volume-tester-d87p2" satisfied condition "Succeeded or Failed" May 15 07:18:15.116: INFO: deleting Pod "azurefile-4657"/"azurefile-volume-tester-d87p2" May 15 07:18:15.148: INFO: Pod azurefile-volume-tester-d87p2 has the following logs: hello world [1mSTEP[0m: Deleting pod azurefile-volume-tester-d87p2 in namespace azurefile-4657 May 15 07:18:15.184: INFO: deleting PVC "azurefile-4657"/"pvc-s8lwc" May 15 07:18:15.184: INFO: Deleting PersistentVolumeClaim "pvc-s8lwc" ... skipping 29 lines ... [1mSTEP[0m: setting up the StorageClass [1mSTEP[0m: creating a StorageClass [1mSTEP[0m: setting up the PVC [1mSTEP[0m: setting up the statefulset [1mSTEP[0m: deploying the statefulset I0515 07:18:21.071762 36277 testsuites.go:630] 0/1 replicas in the StatefulSet are ready {"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:169","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2022-05-15T07:18:21Z"} ++ early_exit_handler ++ '[' -n 161 ']' ++ kill -TERM 161 ++ cleanup_dind ++ [[ true == \t\r\u\e ]] ++ echo 'Cleaning up after docker' ... skipping 4 lines ...