This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: chore: refine metrics naming
ResultABORTED
Tests 0 failed / 0 succeeded
Started2022-04-24 07:27
Elapsed54m13s
Revisiondb520906489f26c291de1c1830e4a26b865dc0fc
Refs 1296

No Test Failures!


Error lines from build-log.txt

... skipping 670 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 129 lines ...
# Wait for the kubeconfig to become available.
timeout --foreground 300 bash -c "while ! kubectl get secrets | grep capz-wducy3-kubeconfig; do sleep 1; done"
capz-wducy3-kubeconfig                 cluster.x-k8s.io/secret               1      0s
# Get kubeconfig and store it locally.
kubectl get secrets capz-wducy3-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-wducy3-control-plane-rwwtg   NotReady   <none>   1s    v1.23.5
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), 0 worker machine(s), and 2 windows machine(s) to become Ready
node/capz-wduc-r64sx condition met
node/capz-wduc-xvdbf condition met
... skipping 36 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   198k      0 --:--:-- --:--:-- --:--:--  198k
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/azuredisk-csi:v1.17.0-9f832dee84b6fa7ac477cdebcee664e29fc604b1 || make container-all push-manifest
Error response from daemon: manifest for capzci.azurecr.io/azuredisk-csi:v1.17.0-9f832dee84b6fa7ac477cdebcee664e29fc604b1 not found: manifest unknown: manifest tagged by "v1.17.0-9f832dee84b6fa7ac477cdebcee664e29fc604b1" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver'
CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.driverVersion=v1.17.0-9f832dee84b6fa7ac477cdebcee664e29fc604b1 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=9f832dee84b6fa7ac477cdebcee664e29fc604b1 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2022-04-24T07:42:30Z -extldflags "-static""  -mod vendor -o _output/amd64/azurediskplugin.exe ./pkg/azurediskplugin
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 2016 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'
            - '-feature-gates=RecoverVolumeExpansionFailure=true'
            - "-timeout=240s"
          env:
            - name: ADDRESS
              value: /csi/csi.sock
          volumeMounts:
... skipping 124 lines ...
Go Version: go1.18.1
Platform: linux/amd64
Topology Key: topology.disk.csi.azure.com/zone

