This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-24 17:58
Elapsed3m18s
Revision
Builder0b29d524-1d61-11ec-8616-9ed50c11e500
infra-commit57eb2fe17
reposigs.k8s.io/gcp-compute-persistent-disk-csi-driver
repo-commitf5055fab178a409a53938e4a538984001a3b12e5
repos{u'sigs.k8s.io/gcp-compute-persistent-disk-csi-driver': u'master'}

No Test Failures!


Error lines from build-log.txt

... skipping 55 lines ...
W0924 18:00:28.403] I0924 18:00:28.403159    3626 utils.go:139] Using project k8s-gce-gci-1-5-1-6-ctl-skew and service account 322205028729-compute@developer.gserviceaccount.com
I0924 18:00:29.397] Pushing GCP Container for Linux
I0924 18:00:29.397] [make -C /go/src/sigs.k8s.io/gcp-compute-persistent-disk-csi-driver push-container GCE_PD_CSI_STAGING_VERSION=a4e78a37-4f54-4c6a-b13b-5a57b7b0722f GCE_PD_CSI_STAGING_IMAGE=gcr.io/k8s-gce-gci-1-5-1-6-ctl-skew/gcp-persistent-disk-csi-driver]
I0924 18:00:29.401] make: Entering directory '/go/src/sigs.k8s.io/gcp-compute-persistent-disk-csi-driver'
I0924 18:00:29.401] # Ensure we use a builder that can leverage it (the default on linux will not)
I0924 18:00:29.402] DOCKER_CLI_EXPERIMENTAL=enabled docker buildx rm multiarch-multiplatform-builder
W0924 18:00:29.533] error: no builder "multiarch-multiplatform-builder" found
W0924 18:00:29.540] make: [Makefile:128: init-buildx] Error 1 (ignored)
I0924 18:00:29.641] DOCKER_CLI_EXPERIMENTAL=enabled docker buildx create --use --name=multiarch-multiplatform-builder
I0924 18:00:29.668] multiarch-multiplatform-builder
I0924 18:00:29.675] DOCKER_CLI_EXPERIMENTAL=enabled docker run --rm --privileged multiarch/qemu-user-static --reset --credential yes --persistent yes
W0924 18:00:29.776] Unable to find image 'multiarch/qemu-user-static:latest' locally
W0924 18:00:30.688] latest: Pulling from multiarch/qemu-user-static
W0924 18:00:30.688] 24fb2886d6f6: Pulling fs layer
... skipping 212 lines ...
W0924 18:01:30.306] #13 0.191 Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
W0924 18:01:30.456] #13 0.361 Get:2 http://security.debian.org/debian-security buster/updates/main amd64 Packages [305 kB]
W0924 18:01:52.267] #13 ...
W0924 18:01:52.267] 
W0924 18:01:52.267] #14 [mad-hack 2/2] RUN clean-install udev
W0924 18:01:52.268] #14 60.40 Err:5 http://security.debian.org/debian-security buster/updates InRelease
W0924 18:01:52.268] #14 60.40   Connection failed [IP: 151.101.66.132 80]
W0924 18:01:52.268] #14 60.41 Fetched 8096 kB in 60s (135 kB/s)
W0924 18:01:53.170] #14 60.41 Reading package lists...
W0924 18:01:53.170] #14 61.30 W: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease  Connection failed [IP: 151.101.66.132 80]
W0924 18:01:53.170] #14 61.30 W: Some index files failed to download. They have been ignored, or old ones used instead.
W0924 18:01:54.072] #14 61.31 Reading package lists...
W0924 18:01:54.216] #14 62.21 Building dependency tree...
W0924 18:01:54.367] #14 62.42 Reading state information...
W0924 18:01:54.367] #14 62.50 Some packages could not be installed. This may mean that you have
W0924 18:01:54.367] #14 62.50 requested an impossible situation or if you are using the unstable
W0924 18:01:54.368] #14 62.50 distribution that some required packages have not yet been created
W0924 18:01:54.368] #14 62.50 or been moved out of Incoming.
W0924 18:01:54.368] #14 62.50 The following information may help to resolve the situation:
W0924 18:01:54.368] #14 62.50 
W0924 18:01:54.368] #14 62.50 The following packages have unmet dependencies:
W0924 18:01:54.517] #14 62.60  udev : Depends: libudev1 (= 241-7~deb10u7) but 241-7~deb10u8 is to be installed
W0924 18:01:54.518] #14 62.62 E: Unable to correct problems, you have held broken packages.
W0924 18:01:54.518] #14 ERROR: process "/bin/sh -c clean-install udev" did not complete successfully: exit code: 100
W0924 18:01:54.518] 
W0924 18:01:54.518] #13 [stage-2 3/4] RUN clean-install util-linux e2fsprogs mount ca-certificates udev xfsprogs
W0924 18:01:54.540] #13 CANCELED
W0924 18:01:54.540] ------
W0924 18:01:54.540]  > [mad-hack 2/2] RUN clean-install udev:
W0924 18:01:54.540] 
... skipping 12 lines ...
W0924 18:01:54.545]   26 |     # MAD HACKS: Build a version first so we can take the scsi_id bin and put it somewhere else in our real build
W0924 18:01:54.546]   27 |     FROM k8s.gcr.io/build-image/debian-base:buster-v1.9.0 as mad-hack
W0924 18:01:54.546]   28 | >>> RUN clean-install udev
W0924 18:01:54.546]   29 |     
W0924 18:01:54.546]   30 |     # Start from Kubernetes Debian base
W0924 18:01:54.546] --------------------
W0924 18:01:54.546] error: failed to solve: process "/bin/sh -c clean-install udev" did not complete successfully: exit code: 100
W0924 18:01:54.559] make: *** [Makefile:50: build-container] Error 1
I0924 18:01:54.660] make: Leaving directory '/go/src/sigs.k8s.io/gcp-compute-persistent-disk-csi-driver'
W0924 18:01:55.545] F0924 18:01:55.545222    3626 main.go:189] Failed to run integration test: failed pushing image: failed to run make command for linux: err: exit status 2
W0924 18:01:55.553] Traceback (most recent call last):
W0924 18:01:55.553]   File "/workspace/./test-infra/jenkins/../scenarios/execute.py", line 50, in <module>
W0924 18:01:55.553]     main(ARGS.env, ARGS.cmd + ARGS.args)
W0924 18:01:55.554]   File "/workspace/./test-infra/jenkins/../scenarios/execute.py", line 41, in main
W0924 18:01:55.554]     check(*cmd)
W0924 18:01:55.554]   File "/workspace/./test-infra/jenkins/../scenarios/execute.py", line 30, in check
W0924 18:01:55.554]     subprocess.check_call(cmd)
W0924 18:01:55.554]   File "/usr/lib/python2.7/subprocess.py", line 190, in check_call
W0924 18:01:55.554]     raise CalledProcessError(retcode, cmd)
W0924 18:01:55.555] subprocess.CalledProcessError: Command '('test/run-k8s-integration-migration.sh',)' returned non-zero exit status 255
E0924 18:01:55.555] Command failed
I0924 18:01:55.555] process 429 exited with code 1 after 3.1m
E0924 18:01:55.555] FAIL: ci-gcp-compute-persistent-disk-csi-driver-latest-k8s-master-migration
I0924 18:01:55.556] Call:  gcloud auth activate-service-account --key-file=/etc/service-account/service-account.json
W0924 18:01:56.292] Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
I0924 18:01:56.476] process 6469 exited with code 0 after 0.0m
I0924 18:01:56.476] Call:  gcloud config get-value account
I0924 18:01:57.283] process 6482 exited with code 0 after 0.0m
I0924 18:01:57.283] Will upload results to gs://kubernetes-jenkins/logs using pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com
... skipping 20 lines ...