This job view page is being replaced by Spyglass soon. Check out the new job view.
PRKarthik-K-N: Fix TestJitterWithNegativeMaxFactor flaky test
ResultFAILURE
Tests 1 failed / 12 succeeded
Started2022-11-23 07:21
Elapsed58m35s
Revision6f568c4ef2f3110dd5f12ef5582463e1b48ddc0d
Refs 114078

Test Failures


AzureDisk CSI Driver End-to-End Tests AfterSuite 1.31s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=AzureDisk\sCSI\sDriver\sEnd\-to\-End\sTests\sAfterSuite$'
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:165
Unexpected error:
    <*exec.ExitError | 0xc000cbf780>: {
        ProcessState: {
            pid: 111294,
            status: 31488,
            rusage: {
                Utime: {Sec: 0, Usec: 429694},
                Stime: {Sec: 0, Usec: 213015},
                Maxrss: 52556,
                Ixrss: 0,
                Idrss: 0,
                Isrss: 0,
                Minflt: 25622,
                Majflt: 3,
                Nswap: 0,
                Inblock: 400,
                Oublock: 0,
                Msgsnd: 0,
                Msgrcv: 0,
                Nsignals: 0,
                Nvcsw: 3017,
                Nivcsw: 494,
            },
        },
        Stderr: nil,
    }
    exit status 123
occurred
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:291
				from junit_01.xml

Filter through log files | View test history on testgrid


Show 12 Passed Tests

Show 50 Skipped Tests

Error lines from build-log.txt

... skipping 126 lines ...
/home/prow/go/src/k8s.io/kubernetes /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   138  100   138    0     0   6000      0 --:--:-- --:--:-- --:--:--  6000

100    33  100    33    0     0    340      0 --:--:-- --:--:-- --:--:--   340
Error response from daemon: manifest for capzci.azurecr.io/kube-apiserver:v1.27.0-alpha.0.38_ab1d93cff12290 not found: manifest unknown: manifest tagged by "v1.27.0-alpha.0.38_ab1d93cff12290" is not found
Building Kubernetes
make: Entering directory '/home/prow/go/src/k8s.io/kubernetes'
+++ [1123 07:22:47] Verifying Prerequisites....
+++ [1123 07:22:47] Building Docker image kube-build:build-f679f59299-5-v1.25.0-go1.19.3-bullseye.0
+++ [1123 07:25:41] Creating data container kube-build-data-f679f59299-5-v1.25.0-go1.19.3-bullseye.0
+++ [1123 07:25:59] Syncing sources to container
... skipping 769 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 130 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-8cmo64-kubeconfig; do sleep 1; done"
capz-8cmo64-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-8cmo64-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-8cmo64-control-plane-dqmxl   NotReady   control-plane   9s    v1.27.0-alpha.0.38+ab1d93cff12290
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), 2 worker machine(s), and  windows machine(s) to become Ready
node/capz-8cmo64-control-plane-dqmxl condition met
node/capz-8cmo64-mp-0000000 condition met
... skipping 62 lines ...
Pre-Provisioned [single-az] 
  should use a pre-provisioned volume and mount it as readOnly in a pod [disk.csi.azure.com][windows]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:70
STEP: Creating a kubernetes client
Nov 23 07:54:13.003: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
STEP: Building a namespace api object, basename azuredisk
Nov 23 07:54:13.244: INFO: Error listing PodSecurityPolicies; assuming PodSecurityPolicy is disabled: the server could not find the requested resource
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
I1123 07:54:13.354436  110552 azuredisk_driver.go:56] Using azure disk driver: kubernetes.io/azure-disk
Nov 23 07:54:13.354: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "azuredisk-8081" for this suite.

... skipping 55 lines ...

    test case is only available for CSI drivers

    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:304
------------------------------
Pre-Provisioned [single-az] 
  should fail when maxShares is invalid [disk.csi.azure.com][windows]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:164
STEP: Creating a kubernetes client
Nov 23 07:54:13.993: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
STEP: Building a namespace api object, basename azuredisk
STEP: Waiting for a default service account to be provisioned in namespace
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace
... skipping 3 lines ...

