kubernetes-sigs/azurefile-csi-driver PR #1118 pull-azurefile-csi-driver-e2e-capz-windows-2019 #1590599910099521536
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | umagnus: feat: support management api for volume snapshot |
| Result | ABORTED |
| Tests | 0 failed / 21 succeeded |
| Started | |
| Elapsed | 1h0m |
| Revision | 402cbb2873286852c190e4141d0bfa1c104e8b63 |
| Refs |
1118 |
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a Premium_LRS volume on demand with useDataPlaneAPI [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning should create a Standard_LRS volume on demand with disableDeleteRetentionPolicy [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 [kubernetes.io/azure-file] [file.csi.azure.com] [Windows]
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 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 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 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 [kubernetes.io/azure-file] [file.csi.azure.com] [Windows]
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 retain PV with reclaimPolicy "Retain" [file.csi.azure.com] [Windows]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning smb volume mount is still valid after driver restart [file.csi.azure.com]
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 [env] should retain PV with reclaimPolicy "Retain" [file.csi.azure.com] [disk]
AzureFile CSI Driver End-to-End Tests Dynamic Provisioning nfs volume mount is still valid after driver restart [file.csi.azure.com]
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 [file.csi.azure.com] [disk]
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, 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 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 an inline volume by in-tree driver [kubernetes.io/azure-file]
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 delete PV with reclaimPolicy "Delete" [file.csi.azure.com] [disk]
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]
... skipping 758 lines ... certificate.cert-manager.io "selfsigned-cert" deleted # Create secret for AzureClusterIdentity ./hack/create-identity-secret.sh make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make[2]: Nothing to be done for 'kubectl'. make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' Error from server (NotFound): secrets "cluster-identity-secret" not found secret/cluster-identity-secret created secret/cluster-identity-secret labeled # Create customized cloud provider configs ./hack/create-custom-cloud-provider-config.sh make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make[2]: Nothing to be done for 'kubectl'. ... skipping 141 lines ... # Wait for the kubeconfig to become available. timeout --foreground 300 bash -c "while ! /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 get secrets | grep capz-ya99s9-kubeconfig; do sleep 1; done" capz-ya99s9-kubeconfig cluster.x-k8s.io/secret 1 1s # Get kubeconfig and store it locally. /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 get secrets capz-ya99s9-kubeconfig -o json | jq -r .data.value | base64 --decode > ./kubeconfig timeout --foreground 600 bash -c "while ! /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 --kubeconfig=./kubeconfig get nodes | grep control-plane; do sleep 1; done" error: the server doesn't have a resource type "nodes" capz-ya99s9-control-plane-sbh4x NotReady control-plane,master 8s v1.23.14-rc.0.31+845565ba773c10 run "/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 --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), 0 worker machine(s), and 2 windows machine(s) to become Ready node/capz-ya99-89tp5 condition met node/capz-ya99-n5ghw condition met ... skipping 35 lines ... 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 11156 100 11156 0 0 143k 0 --:--:-- --:--:-- --:--:-- 143k Downloading https://get.helm.sh/helm-v3.10.1-linux-amd64.tar.gz Verifying checksum... Done. Preparing to install helm into /usr/local/bin helm installed into /usr/local/bin/helm docker pull capzci.azurecr.io/azurefile-csi:e2e-c0bfcdcfa7db478dde30992e1923280dd4cdb7b8 || make container-all push-manifest Error response from daemon: manifest for capzci.azurecr.io/azurefile-csi:e2e-c0bfcdcfa7db478dde30992e1923280dd4cdb7b8 not found: manifest unknown: manifest tagged by "e2e-c0bfcdcfa7db478dde30992e1923280dd4cdb7b8" 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-c0bfcdcfa7db478dde30992e1923280dd4cdb7b8 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.gitCommit=c0bfcdcfa7db478dde30992e1923280dd4cdb7b8 -X sigs.k8s.io/azurefile-csi-driver/pkg/azurefile.buildDate=2022-11-10T07:22:50Z -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 2526 lines ... image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.5.0" args: - "-csi-address=$(ADDRESS)" - "-v=2" - "-leader-election" - "--leader-election-namespace=kube-system" - '-handle-volume-inuse-error=false' - '-timeout=120s' - '-feature-gates=RecoverVolumeExpansionFailure=true' env: - name: ADDRESS value: /csi/csi.sock imagePullPolicy: IfNotPresent ... skipping 281 lines ... Nov 10 07:39:34.753: INFO: PersistentVolumeClaim pvc-b2q5b found but phase is Pending instead of Bound. Nov 10 07:39:36.819: INFO: PersistentVolumeClaim pvc-b2q5b found and phase=Bound (1m39.287360072s) [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 Nov 10 07:39:37.023: INFO: Waiting up to 15m0s for pod "azurefile-volume-tester-n7lns" in namespace "azurefile-2540" to be "Succeeded or Failed" Nov 10 07:39:37.089: INFO: Pod "azurefile-volume-tester-n7lns": Phase="Pending", Reason="", readiness=false. Elapsed: 65.179871ms Nov 10 07:39:39.155: INFO: Pod "azurefile-volume-tester-n7lns": Phase="Pending", Reason="", readiness=false. Elapsed: 2.131737757s Nov 10 07:39:41.221: INFO: Pod "azurefile-volume-tester-n7lns": Phase="Pending", Reason="", readiness=false. Elapsed: 4.19738757s Nov 10 07:39:43.287: INFO: Pod "azurefile-volume-tester-n7lns": Phase="Pending", Reason="", readiness=false. Elapsed: 6.263421914s Nov 10 07:39:45.359: INFO: Pod "azurefile-volume-tester-n7lns": Phase="Pending", Reason="", readiness=false. Elapsed: 8.335529577s Nov 10 07:39:47.432: INFO: Pod "azurefile-volume-tester-n7lns": Phase="Pending", Reason="", readiness=false. Elapsed: 10.4080509s ... skipping 153 lines ...