This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: feat: switch to async disk attach/detach
ResultABORTED
Tests 0 failed / 10 succeeded
Started2021-07-28 07:52
Elapsed41m10s
Revision83d456b5cb215fac95bb2bdc01f172a5a0abce51
Refs 897

No Test Failures!


Show 10 Passed Tests

Show 43 Skipped Tests

Error lines from build-log.txt

... skipping 887 lines ...
        - name: csi-resizer
          image: "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.1.0"
          args:
            - "-csi-address=$(ADDRESS)"
            - "-v=2"
            - "-leader-election"
            - '-handle-volume-inuse-error=true'
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          volumeMounts:
            - name: socket-dir
              mountPath: /csi
... skipping 120 lines ...
Git Commit: N/A
Go Version: go1.16.6
Platform: linux/amd64
Topology Key: topology.disk.csi.azure.com/zone

Streaming logs below:
E0728 08:01:53.390833   14244 azure_config.go:45] Failed to get cloud-config from secret: failed to get secret /: resource name may not be empty
W0728 08:01:53.391837   14244 azuredisk.go:207] DisableAvailabilitySetNodes for controller is set as false while current VMType is vmss
I0728 08:01:53.392237   14244 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I0728 08:01:53.392253   14244 driver.go:81] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0728 08:01:53.392259   14244 driver.go:81] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0728 08:01:53.392265   14244 driver.go:81] Enabling controller service capability: LIST_SNAPSHOTS
I0728 08:01:53.392270   14244 driver.go:81] Enabling controller service capability: CLONE_VOLUME
... skipping 66 lines ...

    test case is only available for CSI drivers

    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:263
------------------------------
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:158
STEP: Creating a kubernetes client
Jul 28 08:01:53.933: INFO: >>> kubeConfig: /root/tmp040991256/kubeconfig/kubeconfig.northcentralus.json
STEP: Building a namespace api object, basename azuredisk
STEP: Waiting for a default service account to be provisioned in namespace
I0728 08:01:54.008731   14244 azuredisk_driver.go:57] Using azure disk driver: kubernetes.io/azure-disk
... skipping 2 lines ...

S [SKIPPING] [0.108 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:67
    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:158

    test case is only available for CSI drivers

    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/suite_test.go:263
------------------------------
... skipping 51 lines ...
STEP: Building a namespace api object, basename azuredisk
STEP: Waiting for a default service account to be provisioned in namespace
I0728 08:01:54.356559   14244 azuredisk_driver.go:57] Using azure disk driver: kubernetes.io/azure-disk
STEP: Successfully provisioned AzureDisk volume: "/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/kubetest-bkm7bu0x/providers/Microsoft.Compute/disks/pre-provisioned-inline-volume"

STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Jul 28 08:01:57.725: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-cbxsk" in namespace "azuredisk-5541" to be "Succeeded or Failed"
Jul 28 08:01:57.742: INFO: Pod "azuredisk-volume-tester-cbxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 17.479096ms
Jul 28 08:01:59.757: INFO: Pod "azuredisk-volume-tester-cbxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 2.031897934s
Jul 28 08:02:01.772: INFO: Pod "azuredisk-volume-tester-cbxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 4.047781033s
Jul 28 08:02:03.788: INFO: Pod "azuredisk-volume-tester-cbxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 6.062888721s
Jul 28 08:02:05.802: INFO: Pod "azuredisk-volume-tester-cbxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 8.077079058s
Jul 28 08:02:07.816: INFO: Pod "azuredisk-volume-tester-cbxsk": Phase="Pending", Reason="", readiness=false. Elapsed: 10.091397315s
... skipping 132 lines ...
Jul 28 08:06:37.546: INFO: Pod "azuredisk-volume-tester-cbxsk": Phase="Running", Reason="", readiness=true. Elapsed: 4m39.821227107s
Jul 28 08:06:39.562: INFO: Pod "azuredisk-volume-tester-cbxsk": Phase="Running", Reason="", readiness=true. Elapsed: 4m41.837067577s
Jul 28 08:06:41.578: INFO: Pod "azuredisk-volume-tester-cbxsk": Phase="Running", Reason="", readiness=true. Elapsed: 4m43.853531682s
Jul 28 08:06:43.593: INFO: Pod "azuredisk-volume-tester-cbxsk": Phase="Running", Reason="", readiness=true. Elapsed: 4m45.868688645s
Jul 28 08:06:45.609: INFO: Pod "azuredisk-volume-tester-cbxsk": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4m47.884056751s
STEP: Saw pod success
Jul 28 08:06:45.609: INFO: Pod "azuredisk-volume-tester-cbxsk" satisfied condition "Succeeded or Failed"
Jul 28 08:06:45.609: INFO: deleting Pod "azuredisk-5541"/"azuredisk-volume-tester-cbxsk"
Jul 28 08:06:45.693: INFO: Pod azuredisk-volume-tester-cbxsk has the following logs: ´╗┐hello world