S [SKIPPING] [0.270 seconds]
Pre-Provisioned
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:37
  [single-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:69
    should fail when maxShares is invalid [disk.csi.azure.com][windows] [It]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:164

    test case is only available for CSI drivers

    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:304
------------------------------
... skipping 109 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Nov 23 07:54:15.915: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-2md9k" in namespace "azuredisk-2888" to be "Succeeded or Failed"
Nov 23 07:54:15.945: INFO: Pod "azuredisk-volume-tester-2md9k": Phase="Pending", Reason="", readiness=false. Elapsed: 29.125339ms
Nov 23 07:54:17.974: INFO: Pod "azuredisk-volume-tester-2md9k": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058662364s
Nov 23 07:54:20.004: INFO: Pod "azuredisk-volume-tester-2md9k": Phase="Pending", Reason="", readiness=false. Elapsed: 4.088416416s
Nov 23 07:54:22.034: INFO: Pod "azuredisk-volume-tester-2md9k": Phase="Pending", Reason="", readiness=false. Elapsed: 6.118191632s
Nov 23 07:54:24.063: INFO: Pod "azuredisk-volume-tester-2md9k": Phase="Pending", Reason="", readiness=false. Elapsed: 8.147242584s
Nov 23 07:54:26.092: INFO: Pod "azuredisk-volume-tester-2md9k": Phase="Pending", Reason="", readiness=false. Elapsed: 10.176768376s
... skipping 2 lines ...
Nov 23 07:54:32.179: INFO: Pod "azuredisk-volume-tester-2md9k": Phase="Pending", Reason="", readiness=false. Elapsed: 16.263578553s
Nov 23 07:54:34.208: INFO: Pod "azuredisk-volume-tester-2md9k": Phase="Pending", Reason="", readiness=false. Elapsed: 18.292680173s
Nov 23 07:54:36.239: INFO: Pod "azuredisk-volume-tester-2md9k": Phase="Pending", Reason="", readiness=false. Elapsed: 20.323419491s
Nov 23 07:54:38.269: INFO: Pod "azuredisk-volume-tester-2md9k": Phase="Running", Reason="", readiness=false. Elapsed: 22.353205437s
Nov 23 07:54:40.299: INFO: Pod "azuredisk-volume-tester-2md9k": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.383116029s
STEP: Saw pod success
Nov 23 07:54:40.299: INFO: Pod "azuredisk-volume-tester-2md9k" satisfied condition "Succeeded or Failed"
Nov 23 07:54:40.299: INFO: deleting Pod "azuredisk-2888"/"azuredisk-volume-tester-2md9k"
Nov 23 07:54:40.341: INFO: Pod azuredisk-volume-tester-2md9k has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-2md9k in namespace azuredisk-2888
STEP: validating provisioned PV
STEP: checking the PV
... skipping 98 lines ...
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod has 'FailedMount' event
Nov 23 07:55:40.481: INFO: deleting Pod "azuredisk-7463"/"azuredisk-volume-tester-72pmp"
Nov 23 07:55:40.522: INFO: Error getting logs for pod azuredisk-volume-tester-72pmp: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-72pmp)
STEP: Deleting pod azuredisk-volume-tester-72pmp in namespace azuredisk-7463
STEP: validating provisioned PV
STEP: checking the PV
Nov 23 07:55:40.616: INFO: deleting PVC "azuredisk-7463"/"pvc-bqt25"
Nov 23 07:55:40.616: INFO: Deleting PersistentVolumeClaim "pvc-bqt25"
STEP: waiting for claim's PV "pvc-6fc3f74a-4fd7-4927-8798-a8284faf9a6d" to be deleted
... skipping 58 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Nov 23 07:58:07.235: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-gtrx6" in namespace "azuredisk-9241" to be "Succeeded or Failed"
Nov 23 07:58:07.264: INFO: Pod "azuredisk-volume-tester-gtrx6": Phase="Pending", Reason="", readiness=false. Elapsed: 28.669992ms
Nov 23 07:58:09.295: INFO: Pod "azuredisk-volume-tester-gtrx6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059532721s
Nov 23 07:58:11.324: INFO: Pod "azuredisk-volume-tester-gtrx6": Phase="Pending", Reason="", readiness=false. Elapsed: 4.088852475s
Nov 23 07:58:13.354: INFO: Pod "azuredisk-volume-tester-gtrx6": Phase="Pending", Reason="", readiness=false. Elapsed: 6.11815859s
Nov 23 07:58:15.382: INFO: Pod "azuredisk-volume-tester-gtrx6": Phase="Pending", Reason="", readiness=false. Elapsed: 8.146919181s
Nov 23 07:58:17.411: INFO: Pod "azuredisk-volume-tester-gtrx6": Phase="Pending", Reason="", readiness=false. Elapsed: 10.175610944s
Nov 23 07:58:19.439: INFO: Pod "azuredisk-volume-tester-gtrx6": Phase="Pending", Reason="", readiness=false. Elapsed: 12.204007349s
Nov 23 07:58:21.468: INFO: Pod "azuredisk-volume-tester-gtrx6": Phase="Pending", Reason="", readiness=false. Elapsed: 14.232452428s
Nov 23 07:58:23.497: INFO: Pod "azuredisk-volume-tester-gtrx6": Phase="Pending", Reason="", readiness=false. Elapsed: 16.261124207s
Nov 23 07:58:25.526: INFO: Pod "azuredisk-volume-tester-gtrx6": Phase="Pending", Reason="", readiness=false. Elapsed: 18.290916897s
Nov 23 07:58:27.556: INFO: Pod "azuredisk-volume-tester-gtrx6": Phase="Running", Reason="", readiness=false. Elapsed: 20.320875308s
Nov 23 07:58:29.587: INFO: Pod "azuredisk-volume-tester-gtrx6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.35142681s
STEP: Saw pod success
Nov 23 07:58:29.587: INFO: Pod "azuredisk-volume-tester-gtrx6" satisfied condition "Succeeded or Failed"
Nov 23 07:58:29.587: INFO: deleting Pod "azuredisk-9241"/"azuredisk-volume-tester-gtrx6"
Nov 23 07:58:29.624: INFO: Pod azuredisk-volume-tester-gtrx6 has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-gtrx6 in namespace azuredisk-9241
STEP: validating provisioned PV
STEP: checking the PV
... skipping 40 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with an error
Nov 23 07:59:10.689: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-dsc8s" in namespace "azuredisk-9336" to be "Error status code"
Nov 23 07:59:10.717: INFO: Pod "azuredisk-volume-tester-dsc8s": Phase="Pending", Reason="", readiness=false. Elapsed: 28.001452ms
Nov 23 07:59:12.747: INFO: Pod "azuredisk-volume-tester-dsc8s": Phase="Pending", Reason="", readiness=false. Elapsed: 2.057361126s
Nov 23 07:59:14.776: INFO: Pod "azuredisk-volume-tester-dsc8s": Phase="Pending", Reason="", readiness=false. Elapsed: 4.086745414s
Nov 23 07:59:16.805: INFO: Pod "azuredisk-volume-tester-dsc8s": Phase="Pending", Reason="", readiness=false. Elapsed: 6.115484623s
Nov 23 07:59:18.834: INFO: Pod "azuredisk-volume-tester-dsc8s": Phase="Pending", Reason="", readiness=false. Elapsed: 8.144350196s
Nov 23 07:59:20.863: INFO: Pod "azuredisk-volume-tester-dsc8s": Phase="Pending", Reason="", readiness=false. Elapsed: 10.174250264s
Nov 23 07:59:22.893: INFO: Pod "azuredisk-volume-tester-dsc8s": Phase="Pending", Reason="", readiness=false. Elapsed: 12.203619692s
Nov 23 07:59:24.922: INFO: Pod "azuredisk-volume-tester-dsc8s": Phase="Pending", Reason="", readiness=false. Elapsed: 14.233142498s
Nov 23 07:59:26.952: INFO: Pod "azuredisk-volume-tester-dsc8s": Phase="Pending", Reason="", readiness=false. Elapsed: 16.262311787s
Nov 23 07:59:28.980: INFO: Pod "azuredisk-volume-tester-dsc8s": Phase="Pending", Reason="", readiness=false. Elapsed: 18.290888377s
Nov 23 07:59:31.011: INFO: Pod "azuredisk-volume-tester-dsc8s": Phase="Pending", Reason="", readiness=false. Elapsed: 20.321253587s
Nov 23 07:59:33.041: INFO: Pod "azuredisk-volume-tester-dsc8s": Phase="Pending", Reason="", readiness=false. Elapsed: 22.351270946s
Nov 23 07:59:35.070: INFO: Pod "azuredisk-volume-tester-dsc8s": Phase="Failed", Reason="", readiness=false. Elapsed: 24.380956209s
STEP: Saw pod failure
Nov 23 07:59:35.070: INFO: Pod "azuredisk-volume-tester-dsc8s" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Nov 23 07:59:35.108: INFO: deleting Pod "azuredisk-9336"/"azuredisk-volume-tester-dsc8s"
Nov 23 07:59:35.138: INFO: Pod azuredisk-volume-tester-dsc8s has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-dsc8s in namespace azuredisk-9336
STEP: validating provisioned PV
... skipping 389 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Nov 23 08:08:02.983: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-wpzw2" in namespace "azuredisk-4547" to be "Succeeded or Failed"
Nov 23 08:08:03.017: INFO: Pod "azuredisk-volume-tester-wpzw2": Phase="Pending", Reason="", readiness=false. Elapsed: 33.773633ms
Nov 23 08:08:05.047: INFO: Pod "azuredisk-volume-tester-wpzw2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.063136478s
Nov 23 08:08:07.077: INFO: Pod "azuredisk-volume-tester-wpzw2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093678896s
Nov 23 08:08:09.108: INFO: Pod "azuredisk-volume-tester-wpzw2": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124587555s
Nov 23 08:08:11.139: INFO: Pod "azuredisk-volume-tester-wpzw2": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155628213s
Nov 23 08:08:13.170: INFO: Pod "azuredisk-volume-tester-wpzw2": Phase="Pending", Reason="", readiness=false. Elapsed: 10.186646971s
... skipping 8 lines ...
Nov 23 08:08:31.448: INFO: Pod "azuredisk-volume-tester-wpzw2": Phase="Pending", Reason="", readiness=false. Elapsed: 28.465011298s
Nov 23 08:08:33.479: INFO: Pod "azuredisk-volume-tester-wpzw2": Phase="Pending", Reason="", readiness=false. Elapsed: 30.495837633s
Nov 23 08:08:35.510: INFO: Pod "azuredisk-volume-tester-wpzw2": Phase="Pending", Reason="", readiness=false. Elapsed: 32.526825128s
Nov 23 08:08:37.540: INFO: Pod "azuredisk-volume-tester-wpzw2": Phase="Pending", Reason="", readiness=false. Elapsed: 34.556665078s
Nov 23 08:08:39.570: INFO: Pod "azuredisk-volume-tester-wpzw2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 36.586257074s
STEP: Saw pod success
Nov 23 08:08:39.570: INFO: Pod "azuredisk-volume-tester-wpzw2" satisfied condition "Succeeded or Failed"
Nov 23 08:08:39.570: INFO: deleting Pod "azuredisk-4547"/"azuredisk-volume-tester-wpzw2"
Nov 23 08:08:39.611: INFO: Pod azuredisk-volume-tester-wpzw2 has the following logs: hello world
hello world
hello world

