This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-10-15 04:50
Elapsed48m33s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 365 lines ...
Trying to find master named 'e2e-c4096e2ee6-24e2a-master'
Looking for address 'e2e-c4096e2ee6-24e2a-master-ip'
Using master: e2e-c4096e2ee6-24e2a-master (external IP: 34.83.25.80; internal IP: (not set))
Waiting up to 300 seconds for cluster initialization.

  This will continually check to see if the API for kubernetes is reachable.
  This may time out if there was some uncaught error during start up.

.....Kubernetes cluster created.
Cluster "k8s-jkns-e2e-gce-gci-serial_e2e-c4096e2ee6-24e2a" set.
User "k8s-jkns-e2e-gce-gci-serial_e2e-c4096e2ee6-24e2a" set.
Context "k8s-jkns-e2e-gce-gci-serial_e2e-c4096e2ee6-24e2a" created.
Switched to context "k8s-jkns-e2e-gce-gci-serial_e2e-c4096e2ee6-24e2a".
... skipping 34 lines ...
e2e-c4096e2ee6-24e2a-windows-node-group-3303   Ready                      <none>   19s     v1.20.0-alpha.2.99+b3d4b8ed8a07d0
e2e-c4096e2ee6-24e2a-windows-node-group-k09b   Ready                      <none>   24s     v1.20.0-alpha.2.99+b3d4b8ed8a07d0
e2e-c4096e2ee6-24e2a-windows-node-group-qz6z   Ready                      <none>   24s     v1.20.0-alpha.2.99+b3d4b8ed8a07d0
Warning: v1 ComponentStatus is deprecated in v1.19+
Validate output:
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME                 STATUS    MESSAGE             ERROR
controller-manager   Healthy   ok                  
scheduler            Healthy   ok                  
etcd-1               Healthy   {"health":"true"}   
etcd-0               Healthy   {"health":"true"}   
Cluster validation succeeded
Done, listing cluster services:
... skipping 541 lines ...
gcloud docker -- push gcr.io/k8s-jkns-e2e-gce-gci-serial/gcp-persistent-disk-csi-driver:026df02c-8fe2-4508-ad31-4c108693e485
WARNING: `gcloud docker` will not be supported for Docker client versions above 18.03.

As an alternative, use `gcloud auth configure-docker` to configure `docker` to
use `gcloud` as a credential helper, then use `docker` as you would for non-GCR
registries, e.g. `docker pull gcr.io/project-id/my-image`. Add
`--verbosity=error` to silence this warning: `gcloud docker
--verbosity=error -- pull gcr.io/project-id/my-image`.

See: https://cloud.google.com/container-registry/docs/support/deprecation-notices#gcloud-docker

The push refers to repository [gcr.io/k8s-jkns-e2e-gce-gci-serial/gcp-persistent-disk-csi-driver]
864d089637e2: Preparing
33ae3ba49612: Preparing
... skipping 8 lines ...
Building and Pushing GCP Container for Windows
[make -C /home/prow/go/src/sigs.k8s.io/gcp-compute-persistent-disk-csi-driver build-and-push-windows-container-ltsc2019 GCE_PD_CSI_STAGING_VERSION=026df02c-8fe2-4508-ad31-4c108693e485 GCE_PD_CSI_STAGING_IMAGE=gcr.io/k8s-jkns-e2e-gce-gci-serial/gcp-persistent-disk-csi-driver-win]
make: Entering directory '/home/prow/go/src/sigs.k8s.io/gcp-compute-persistent-disk-csi-driver'
# Ensure we use a builder that can leverage it (the default on linux will not)
DOCKER_CLI_EXPERIMENTAL=enabled docker buildx rm windows-builder
no builder "windows-builder" found
make: [Makefile:69: init-buildx] Error 1 (ignored)
DOCKER_CLI_EXPERIMENTAL=enabled docker buildx create --use --name=windows-builder
windows-builder
# Register gcloud as a Docker credential helper.
# Required for "docker buildx build --push".
gcloud auth configure-docker --quiet
Adding credentials for all GCR repositories.
... skipping 272 lines ...
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
Cleaning up after docker
++ docker ps -aq
++ xargs -r docker rm -f
make: *** [Makefile:531: kubectl] Terminated
{"component":"entrypoint","file":"prow/entrypoint/run.go:169","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2020-10-15T05:39:07Z"}
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?