Streaming logs below:
STEP: Building a namespace api object, basename azuredisk
W0424 07:55:19.134705   36179 azure_disk_utils.go:165] InitializeCloudFromSecret: failed to get cloud config from secret /: failed to get secret /: resource name may not be empty
W0424 07:55:19.141219   36179 azuredisk.go:188] DisableAvailabilitySetNodes for controller is set as false while current VMType is vmss
I0424 07:55:19.142638   36179 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I0424 07:55:19.142659   36179 driver.go:81] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0424 07:55:19.142664   36179 driver.go:81] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0424 07:55:19.142668   36179 driver.go:81] Enabling controller service capability: CLONE_VOLUME
I0424 07:55:19.142683   36179 driver.go:81] Enabling controller service capability: EXPAND_VOLUME
... skipping 18 lines ...
Apr 24 07:55:23.420: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-dhl5b] to have phase Bound
Apr 24 07:55:23.464: INFO: PersistentVolumeClaim pvc-dhl5b found and phase=Bound (44.713317ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pod's command exits with an error
Apr 24 07:55:23.564: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-md998" in namespace "azuredisk-8081" to be "Error status code"
Apr 24 07:55:23.610: INFO: Pod "azuredisk-volume-tester-md998": Phase="Pending", Reason="", readiness=false. Elapsed: 45.675289ms
Apr 24 07:55:25.643: INFO: Pod "azuredisk-volume-tester-md998": Phase="Pending", Reason="", readiness=false. Elapsed: 2.07949925s
Apr 24 07:55:27.677: INFO: Pod "azuredisk-volume-tester-md998": Phase="Pending", Reason="", readiness=false. Elapsed: 4.112597306s
Apr 24 07:55:29.725: INFO: Pod "azuredisk-volume-tester-md998": Phase="Pending", Reason="", readiness=false. Elapsed: 6.161333858s
Apr 24 07:55:31.759: INFO: Pod "azuredisk-volume-tester-md998": Phase="Pending", Reason="", readiness=false. Elapsed: 8.195039252s
Apr 24 07:55:33.793: INFO: Pod "azuredisk-volume-tester-md998": Phase="Pending", Reason="", readiness=false. Elapsed: 10.229337955s
... skipping 232 lines ...
Apr 24 08:03:28.074: INFO: Pod "azuredisk-volume-tester-md998": Phase="Pending", Reason="", readiness=false. Elapsed: 8m4.510586849s
Apr 24 08:03:30.110: INFO: Pod "azuredisk-volume-tester-md998": Phase="Running", Reason="", readiness=true. Elapsed: 8m6.546458708s
Apr 24 08:03:32.146: INFO: Pod "azuredisk-volume-tester-md998": Phase="Running", Reason="", readiness=true. Elapsed: 8m8.582176733s
Apr 24 08:03:34.183: INFO: Pod "azuredisk-volume-tester-md998": Phase="Running", Reason="", readiness=true. Elapsed: 8m10.619317558s
Apr 24 08:03:36.219: INFO: Pod "azuredisk-volume-tester-md998": Phase="Running", Reason="", readiness=true. Elapsed: 8m12.655057682s
Apr 24 08:03:38.255: INFO: Pod "azuredisk-volume-tester-md998": Phase="Running", Reason="", readiness=true. Elapsed: 8m14.69134544s
Apr 24 08:03:40.291: INFO: Pod "azuredisk-volume-tester-md998": Phase="Failed", Reason="", readiness=false. Elapsed: 8m16.726878559s
STEP: Saw pod failure
Apr 24 08:03:40.291: INFO: Pod "azuredisk-volume-tester-md998" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Apr 24 08:03:40.355: INFO: deleting Pod "azuredisk-8081"/"azuredisk-volume-tester-md998"
Apr 24 08:03:40.391: INFO: Pod azuredisk-volume-tester-md998 has the following logs: Out-File : Access to the path 'C:\mnt\test-1\data.txt' is denied.
At line:1 char:22
+ ... cho 'hello world' | Out-File -FilePath C:\mnt\test-1\data.txt; Get-Co ...
+                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
... skipping 105 lines ...
  [single-az]
  /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:69
    should succeed when creating a shared disk [disk.csi.azure.com][windows]
    /home/prow/go/src/sigs.k8s.io/azuredisk-csi-driver/test/e2e/pre_provisioning_test.go:143
------------------------------
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:163
STEP: Creating a kubernetes client
Apr 24 08:04:44.626: 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 46 lines ...
Apr 24 08:04:48.532: INFO: PersistentVolumeClaim pvc-kw2vd found and phase=Bound (35.899612ms)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: attaching disk to node#0
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
Apr 24 08:05:05.406: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-4r99z" in namespace "azuredisk-5356" to be "Succeeded or Failed"
Apr 24 08:05:05.441: INFO: Pod "azuredisk-volume-tester-4r99z": Phase="Pending", Reason="", readiness=false. Elapsed: 34.849922ms
Apr 24 08:05:07.474: INFO: Pod "azuredisk-volume-tester-4r99z": Phase="Pending", Reason="", readiness=false. Elapsed: 2.067481173s
Apr 24 08:05:09.507: INFO: Pod "azuredisk-volume-tester-4r99z": Phase="Pending", Reason="", readiness=false. Elapsed: 4.101228275s
Apr 24 08:05:11.540: INFO: Pod "azuredisk-volume-tester-4r99z": Phase="Pending", Reason="", readiness=false. Elapsed: 6.133936192s
Apr 24 08:05:13.573: INFO: Pod "azuredisk-volume-tester-4r99z": Phase="Pending", Reason="", readiness=false. Elapsed: 8.166641135s
Apr 24 08:05:15.609: INFO: Pod "azuredisk-volume-tester-4r99z": Phase="Pending", Reason="", readiness=false. Elapsed: 10.202860538s
... skipping 42 lines ...