This job view page is being replaced by Spyglass soon. Check out the new job view.
PROctopusjust: pkg/volume/azuredd: Fix test order in attacher_test.go
ResultFAILURE
Tests 1 failed / 12 succeeded
Started2022-11-28 02:37
Elapsed1h6m
Revision89e893fc79fc5ec0ec3c7b9e81e11eeacf3fede6
Refs 114157

Test Failures


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

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 | 0xc00057e980>: {
        ProcessState: {
            pid: 112127,
            status: 31488,
            rusage: {
                Utime: {Sec: 0, Usec: 505458},
                Stime: {Sec: 0, Usec: 179329},
                Maxrss: 53232,
                Ixrss: 0,
                Idrss: 0,
                Isrss: 0,
                Minflt: 24901,
                Majflt: 2,
                Nswap: 0,
                Inblock: 776,
                Oublock: 0,
                Msgsnd: 0,
                Msgrcv: 0,
                Nsignals: 0,
                Nvcsw: 2804,
                Nivcsw: 195,
            },
        },
        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 130 lines ...
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   138  100   138    0     0   5520      0 --:--:-- --:--:-- --:--:--  5520

100    33  100    33    0     0    452      0 --:--:-- --:--:-- --:--:--   452
using CI_VERSION=v1.27.0-alpha.0.50+70617042976dc1
using KUBERNETES_VERSION=v1.27.0-alpha.0.50+70617042976dc1
using IMAGE_TAG=v1.27.0-alpha.0.52_c9a0e68a5a7905
Error response from daemon: manifest for capzci.azurecr.io/kube-apiserver:v1.27.0-alpha.0.52_c9a0e68a5a7905 not found: manifest unknown: manifest tagged by "v1.27.0-alpha.0.52_c9a0e68a5a7905" is not found
Building Kubernetes
make: Entering directory '/home/prow/go/src/k8s.io/kubernetes'
+++ [1128 02:38:18] Verifying Prerequisites....
+++ [1128 02:38:19] Building Docker image kube-build:build-2bafb24b25-5-v1.25.0-go1.19.3-bullseye.0
+++ [1128 02:40:54] Creating data container kube-build-data-2bafb24b25-5-v1.25.0-go1.19.3-bullseye.0
+++ [1128 02:41:16] Syncing sources to container
... skipping 768 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-tr3rkq-kubeconfig; do sleep 1; done"
capz-tr3rkq-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-tr3rkq-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-tr3rkq-control-plane-jcnfl   NotReady   control-plane   3s    v1.27.0-alpha.0.52+c9a0e68a5a7905
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-tr3rkq-control-plane-jcnfl condition met
node/capz-tr3rkq-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 28 03:13:07.712: INFO: >>> kubeConfig: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/kubeconfig
STEP: Building a namespace api object, basename azuredisk
Nov 28 03:13:07.948: 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
I1128 03:13:08.056258  111343 azuredisk_driver.go:56] Using azure disk driver: kubernetes.io/azure-disk
Nov 28 03:13:08.056: 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 28 03:13:08.668: 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.268 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 28 03:13:10.528: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-j45qv" in namespace "azuredisk-2888" to be "Succeeded or Failed"
Nov 28 03:13:10.557: INFO: Pod "azuredisk-volume-tester-j45qv": Phase="Pending", Reason="", readiness=false. Elapsed: 28.357793ms
Nov 28 03:13:12.585: INFO: Pod "azuredisk-volume-tester-j45qv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.056620577s
Nov 28 03:13:14.615: INFO: Pod "azuredisk-volume-tester-j45qv": Phase="Pending", Reason="", readiness=false. Elapsed: 4.086517423s
Nov 28 03:13:16.645: INFO: Pod "azuredisk-volume-tester-j45qv": Phase="Pending", Reason="", readiness=false. Elapsed: 6.116400989s
Nov 28 03:13:18.673: INFO: Pod "azuredisk-volume-tester-j45qv": Phase="Pending", Reason="", readiness=false. Elapsed: 8.144280887s
Nov 28 03:13:20.701: INFO: Pod "azuredisk-volume-tester-j45qv": Phase="Pending", Reason="", readiness=false. Elapsed: 10.172481783s
... skipping 2 lines ...
Nov 28 03:13:26.786: INFO: Pod "azuredisk-volume-tester-j45qv": Phase="Pending", Reason="", readiness=false. Elapsed: 16.258130599s
Nov 28 03:13:28.814: INFO: Pod "azuredisk-volume-tester-j45qv": Phase="Pending", Reason="", readiness=false. Elapsed: 18.285999364s
Nov 28 03:13:30.843: INFO: Pod "azuredisk-volume-tester-j45qv": Phase="Pending", Reason="", readiness=false. Elapsed: 20.315090718s
Nov 28 03:13:32.873: INFO: Pod "azuredisk-volume-tester-j45qv": Phase="Pending", Reason="", readiness=false. Elapsed: 22.344555732s
Nov 28 03:13:34.902: INFO: Pod "azuredisk-volume-tester-j45qv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.374038465s
STEP: Saw pod success
Nov 28 03:13:34.902: INFO: Pod "azuredisk-volume-tester-j45qv" satisfied condition "Succeeded or Failed"
Nov 28 03:13:34.902: INFO: deleting Pod "azuredisk-2888"/"azuredisk-volume-tester-j45qv"
Nov 28 03:13:34.947: INFO: Pod azuredisk-volume-tester-j45qv has the following logs: hello world