STEP: Deleting pod azuredisk-volume-tester-wpzw2 in namespace azuredisk-4547
... skipping 76 lines ...
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Nov 23 08:10:06.375: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-cmdc7" in namespace "azuredisk-7051" to be "Succeeded or Failed"
Nov 23 08:10:06.411: INFO: Pod "azuredisk-volume-tester-cmdc7": Phase="Pending", Reason="", readiness=false. Elapsed: 35.810989ms
Nov 23 08:10:08.441: INFO: Pod "azuredisk-volume-tester-cmdc7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065801123s
Nov 23 08:10:10.469: INFO: Pod "azuredisk-volume-tester-cmdc7": Phase="Pending", Reason="", readiness=false. Elapsed: 4.094474264s
Nov 23 08:10:12.499: INFO: Pod "azuredisk-volume-tester-cmdc7": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123806859s
Nov 23 08:10:14.528: INFO: Pod "azuredisk-volume-tester-cmdc7": Phase="Pending", Reason="", readiness=false. Elapsed: 8.153112547s
Nov 23 08:10:16.557: INFO: Pod "azuredisk-volume-tester-cmdc7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.18183635s
... skipping 10 lines ...
Nov 23 08:10:38.877: INFO: Pod "azuredisk-volume-tester-cmdc7": Phase="Pending", Reason="", readiness=false. Elapsed: 32.501816772s
Nov 23 08:10:40.905: INFO: Pod "azuredisk-volume-tester-cmdc7": Phase="Pending", Reason="", readiness=false. Elapsed: 34.530446811s
Nov 23 08:10:42.935: INFO: Pod "azuredisk-volume-tester-cmdc7": Phase="Pending", Reason="", readiness=false. Elapsed: 36.559933936s
Nov 23 08:10:44.966: INFO: Pod "azuredisk-volume-tester-cmdc7": Phase="Pending", Reason="", readiness=false. Elapsed: 38.591092871s
Nov 23 08:10:46.998: INFO: Pod "azuredisk-volume-tester-cmdc7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 40.623171817s
STEP: Saw pod success
Nov 23 08:10:46.998: INFO: Pod "azuredisk-volume-tester-cmdc7" satisfied condition "Succeeded or Failed"
Nov 23 08:10:46.998: INFO: deleting Pod "azuredisk-7051"/"azuredisk-volume-tester-cmdc7"
Nov 23 08:10:47.041: INFO: Pod azuredisk-volume-tester-cmdc7 has the following logs: 100+0 records in
100+0 records out
104857600 bytes (100.0MB) copied, 0.057667 seconds, 1.7GB/s
hello world