STEP: Deleting pod azuredisk-volume-tester-cbxsk in namespace azuredisk-5541
Jul 28 08:06:45.714: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "azuredisk-5541" for this suite.
... skipping 21 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
Jul 28 08:06:46.490: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-d95jn" in namespace "azuredisk-5356" to be "Succeeded or Failed"
Jul 28 08:06:46.508: INFO: Pod "azuredisk-volume-tester-d95jn": Phase="Pending", Reason="", readiness=false. Elapsed: 17.669759ms
Jul 28 08:06:48.524: INFO: Pod "azuredisk-volume-tester-d95jn": Phase="Pending", Reason="", readiness=false. Elapsed: 2.034140435s
Jul 28 08:06:50.538: INFO: Pod "azuredisk-volume-tester-d95jn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.047932449s
Jul 28 08:06:52.553: INFO: Pod "azuredisk-volume-tester-d95jn": Phase="Pending", Reason="", readiness=false. Elapsed: 6.062846387s
Jul 28 08:06:54.567: INFO: Pod "azuredisk-volume-tester-d95jn": Phase="Pending", Reason="", readiness=false. Elapsed: 8.077490474s
Jul 28 08:06:56.582: INFO: Pod "azuredisk-volume-tester-d95jn": Phase="Pending", Reason="", readiness=false. Elapsed: 10.092481488s
... skipping 41 lines ...
Jul 28 08:08:21.258: INFO: Pod "azuredisk-volume-tester-d95jn": Phase="Pending", Reason="", readiness=false. Elapsed: 1m34.767780313s
Jul 28 08:08:23.275: INFO: Pod "azuredisk-volume-tester-d95jn": Phase="Running", Reason="", readiness=true. Elapsed: 1m36.784543728s
Jul 28 08:08:25.288: INFO: Pod "azuredisk-volume-tester-d95jn": Phase="Running", Reason="", readiness=true. Elapsed: 1m38.798164097s
Jul 28 08:08:27.303: INFO: Pod "azuredisk-volume-tester-d95jn": Phase="Running", Reason="", readiness=true. Elapsed: 1m40.812688933s
Jul 28 08:08:29.321: INFO: Pod "azuredisk-volume-tester-d95jn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 1m42.830516039s
STEP: Saw pod success
Jul 28 08:08:29.321: INFO: Pod "azuredisk-volume-tester-d95jn" satisfied condition "Succeeded or Failed"
Jul 28 08:08:29.321: INFO: deleting Pod "azuredisk-5356"/"azuredisk-volume-tester-d95jn"
Jul 28 08:08:29.399: INFO: Pod azuredisk-volume-tester-d95jn has the following logs: ´╗┐hello world

STEP: Deleting pod azuredisk-volume-tester-d95jn in namespace azuredisk-5356
STEP: validating provisioned PV
STEP: checking the PV
... skipping 147 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
Jul 28 08:09:12.739: INFO: Waiting up to 10m0s for pod "azuredisk-volume-tester-fmgw9" in namespace "azuredisk-2451" to be "Error status code"
Jul 28 08:09:12.755: INFO: Pod "azuredisk-volume-tester-fmgw9": Phase="Pending", Reason="", readiness=false. Elapsed: 15.456189ms
Jul 28 08:09:14.770: INFO: Pod "azuredisk-volume-tester-fmgw9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.030045557s
Jul 28 08:09:16.789: INFO: Pod "azuredisk-volume-tester-fmgw9": Phase="Pending", Reason="", readiness=false. Elapsed: 4.049763185s
Jul 28 08:09:18.805: INFO: Pod "azuredisk-volume-tester-fmgw9": Phase="Pending", Reason="", readiness=false. Elapsed: 6.065131372s
Jul 28 08:09:20.820: INFO: Pod "azuredisk-volume-tester-fmgw9": Phase="Pending", Reason="", readiness=false. Elapsed: 8.080593324s
Jul 28 08:09:22.835: INFO: Pod "azuredisk-volume-tester-fmgw9": Phase="Pending", Reason="", readiness=false. Elapsed: 10.095542021s
... skipping 147 lines ...
Jul 28 08:14:21.147: INFO: Pod "azuredisk-volume-tester-fmgw9": Phase="Pending", Reason="", readiness=false. Elapsed: 5m8.40754399s
Jul 28 08:14:23.163: INFO: Pod "azuredisk-volume-tester-fmgw9": Phase="Pending", Reason="", readiness=false. Elapsed: 5m10.423241169s
Jul 28 08:14:25.179: INFO: Pod "azuredisk-volume-tester-fmgw9": Phase="Running", Reason="", readiness=true. Elapsed: 5m12.439077777s
Jul 28 08:14:27.194: INFO: Pod "azuredisk-volume-tester-fmgw9": Phase="Running", Reason="", readiness=true. Elapsed: 5m14.454457037s
Jul 28 08:14:29.208: INFO: Pod "azuredisk-volume-tester-fmgw9": Phase="Running", Reason="", readiness=true. Elapsed: 5m16.468424662s
Jul 28 08:14:31.223: INFO: Pod "azuredisk-volume-tester-fmgw9": Phase="Running", Reason="", readiness=true. Elapsed: 5m18.483529839s
Jul 28 08:14:33.238: INFO: Pod "azuredisk-volume-tester-fmgw9": Phase="Failed", Reason="", readiness=false. Elapsed: 5m20.498850638s
STEP: Saw pod failure
Jul 28 08:14:33.238: INFO: Pod "azuredisk-volume-tester-fmgw9" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Jul 28 08:14:33.317: INFO: deleting Pod "azuredisk-2451"/"azuredisk-volume-tester-fmgw9"
Jul 28 08:14:33.337: INFO: Pod azuredisk-volume-tester-fmgw9 has the following logs: out-file : Access to the path 'C:\mnt\test-1\data' is denied.
At line:1 char:1
+ echo $null >> C:\mnt\test-1\data
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
... skipping 265 lines ...