STEP: Deleting pod azuredisk-volume-tester-j45qv 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 28 03:14:35.062: INFO: deleting Pod "azuredisk-7463"/"azuredisk-volume-tester-5zfc9"
Nov 28 03:14:35.106: INFO: Error getting logs for pod azuredisk-volume-tester-5zfc9: the server rejected our request for an unknown reason (get pods azuredisk-volume-tester-5zfc9)
STEP: Deleting pod azuredisk-volume-tester-5zfc9 in namespace azuredisk-7463
STEP: validating provisioned PV
STEP: checking the PV
Nov 28 03:14:35.193: INFO: deleting PVC "azuredisk-7463"/"pvc-9r5r7"
Nov 28 03:14:35.193: INFO: Deleting PersistentVolumeClaim "pvc-9r5r7"
STEP: waiting for claim's PV "pvc-55ba2a90-672b-4719-b1d1-0414d89cc3a4" 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 28 03:17:01.784: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-4cq5l" in namespace "azuredisk-9241" to be "Succeeded or Failed"
Nov 28 03:17:01.813: INFO: Pod "azuredisk-volume-tester-4cq5l": Phase="Pending", Reason="", readiness=false. Elapsed: 29.337835ms
Nov 28 03:17:03.841: INFO: Pod "azuredisk-volume-tester-4cq5l": Phase="Pending", Reason="", readiness=false. Elapsed: 2.057014265s
Nov 28 03:17:05.870: INFO: Pod "azuredisk-volume-tester-4cq5l": Phase="Pending", Reason="", readiness=false. Elapsed: 4.086127529s
Nov 28 03:17:07.899: INFO: Pod "azuredisk-volume-tester-4cq5l": Phase="Pending", Reason="", readiness=false. Elapsed: 6.114955589s
Nov 28 03:17:09.930: INFO: Pod "azuredisk-volume-tester-4cq5l": Phase="Pending", Reason="", readiness=false. Elapsed: 8.146046276s
Nov 28 03:17:11.959: INFO: Pod "azuredisk-volume-tester-4cq5l": Phase="Pending", Reason="", readiness=false. Elapsed: 10.174762358s
... skipping 4 lines ...
Nov 28 03:17:22.104: INFO: Pod "azuredisk-volume-tester-4cq5l": Phase="Pending", Reason="", readiness=false. Elapsed: 20.320205996s
Nov 28 03:17:24.133: INFO: Pod "azuredisk-volume-tester-4cq5l": Phase="Pending", Reason="", readiness=false. Elapsed: 22.349102448s
Nov 28 03:17:26.163: INFO: Pod "azuredisk-volume-tester-4cq5l": Phase="Pending", Reason="", readiness=false. Elapsed: 24.379163987s
Nov 28 03:17:28.193: INFO: Pod "azuredisk-volume-tester-4cq5l": Phase="Pending", Reason="", readiness=false. Elapsed: 26.409121829s
Nov 28 03:17:30.223: INFO: Pod "azuredisk-volume-tester-4cq5l": Phase="Succeeded", Reason="", readiness=false. Elapsed: 28.438540581s
STEP: Saw pod success
Nov 28 03:17:30.223: INFO: Pod "azuredisk-volume-tester-4cq5l" satisfied condition "Succeeded or Failed"
Nov 28 03:17:30.223: INFO: deleting Pod "azuredisk-9241"/"azuredisk-volume-tester-4cq5l"
Nov 28 03:17:30.266: INFO: Pod azuredisk-volume-tester-4cq5l has the following logs: e2e-test