... skipping 118 lines ...
STEP: creating a PVC
STEP: setting up the StorageClass
STEP: creating a StorageClass 
STEP: setting up the PVC and PV
STEP: creating a PVC
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Nov 23 08:11:39.467: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-7w9sb" in namespace "azuredisk-1968" to be "Succeeded or Failed"
Nov 23 08:11:39.500: INFO: Pod "azuredisk-volume-tester-7w9sb": Phase="Pending", Reason="", readiness=false. Elapsed: 33.023288ms
Nov 23 08:11:41.529: INFO: Pod "azuredisk-volume-tester-7w9sb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.062331278s
Nov 23 08:11:43.561: INFO: Pod "azuredisk-volume-tester-7w9sb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.093615471s
Nov 23 08:11:45.591: INFO: Pod "azuredisk-volume-tester-7w9sb": Phase="Pending", Reason="", readiness=false. Elapsed: 6.124409425s
Nov 23 08:11:47.622: INFO: Pod "azuredisk-volume-tester-7w9sb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.155265779s
Nov 23 08:11:49.653: INFO: Pod "azuredisk-volume-tester-7w9sb": Phase="Pending", Reason="", readiness=false. Elapsed: 10.186014987s
... skipping 5 lines ...
Nov 23 08:12:01.835: INFO: Pod "azuredisk-volume-tester-7w9sb": Phase="Pending", Reason="", readiness=false. Elapsed: 22.368567472s
Nov 23 08:12:03.865: INFO: Pod "azuredisk-volume-tester-7w9sb": Phase="Pending", Reason="", readiness=false. Elapsed: 24.398555409s
Nov 23 08:12:05.896: INFO: Pod "azuredisk-volume-tester-7w9sb": Phase="Pending", Reason="", readiness=false. Elapsed: 26.428722692s
Nov 23 08:12:07.926: INFO: Pod "azuredisk-volume-tester-7w9sb": Phase="Running", Reason="", readiness=false. Elapsed: 28.459084385s
Nov 23 08:12:09.956: INFO: Pod "azuredisk-volume-tester-7w9sb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 30.489051958s
STEP: Saw pod success
Nov 23 08:12:09.956: INFO: Pod "azuredisk-volume-tester-7w9sb" satisfied condition "Succeeded or Failed"
Nov 23 08:12:09.956: INFO: deleting Pod "azuredisk-1968"/"azuredisk-volume-tester-7w9sb"
Nov 23 08:12:09.989: INFO: Pod azuredisk-volume-tester-7w9sb has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-7w9sb in namespace azuredisk-1968
STEP: validating provisioned PV
STEP: checking the PV
... skipping 387 lines ...
======================================================================================
print out controller-manager logs ...
======================================================================================
kube-controller-manager-capz-8cmo64-control-plane-dqmxl   1/1     Running   0          26m
kube-controller-manager-capz-8cmo64-control-plane-dqmxl
dumping logs for kube-system/kube-controller-manager-capz-8cmo64-control-plane-dqmxl
Error from server (BadRequest): container "kube-controller-manager" in pod "kube-controller-manager-capz-8cmo64-control-plane-dqmxl" is not available

