This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: fix: filesystem is not resized when restoring from snapshot with a bigger size
ResultABORTED
Tests 0 failed / 0 succeeded
Started2022-05-01 13:03
Elapsed45m27s
Revisionb9079ac367a70b52c1cb25345e856049980910d8
Refs 1309

No Test Failures!


Error lines from build-log.txt

... skipping 672 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 131 lines ...
# Wait for the kubeconfig to become available.
timeout --foreground 300 bash -c "while ! kubectl get secrets | grep capz-3yeqdm-kubeconfig; do sleep 1; done"
capz-3yeqdm-kubeconfig                 cluster.x-k8s.io/secret               1      1s
# Get kubeconfig and store it locally.
kubectl get secrets capz-3yeqdm-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-3yeqdm-control-plane-w5v5h   NotReady   control-plane,master   3s    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-3yeq-5fc7b condition met
node/capz-3yeq-7t7b5 condition met
... skipping 36 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11156  100 11156    0     0   162k      0 --:--:-- --:--:-- --:--:--  162k
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.18.0-59de170d5999bf1826de94c94c24f912e8346dd3 || make container-all push-manifest
Error response from daemon: manifest for capzci.azurecr.io/azuredisk-csi:v1.18.0-59de170d5999bf1826de94c94c24f912e8346dd3 not found: manifest unknown: manifest tagged by "v1.18.0-59de170d5999bf1826de94c94c24f912e8346dd3" 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.18.0-59de170d5999bf1826de94c94c24f912e8346dd3 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.gitCommit=59de170d5999bf1826de94c94c24f912e8346dd3 -X sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.buildDate=2022-05-01T13:18:13Z -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 2049 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
W0501 13:28:41.582803   36378 azure_disk_utils.go:165] InitializeCloudFromSecret: failed to get cloud config from secret /: failed to get secret /: resource name may not be empty
W0501 13:28:41.583608   36378 azuredisk.go:188] DisableAvailabilitySetNodes for controller is set as false while current VMType is vmss
I0501 13:28:41.584763   36378 driver.go:81] Enabling controller service capability: CREATE_DELETE_VOLUME
I0501 13:28:41.584785   36378 driver.go:81] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0501 13:28:41.584792   36378 driver.go:81] Enabling controller service capability: CREATE_DELETE_SNAPSHOT
I0501 13:28:41.584797   36378 driver.go:81] Enabling controller service capability: CLONE_VOLUME
I0501 13:28:41.584802   36378 driver.go:81] Enabling controller service capability: EXPAND_VOLUME
... skipping 23 lines ...
May  1 13:28:46.858: INFO: PersistentVolumeClaim pvc-hrszb found and phase=Bound (4.176019309s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: setting up the pod
STEP: deploying the pod
STEP: checking that the pod's command exits with no error
May  1 13:28:47.028: INFO: Waiting up to 15m0s for pod "azuredisk-volume-tester-86bpq" in namespace "azuredisk-8081" to be "Succeeded or Failed"
May  1 13:28:47.083: INFO: Pod "azuredisk-volume-tester-86bpq": Phase="Pending", Reason="", readiness=false. Elapsed: 55.661355ms
May  1 13:28:49.140: INFO: Pod "azuredisk-volume-tester-86bpq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.112581127s
May  1 13:28:51.198: INFO: Pod "azuredisk-volume-tester-86bpq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.169810093s
May  1 13:28:53.255: INFO: Pod "azuredisk-volume-tester-86bpq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.227538311s
May  1 13:28:55.313: INFO: Pod "azuredisk-volume-tester-86bpq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.28513035s
May  1 13:28:57.370: INFO: Pod "azuredisk-volume-tester-86bpq": Phase="Pending", Reason="", readiness=false. Elapsed: 10.341853423s
... skipping 131 lines ...
May  1 13:33:29.354: INFO: Pod "azuredisk-volume-tester-86bpq": Phase="Pending", Reason="", readiness=false. Elapsed: 4m42.325925791s
May  1 13:33:31.414: INFO: Pod "azuredisk-volume-tester-86bpq": Phase="Pending", Reason="", readiness=false. Elapsed: 4m44.386253123s
May  1 13:33:33.475: INFO: Pod "azuredisk-volume-tester-86bpq": Phase="Pending", Reason="", readiness=false. Elapsed: 4m46.447140799s
May  1 13:33:35.536: INFO: Pod "azuredisk-volume-tester-86bpq": Phase="Pending", Reason="", readiness=false. Elapsed: 4m48.508180668s
May  1 13:33:37.597: INFO: Pod "azuredisk-volume-tester-86bpq": Phase="Pending", Reason="", readiness=false. Elapsed: 4m50.569092305s
May  1 13:33:39.657: INFO: Pod "azuredisk-volume-tester-86bpq": Phase="Pending", Reason="", readiness=false. Elapsed: 4m52.629344693s
{"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:169","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2022-05-01T13:33:41Z"}
++ early_exit_handler
++ '[' -n 162 ']'
++ kill -TERM 162
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 4 lines ...