STEP: Deleting pod azuredisk-volume-tester-4cq5l 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 28 03:18:11.309: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-9rtbp" in namespace "azuredisk-9336" to be "Error status code"
Nov 28 03:18:11.341: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Pending", Reason="", readiness=false. Elapsed: 32.070637ms
Nov 28 03:18:13.370: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Pending", Reason="", readiness=false. Elapsed: 2.061197312s
Nov 28 03:18:15.398: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Pending", Reason="", readiness=false. Elapsed: 4.089602336s
Nov 28 03:18:17.430: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Pending", Reason="", readiness=false. Elapsed: 6.120887884s
Nov 28 03:18:19.458: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Pending", Reason="", readiness=false. Elapsed: 8.149040879s
Nov 28 03:18:21.487: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Pending", Reason="", readiness=false. Elapsed: 10.178299065s
Nov 28 03:18:23.517: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Pending", Reason="", readiness=false. Elapsed: 12.207935013s
Nov 28 03:18:25.547: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Pending", Reason="", readiness=false. Elapsed: 14.23805724s
Nov 28 03:18:27.575: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Pending", Reason="", readiness=false. Elapsed: 16.265884739s
Nov 28 03:18:29.603: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Pending", Reason="", readiness=false. Elapsed: 18.29476174s
Nov 28 03:18:31.633: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Pending", Reason="", readiness=false. Elapsed: 20.324082364s
Nov 28 03:18:33.661: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Pending", Reason="", readiness=false. Elapsed: 22.352681195s
Nov 28 03:18:35.692: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Pending", Reason="", readiness=false. Elapsed: 24.382940783s
Nov 28 03:18:37.722: INFO: Pod "azuredisk-volume-tester-9rtbp": Phase="Failed", Reason="", readiness=false. Elapsed: 26.412876162s
STEP: Saw pod failure
Nov 28 03:18:37.722: INFO: Pod "azuredisk-volume-tester-9rtbp" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Nov 28 03:18:37.752: INFO: deleting Pod "azuredisk-9336"/"azuredisk-volume-tester-9rtbp"
Nov 28 03:18:37.783: INFO: Pod azuredisk-volume-tester-9rtbp has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod azuredisk-volume-tester-9rtbp in namespace azuredisk-9336
STEP: validating provisioned PV
... skipping 404 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 28 03:28:21.581: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-jhshz" in namespace "azuredisk-4547" to be "Succeeded or Failed"
Nov 28 03:28:21.618: INFO: Pod "azuredisk-volume-tester-jhshz": Phase="Pending", Reason="", readiness=false. Elapsed: 36.33447ms
Nov 28 03:28:23.647: INFO: Pod "azuredisk-volume-tester-jhshz": Phase="Pending", Reason="", readiness=false. Elapsed: 2.065242952s
Nov 28 03:28:25.677: INFO: Pod "azuredisk-volume-tester-jhshz": Phase="Pending", Reason="", readiness=false. Elapsed: 4.096060435s
Nov 28 03:28:27.708: INFO: Pod "azuredisk-volume-tester-jhshz": Phase="Pending", Reason="", readiness=false. Elapsed: 6.126372929s
Nov 28 03:28:29.738: INFO: Pod "azuredisk-volume-tester-jhshz": Phase="Pending", Reason="", readiness=false. Elapsed: 8.156988899s
Nov 28 03:28:31.769: INFO: Pod "azuredisk-volume-tester-jhshz": Phase="Pending", Reason="", readiness=false. Elapsed: 10.187671892s
... skipping 9 lines ...
Nov 28 03:28:52.067: INFO: Pod "azuredisk-volume-tester-jhshz": Phase="Pending", Reason="", readiness=false. Elapsed: 30.485165769s
Nov 28 03:28:54.098: INFO: Pod "azuredisk-volume-tester-jhshz": Phase="Pending", Reason="", readiness=false. Elapsed: 32.516075837s
Nov 28 03:28:56.127: INFO: Pod "azuredisk-volume-tester-jhshz": Phase="Running", Reason="", readiness=true. Elapsed: 34.545430156s
Nov 28 03:28:58.156: INFO: Pod "azuredisk-volume-tester-jhshz": Phase="Running", Reason="", readiness=false. Elapsed: 36.574780551s
Nov 28 03:29:00.186: INFO: Pod "azuredisk-volume-tester-jhshz": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.605033037s
STEP: Saw pod success
Nov 28 03:29:00.187: INFO: Pod "azuredisk-volume-tester-jhshz" satisfied condition "Succeeded or Failed"
Nov 28 03:29:00.187: INFO: deleting Pod "azuredisk-4547"/"azuredisk-volume-tester-jhshz"
Nov 28 03:29:00.226: INFO: Pod azuredisk-volume-tester-jhshz has the following logs: hello world
hello world
hello world