------------------------------
Failure [1.310 seconds]
[AfterSuite] AfterSuite 
/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:165

  Unexpected error:
      <*exec.ExitError | 0xc000cbf780>: {
          ProcessState: {
              pid: 111294,
              status: 31488,
              rusage: {
                  Utime: {Sec: 0, Usec: 429694},
... skipping 22 lines ...
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:291
------------------------------

JUnit report was created: /logs/artifacts/junit_01.xml

Ran 12 of 62 Specs in 1317.409 seconds
FAIL! -- 12 Passed | 0 Failed | 0 Pending | 50 Skipped

You're using deprecated Ginkgo functionality:
=============================================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
... skipping 5 lines ...
  If this change will be impactful to you please leave a comment on https://github.com/onsi/ginkgo/issues/711
  Learn more at: https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#removed-custom-reporters

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=1.16.5

--- FAIL: TestE2E (1317.43s)
FAIL
FAIL	sigs.k8s.io/azuredisk-csi-driver/test/e2e	1317.482s
FAIL
make: *** [Makefile:261: e2e-test] Error 1
NAME                              STATUS   ROLES           AGE   VERSION                             INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION     CONTAINER-RUNTIME
capz-8cmo64-control-plane-dqmxl   Ready    control-plane   26m   v1.27.0-alpha.0.38+ab1d93cff12290   10.0.0.4      <none>        Ubuntu 18.04.6 LTS   5.4.0-1091-azure   containerd://1.6.2
capz-8cmo64-mp-0000000            Ready    <none>          23m   v1.27.0-alpha.0.38+ab1d93cff12290   10.1.0.4      <none>        Ubuntu 18.04.6 LTS   5.4.0-1091-azure   containerd://1.6.2
capz-8cmo64-mp-0000001            Ready    <none>          24m   v1.27.0-alpha.0.38+ab1d93cff12290   10.1.0.5      <none>        Ubuntu 18.04.6 LTS   5.4.0-1091-azure   containerd://1.6.2
NAMESPACE        NAME                                                      READY   STATUS        RESTARTS   AGE   IP                NODE                              NOMINATED NODE   READINESS GATES
azuredisk-6611   azuredisk-volume-tester-ln5pm-0                           1/1     Terminating   0          34s   192.168.102.202   capz-8cmo64-mp-0000001            <none>           <none>
... skipping 91 lines ...
STEP: Creating log watcher for controller kube-system/csi-azuredisk-controller-7bb7795989-rt7qt, container liveness-probe
STEP: Creating log watcher for controller kube-system/csi-azuredisk-controller-7bb7795989-rt7qt, container azuredisk
STEP: Creating log watcher for controller kube-system/csi-azuredisk-controller-7bb7795989-sgm7h, container csi-attacher
STEP: Creating log watcher for controller kube-system/csi-azuredisk-controller-7bb7795989-sgm7h, container csi-snapshotter
STEP: Creating log watcher for controller kube-system/csi-azuredisk-controller-7bb7795989-sgm7h, container csi-resizer
STEP: Collecting events for Pod kube-system/csi-azuredisk-controller-7bb7795989-rt7qt
STEP: Error starting logs stream for pod kube-system/kube-scheduler-capz-8cmo64-control-plane-dqmxl, container kube-scheduler: container "kube-scheduler" in pod "kube-scheduler-capz-8cmo64-control-plane-dqmxl" is not available
STEP: Error starting logs stream for pod kube-system/kube-apiserver-capz-8cmo64-control-plane-dqmxl, container kube-apiserver: container "kube-apiserver" in pod "kube-apiserver-capz-8cmo64-control-plane-dqmxl" is not available
STEP: Error starting logs stream for pod kube-system/kube-controller-manager-capz-8cmo64-control-plane-dqmxl, container kube-controller-manager: container "kube-controller-manager" in pod "kube-controller-manager-capz-8cmo64-control-plane-dqmxl" is not available
STEP: Fetching activity logs took 8.295725181s
================ REDACTING LOGS ================
All sensitive variables are redacted
make: Entering directory '/home/prow/go/src/k8s.io/kubernetes'
+++ [1123 08:20:04] Verifying Prerequisites....
+++ [1123 08:20:07] Removing _output directory
... skipping 12 lines ...