This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: feat: bring own serviceAccount in helm install
ResultABORTED
Tests 0 failed / 9 succeeded
Started2021-07-10 03:19
Elapsed19m49s
Revisionc91dbc295841a6e4c643ee41917e1ceebb60a36a
Refs 321

No Test Failures!


Show 9 Passed Tests

Show 1 Skipped Tests

Error lines from build-log.txt

... skipping 76 lines ...

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 11248  100 11248    0     0   140k      0 --:--:-- --:--:-- --:--:--  140k
Downloading https://get.helm.sh/helm-v3.6.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 k8sprow.azurecr.io/smb-csi:e2e-02b0fe683e700bbb159c8e35139327e44518cb57 || make container-all push-manifest
Error response from daemon: manifest for k8sprow.azurecr.io/smb-csi:e2e-02b0fe683e700bbb159c8e35139327e44518cb57 not found: manifest unknown: manifest tagged by "e2e-02b0fe683e700bbb159c8e35139327e44518cb57" is not found
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/csi-driver-smb'
CGO_ENABLED=0 GOOS=windows go build -a -ldflags "-X github.com/kubernetes-csi/csi-driver-smb/pkg/smb.driverVersion=e2e-02b0fe683e700bbb159c8e35139327e44518cb57 -X github.com/kubernetes-csi/csi-driver-smb/pkg/smb.gitCommit=02b0fe683e700bbb159c8e35139327e44518cb57 -X github.com/kubernetes-csi/csi-driver-smb/pkg/smb.buildDate=2021-07-10T03:24:54Z -s -w -extldflags '-static'" -mod vendor -o _output/amd64/smbplugin.exe ./pkg/smbplugin
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 1831 lines ...
Jul 10 03:33:12.647: INFO: PersistentVolumeClaim pvc-9hm8h found but phase is Pending instead of Bound.
Jul 10 03:33:14.685: INFO: PersistentVolumeClaim pvc-9hm8h found and phase=Bound (2.076525142s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with no error
Jul 10 03:33:14.801: INFO: Waiting up to 15m0s for pod "smb-volume-tester-smnhv" in namespace "smb-1318" to be "Succeeded or Failed"
Jul 10 03:33:14.839: INFO: Pod "smb-volume-tester-smnhv": Phase="Pending", Reason="", readiness=false. Elapsed: 37.793448ms
Jul 10 03:33:16.878: INFO: Pod "smb-volume-tester-smnhv": Phase="Pending", Reason="", readiness=false. Elapsed: 2.077148433s
Jul 10 03:33:18.918: INFO: Pod "smb-volume-tester-smnhv": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.116399113s
STEP: Saw pod success
Jul 10 03:33:18.918: INFO: Pod "smb-volume-tester-smnhv" satisfied condition "Succeeded or Failed"
Jul 10 03:33:18.918: INFO: deleting Pod "smb-1318"/"smb-volume-tester-smnhv"
Jul 10 03:33:19.026: INFO: Pod smb-volume-tester-smnhv has the following logs: hello world

STEP: Deleting pod smb-volume-tester-smnhv in namespace smb-1318
Jul 10 03:33:19.072: INFO: deleting PVC "smb-1318"/"pvc-9hm8h"
Jul 10 03:33:19.072: INFO: Deleting PersistentVolumeClaim "pvc-9hm8h"
... skipping 208 lines ...
Jul 10 03:36:33.773: INFO: PersistentVolumeClaim pvc-7jcbl found but phase is Pending instead of Bound.
Jul 10 03:36:35.812: INFO: PersistentVolumeClaim pvc-7jcbl found and phase=Bound (2.076673695s)
STEP: checking the PVC
STEP: validating provisioned PV
STEP: checking the PV
STEP: deploying the pod
STEP: checking that the pods command exits with an error
Jul 10 03:36:35.926: INFO: Waiting up to 15m0s for pod "smb-volume-tester-lbb9p" in namespace "smb-495" to be "Error status code"
Jul 10 03:36:35.966: INFO: Pod "smb-volume-tester-lbb9p": Phase="Pending", Reason="", readiness=false. Elapsed: 39.473769ms
Jul 10 03:36:38.006: INFO: Pod "smb-volume-tester-lbb9p": Phase="Failed", Reason="", readiness=false. Elapsed: 2.079724798s
STEP: Saw pod failure
Jul 10 03:36:38.006: INFO: Pod "smb-volume-tester-lbb9p" satisfied condition "Error status code"
STEP: checking that pod logs contain expected message
Jul 10 03:36:38.047: INFO: deleting Pod "smb-495"/"smb-volume-tester-lbb9p"
Jul 10 03:36:38.088: INFO: Pod smb-volume-tester-lbb9p has the following logs: touch: /mnt/test-1/data: Read-only file system

STEP: Deleting pod smb-volume-tester-lbb9p in namespace smb-495
Jul 10 03:36:38.133: INFO: deleting PVC "smb-495"/"pvc-7jcbl"
... skipping 53 lines ...