STEP: Deleting pod azuredisk-volume-tester-jhshz in namespace azuredisk-4547
... skipping 77 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 28 03:30:31.994: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-phdq8" in namespace "azuredisk-7051" to be "Succeeded or Failed"
Nov 28 03:30:32.021: INFO: Pod "azuredisk-volume-tester-phdq8": Phase="Pending", Reason="", readiness=false. Elapsed: 27.298486ms
Nov 28 03:30:34.050: INFO: Pod "azuredisk-volume-tester-phdq8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.055840275s
Nov 28 03:30:36.079: INFO: Pod "azuredisk-volume-tester-phdq8": Phase="Pending", Reason="", readiness=false. Elapsed: 4.084797168s
Nov 28 03:30:38.107: INFO: Pod "azuredisk-volume-tester-phdq8": Phase="Pending", Reason="", readiness=false. Elapsed: 6.113038252s
Nov 28 03:30:40.135: INFO: Pod "azuredisk-volume-tester-phdq8": Phase="Pending", Reason="", readiness=false. Elapsed: 8.141108302s
Nov 28 03:30:42.163: INFO: Pod "azuredisk-volume-tester-phdq8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.169490298s
... skipping 6 lines ...
Nov 28 03:30:56.366: INFO: Pod "azuredisk-volume-tester-phdq8": Phase="Pending", Reason="", readiness=false. Elapsed: 24.371981566s
Nov 28 03:30:58.400: INFO: Pod "azuredisk-volume-tester-phdq8": Phase="Pending", Reason="", readiness=false. Elapsed: 26.405889976s
Nov 28 03:31:00.434: INFO: Pod "azuredisk-volume-tester-phdq8": Phase="Running", Reason="", readiness=true. Elapsed: 28.440151503s
Nov 28 03:31:02.468: INFO: Pod "azuredisk-volume-tester-phdq8": Phase="Running", Reason="", readiness=false. Elapsed: 30.474407923s
Nov 28 03:31:04.503: INFO: Pod "azuredisk-volume-tester-phdq8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 32.509251174s
STEP: Saw pod success
Nov 28 03:31:04.503: INFO: Pod "azuredisk-volume-tester-phdq8" satisfied condition "Succeeded or Failed"
Nov 28 03:31:04.503: INFO: deleting Pod "azuredisk-7051"/"azuredisk-volume-tester-phdq8"
Nov 28 03:31:04.551: INFO: Pod azuredisk-volume-tester-phdq8 has the following logs: 100+0 records in
100+0 records out
104857600 bytes (100.0MB) copied, 0.096973 seconds, 1.0GB/s
hello world

