kubernetes-sigs/azurefile-csi-driver PR #1011 pull-azurefile-csi-driver-e2e-capz #1522204101738237952
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | andyzhangx: feat: skip chmod if mountPermissions is 0 after mount |
| Result | ABORTED |
| Tests | 0 failed / 31 succeeded |
| Started | |
| Elapsed | 48m36s |
| Revision | 0700ee442fb4cd3f88b2a27248e8abe407eaf213 |
| Refs |
1011 |
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 674 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 131 lines ... # Wait for the kubeconfig to become available. timeout --foreground 300 bash -c "while ! kubectl get secrets | grep capz-jwtbbq-kubeconfig; do sleep 1; done" capz-jwtbbq-kubeconfig cluster.x-k8s.io/secret 1 1s # Get kubeconfig and store it locally. kubectl get secrets capz-jwtbbq-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-jwtbbq-control-plane-5nmhv NotReady control-plane,master 7s 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-jwtbbq-control-plane-5nmhv condition met node/capz-jwtbbq-md-0-7n686 condition met ... skipping 35 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11156 100 11156 0 0 194k 0 --:--:-- --:--:-- --:--:-- 194k 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-b6080c9440f141f2d6451e2c2565a83f95482f0d || make container-all push-manifest Error response from daemon: manifest for capzci.azurecr.io/azurefile-csi:e2e-b6080c9440f141f2d6451e2c2565a83f95482f0d not found: manifest unknown: manifest tagged by "e2e-b6080c9440f141f2d6451e2c2565a83f95482f0d" 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-b6080c9440f141f2d6451e2c2565a83f95482f0d -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.gitCommit=b6080c9440f141f2d6451e2c2565a83f95482f0d -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.buildDate=2022-05-05T13:32:12Z -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 1808 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 W0505 13:44:25.840709 36544 azure.go:78] InitializeCloudFromSecret: failed to get cloud config from secret /: failed to get secret /: resource name may not be empty I0505 13:44:25.845404 36544 driver.go:93] Enabling controller service capability: CREATE_DELETE_VOLUME I0505 13:44:25.845444 36544 driver.go:93] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME I0505 13:44:25.845451 36544 driver.go:93] Enabling controller service capability: CREATE_DELETE_SNAPSHOT I0505 13:44:25.845462 36544 driver.go:93] Enabling controller service capability: EXPAND_VOLUME I0505 13:44:25.845466 36544 driver.go:93] Enabling controller service capability: SINGLE_NODE_MULTI_WRITER I0505 13:44:25.845471 36544 driver.go:112] Enabling volume access mode: SINGLE_NODE_WRITER ... skipping 123 lines ... May 5 13:46:35.522: INFO: PersistentVolumeClaim pvc-bw5tw found but phase is Pending instead of Bound. May 5 13:46:37.559: INFO: PersistentVolumeClaim pvc-bw5tw found and phase=Bound (1m37.814342072s) [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 5 13:46:37.666: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-swckd" in namespace "azurefile-2540" to be "Succeeded or Failed" May 5 13:46:37.700: INFO: Pod "azurefile-volume-tester-swckd": Phase="Pending", Reason="", readiness=false. Elapsed: 34.278215ms May 5 13:46:39.739: INFO: Pod "azurefile-volume-tester-swckd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.073192408s May 5 13:46:41.777: INFO: Pod "azurefile-volume-tester-swckd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.110993764s [1mSTEP[0m: Saw pod success May 5 13:46:41.777: INFO: Pod "azurefile-volume-tester-swckd" satisfied condition "Succeeded or Failed" May 5 13:46:41.777: INFO: deleting Pod "azurefile-2540"/"azurefile-volume-tester-swckd" May 5 13:46:41.824: INFO: Pod azurefile-volume-tester-swckd has the following logs: hello world [1mSTEP[0m: Deleting pod azurefile-volume-tester-swckd in namespace azurefile-2540 May 5 13:46:41.938: INFO: deleting PVC "azurefile-2540"/"pvc-bw5tw" May 5 13:46:41.938: INFO: Deleting PersistentVolumeClaim "pvc-bw5tw" ... skipping 45 lines ... May 5 13:47:08.532: INFO: PersistentVolumeClaim pvc-m8qvh found but phase is Pending instead of Bound. May 5 13:47:10.569: INFO: PersistentVolumeClaim pvc-m8qvh found and phase=Bound (22.430502538s) [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 5 13:47:10.676: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-d8zd6" in namespace "azurefile-4728" to be "Succeeded or Failed" May 5 13:47:10.714: INFO: Pod "azurefile-volume-tester-d8zd6": Phase="Pending", Reason="", readiness=false. Elapsed: 37.481087ms May 5 13:47:12.753: INFO: Pod "azurefile-volume-tester-d8zd6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.076760449s May 5 13:47:14.790: INFO: Pod "azurefile-volume-tester-d8zd6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.113282764s [1mSTEP[0m: Saw pod success May 5 13:47:14.790: INFO: Pod "azurefile-volume-tester-d8zd6" satisfied condition "Succeeded or Failed" May 5 13:47:14.790: INFO: deleting Pod "azurefile-4728"/"azurefile-volume-tester-d8zd6" May 5 13:47:14.829: INFO: Pod azurefile-volume-tester-d8zd6 has the following logs: hello world [1mSTEP[0m: Deleting pod azurefile-volume-tester-d8zd6 in namespace azurefile-4728 May 5 13:47:14.870: INFO: deleting PVC "azurefile-4728"/"pvc-m8qvh" May 5 13:47:14.870: INFO: Deleting PersistentVolumeClaim "pvc-m8qvh" ... skipping 128 lines ... May 5 13:49:01.928: INFO: PersistentVolumeClaim pvc-tlqcl found but phase is Pending instead of Bound. May 5 13:49:03.963: INFO: PersistentVolumeClaim pvc-tlqcl found and phase=Bound (20.638094646s) [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 5 13:49:04.073: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-gkrg6" in namespace "azurefile-2790" to be "Error status code" May 5 13:49:04.115: INFO: Pod "azurefile-volume-tester-gkrg6": Phase="Pending", Reason="", readiness=false. Elapsed: 41.605039ms May 5 13:49:06.152: INFO: Pod "azurefile-volume-tester-gkrg6": Phase="Running", Reason="", readiness=true. Elapsed: 2.079104298s May 5 13:49:08.190: INFO: Pod "azurefile-volume-tester-gkrg6": Phase="Failed", Reason="", readiness=false. Elapsed: 4.117097405s [1mSTEP[0m: Saw pod failure May 5 13:49:08.190: INFO: Pod "azurefile-volume-tester-gkrg6" satisfied condition "Error status code" [1mSTEP[0m: checking that pod logs contain expected message May 5 13:49:08.230: INFO: deleting Pod "azurefile-2790"/"azurefile-volume-tester-gkrg6" May 5 13:49:08.267: INFO: Pod azurefile-volume-tester-gkrg6 has the following logs: touch: /mnt/test-1/data: Read-only file system [1mSTEP[0m: Deleting pod azurefile-volume-tester-gkrg6 in namespace azurefile-2790 May 5 13:49:08.310: INFO: deleting PVC "azurefile-2790"/"pvc-tlqcl" ... skipping 192 lines ... May 5 13:51:00.953: INFO: PersistentVolumeClaim pvc-k9vnd found but phase is Pending instead of Bound. May 5 13:51:02.992: INFO: PersistentVolumeClaim pvc-k9vnd found and phase=Bound (2.073750477s) [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 5 13:51:03.099: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-2f47r" in namespace "azurefile-4538" to be "Succeeded or Failed" May 5 13:51:03.134: INFO: Pod "azurefile-volume-tester-2f47r": Phase="Pending", Reason="", readiness=false. Elapsed: 34.51229ms May 5 13:51:05.172: INFO: Pod "azurefile-volume-tester-2f47r": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.073072364s [1mSTEP[0m: Saw pod success May 5 13:51:05.172: INFO: Pod "azurefile-volume-tester-2f47r" 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 5 13:51:35.559: INFO: deleting Pod "azurefile-4538"/"azurefile-volume-tester-2f47r" ... skipping 40 lines ... May 5 13:51:41.693: INFO: PersistentVolumeClaim pvc-9f74t found but phase is Pending instead of Bound. May 5 13:51:43.730: INFO: PersistentVolumeClaim pvc-9f74t found and phase=Bound (2.07095527s) [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 5 13:51:43.837: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-xt452" in namespace "azurefile-8266" to be "Succeeded or Failed" May 5 13:51:43.874: INFO: Pod "azurefile-volume-tester-xt452": Phase="Pending", Reason="", readiness=false. Elapsed: 37.179702ms May 5 13:51:45.910: INFO: Pod "azurefile-volume-tester-xt452": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07317186s May 5 13:51:47.947: INFO: Pod "azurefile-volume-tester-xt452": Phase="Pending", Reason="", readiness=false. Elapsed: 4.109710154s May 5 13:51:49.983: INFO: Pod "azurefile-volume-tester-xt452": Phase="Pending", Reason="", readiness=false. Elapsed: 6.145899904s May 5 13:51:52.020: INFO: Pod "azurefile-volume-tester-xt452": Phase="Pending", Reason="", readiness=false. Elapsed: 8.182834944s May 5 13:51:54.056: INFO: Pod "azurefile-volume-tester-xt452": Phase="Pending", Reason="", readiness=false. Elapsed: 10.219352121s May 5 13:51:56.094: INFO: Pod "azurefile-volume-tester-xt452": Phase="Succeeded", Reason="", readiness=false. Elapsed: 12.257573791s [1mSTEP[0m: Saw pod success May 5 13:51:56.094: INFO: Pod "azurefile-volume-tester-xt452" satisfied condition "Succeeded or Failed" May 5 13:51:56.095: INFO: deleting Pod "azurefile-8266"/"azurefile-volume-tester-xt452" May 5 13:51:56.135: INFO: Pod azurefile-volume-tester-xt452 has the following logs: hello world [1mSTEP[0m: Deleting pod azurefile-volume-tester-xt452 in namespace azurefile-8266 May 5 13:51:56.186: INFO: deleting PVC "azurefile-8266"/"pvc-9f74t" May 5 13:51:56.186: INFO: Deleting PersistentVolumeClaim "pvc-9f74t" ... 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 5 13:52:06.449: INFO: deleting Pod "azurefile-4376"/"azurefile-volume-tester-gncvc" May 5 13:52:06.487: INFO: Error getting logs for pod azurefile-volume-tester-gncvc: the server rejected our request for an unknown reason (get pods azurefile-volume-tester-gncvc) [1mSTEP[0m: Deleting pod azurefile-volume-tester-gncvc in namespace azurefile-4376 May 5 13:52:06.526: INFO: deleting PVC "azurefile-4376"/"pvc-4bqfb" May 5 13:52:06.527: INFO: Deleting PersistentVolumeClaim "pvc-4bqfb" [1mSTEP[0m: waiting for claim's PV "pvc-f509a0c8-a630-4601-91ea-c3621bb1f94c" to be deleted May 5 13:52:06.645: INFO: Waiting up to 10m0s for PersistentVolume pvc-f509a0c8-a630-4601-91ea-c3621bb1f94c to get deleted May 5 13:52:06.680: INFO: PersistentVolume pvc-f509a0c8-a630-4601-91ea-c3621bb1f94c found and phase=Bound (35.389894ms) ... 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 5 13:54:17.862: INFO: deleting Pod "azurefile-7996"/"azurefile-volume-tester-pxzvd" May 5 13:54:17.907: INFO: Error getting logs for pod azurefile-volume-tester-pxzvd: the server rejected our request for an unknown reason (get pods azurefile-volume-tester-pxzvd) [1mSTEP[0m: Deleting pod azurefile-volume-tester-pxzvd in namespace azurefile-7996 May 5 13:54:17.945: INFO: deleting PVC "azurefile-7996"/"pvc-qckkt" May 5 13:54:17.945: INFO: Deleting PersistentVolumeClaim "pvc-qckkt" [1mSTEP[0m: waiting for claim's PV "pvc-1321ac71-4687-41e9-9029-0435f1ab6e01" to be deleted May 5 13:54:18.057: INFO: Waiting up to 10m0s for PersistentVolume pvc-1321ac71-4687-41e9-9029-0435f1ab6e01 to get deleted May 5 13:54:18.092: INFO: PersistentVolume pvc-1321ac71-4687-41e9-9029-0435f1ab6e01 found and phase=Bound (34.6248ms) ... skipping 140 lines ... May 5 13:57:49.417: INFO: PersistentVolumeClaim pvc-gwbs8 found but phase is Pending instead of Bound. May 5 13:57:51.454: INFO: PersistentVolumeClaim pvc-gwbs8 found and phase=Bound (2.071226554s) [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 5 13:57:51.562: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-djnt5" in namespace "azurefile-2546" to be "Error status code" May 5 13:57:51.605: INFO: Pod "azurefile-volume-tester-djnt5": Phase="Pending", Reason="", readiness=false. Elapsed: 43.231542ms May 5 13:57:53.642: INFO: Pod "azurefile-volume-tester-djnt5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.079896303s May 5 13:57:55.679: INFO: Pod "azurefile-volume-tester-djnt5": Phase="Failed", Reason="", readiness=false. Elapsed: 4.116633923s [1mSTEP[0m: Saw pod failure May 5 13:57:55.679: INFO: Pod "azurefile-volume-tester-djnt5" satisfied condition "Error status code" [1mSTEP[0m: checking that pod logs contain expected message May 5 13:57:55.724: INFO: deleting Pod "azurefile-2546"/"azurefile-volume-tester-djnt5" May 5 13:57:55.760: INFO: Pod azurefile-volume-tester-djnt5 has the following logs: touch: /mnt/test-1/data: Read-only file system [1mSTEP[0m: Deleting pod azurefile-volume-tester-djnt5 in namespace azurefile-2546 May 5 13:57:55.807: INFO: deleting PVC "azurefile-2546"/"pvc-gwbs8" ... skipping 5 lines ...