... skipping 124 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 28 03:32:27.450: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-wt5cf" in namespace "azuredisk-1968" to be "Succeeded or Failed"
Nov 28 03:32:27.486: INFO: Pod "azuredisk-volume-tester-wt5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 35.990181ms
Nov 28 03:32:29.519: INFO: Pod "azuredisk-volume-tester-wt5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.069257669s
Nov 28 03:32:31.554: INFO: Pod "azuredisk-volume-tester-wt5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.103575021s
Nov 28 03:32:33.588: INFO: Pod "azuredisk-volume-tester-wt5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 6.138195874s
Nov 28 03:32:35.623: INFO: Pod "azuredisk-volume-tester-wt5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 8.173240231s
Nov 28 03:32:37.657: INFO: Pod "azuredisk-volume-tester-wt5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 10.206746982s
... skipping 9 lines ...
Nov 28 03:32:57.997: INFO: Pod "azuredisk-volume-tester-wt5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 30.547087228s
Nov 28 03:33:00.031: INFO: Pod "azuredisk-volume-tester-wt5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 32.580780728s
Nov 28 03:33:02.064: INFO: Pod "azuredisk-volume-tester-wt5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 34.614269228s
Nov 28 03:33:04.099: INFO: Pod "azuredisk-volume-tester-wt5cf": Phase="Pending", Reason="", readiness=false. Elapsed: 36.648552524s
Nov 28 03:33:06.133: INFO: Pod "azuredisk-volume-tester-wt5cf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 38.682885206s
STEP: Saw pod success
Nov 28 03:33:06.133: INFO: Pod "azuredisk-volume-tester-wt5cf" satisfied condition "Succeeded or Failed"
Nov 28 03:33:06.133: INFO: deleting Pod "azuredisk-1968"/"azuredisk-volume-tester-wt5cf"
Nov 28 03:33:06.197: INFO: Pod azuredisk-volume-tester-wt5cf has the following logs: hello world

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

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

  Unexpected error:
      <*exec.ExitError | 0xc00057e980>: {
          ProcessState: {
              pid: 112127,
              status: 31488,
              rusage: {
                  Utime: {Sec: 0, Usec: 505458},
... 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 1520.353 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 (1520.37s)
FAIL
FAIL	sigs.k8s.io/azuredisk-csi-driver/test/e2e	1520.436s
FAIL
make: *** [Makefile:261: e2e-test] Error 1
NAME                              STATUS   ROLES           AGE   VERSION                             INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION     CONTAINER-RUNTIME
capz-tr3rkq-control-plane-jcnfl   Ready    control-plane   30m   v1.27.0-alpha.0.52+c9a0e68a5a7905   10.0.0.4      <none>        Ubuntu 18.04.6 LTS   5.4.0-1091-azure   containerd://1.6.2
capz-tr3rkq-mp-0000000            Ready    <none>          28m   v1.27.0-alpha.0.52+c9a0e68a5a7905   10.1.0.4      <none>        Ubuntu 18.04.6 LTS   5.4.0-1091-azure   containerd://1.6.2
capz-tr3rkq-mp-0000001            Ready    <none>          28m   v1.27.0-alpha.0.52+c9a0e68a5a7905   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-8lrmd-0                           1/1     Terminating   0          34s   192.168.25.201   capz-tr3rkq-mp-0000001            <none>           <none>
... skipping 49 lines ...
STEP: Collecting events for Pod kube-system/kube-apiserver-capz-tr3rkq-control-plane-jcnfl
STEP: Creating log watcher for controller kube-system/kube-proxy-fldvj, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-fldvj
STEP: Creating log watcher for controller kube-system/kube-proxy-g84vc, container kube-proxy
STEP: Collecting events for Pod kube-system/calico-kube-controllers-657b584867-c642z
STEP: Collecting events for Pod kube-system/etcd-capz-tr3rkq-control-plane-jcnfl
STEP: failed to find events of Pod "etcd-capz-tr3rkq-control-plane-jcnfl"
STEP: Collecting events for Pod kube-system/kube-proxy-g84vc
STEP: Collecting events for Pod kube-system/kube-proxy-c5stk
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-tr3rkq-control-plane-jcnfl, container kube-scheduler
STEP: Creating log watcher for controller kube-system/calico-node-d7f8b, container calico-node
STEP: Collecting events for Pod kube-system/csi-snapshot-controller-5458dc4566-rcjgf
STEP: Creating log watcher for controller kube-system/calico-node-sprgq, container calico-node
... skipping 30 lines ...
STEP: Collecting events for Pod kube-system/csi-azuredisk-node-pj7fg
STEP: Collecting events for Pod kube-system/kube-scheduler-capz-tr3rkq-control-plane-jcnfl
STEP: Creating log watcher for controller kube-system/kube-proxy-c5stk, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-controller-manager-capz-tr3rkq-control-plane-jcnfl
STEP: Creating log watcher for controller kube-system/csi-snapshot-controller-5458dc4566-rcjgf, container csi-snapshot-controller
STEP: Collecting events for Pod kube-system/csi-snapshot-controller-5458dc4566-47r7t
STEP: Error starting logs stream for pod kube-system/kube-controller-manager-capz-tr3rkq-control-plane-jcnfl, container kube-controller-manager: container "kube-controller-manager" in pod "kube-controller-manager-capz-tr3rkq-control-plane-jcnfl" is not available
STEP: Error starting logs stream for pod kube-system/kube-apiserver-capz-tr3rkq-control-plane-jcnfl, container kube-apiserver: container "kube-apiserver" in pod "kube-apiserver-capz-tr3rkq-control-plane-jcnfl" is not available
STEP: Error starting logs stream for pod kube-system/kube-scheduler-capz-tr3rkq-control-plane-jcnfl, container kube-scheduler: container "kube-scheduler" in pod "kube-scheduler-capz-tr3rkq-control-plane-jcnfl" is not available
STEP: Fetching activity logs took 5.019821183s
================ REDACTING LOGS ================
All sensitive variables are redacted
make: Entering directory '/home/prow/go/src/k8s.io/kubernetes'
+++ [1128 03:42:57] Verifying Prerequisites....
+++ [1128 03:43:01] Removing _output directory
... skipping 12 lines ...