Error lines from build-log.txt
... skipping 260 lines ...
2024/11/18 16:12:16 Building github.com/tektoncd/pipeline/cmd/resolvers for linux/amd64
2024/11/18 16:12:16 git is in a dirty state
Please check in your pipeline what can be changing the following files:
?? kind.yaml
2024/11/18 16:12:16 Building github.com/tektoncd/pipeline/cmd/webhook for linux/amd64
Error: error processing import paths in "config/resolvers/resolvers-deployment.yaml": error resolving image references: build: go build: exit status 1: # github.com/tektoncd/pipeline/pkg/resolution/resolver/bundle
pkg/resolution/resolver/bundle/bundle.go:19:2: "errors" imported and not used
ERROR: Pipeline image resolve failed
***************************************
*** E2E TEST FAILED ***
*** Start of information dump ***
***************************************
>>> All resources:
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system pod/coredns-5dd5756b68-bw86z 1/1 Running 0 3m50s
kube-system pod/coredns-5dd5756b68-kqk6f 1/1 Running 0 3m50s
... skipping 152 lines ...
metallb-system 3m44s Warning FailedScheduling pod/controller-5c6b6c8447-lbt5f 0/4 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }, 3 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/4 nodes are available: 4 Preemption is not helpful for scheduling..
metallb-system 3m42s Normal Scheduled pod/controller-5c6b6c8447-lbt5f Successfully assigned metallb-system/controller-5c6b6c8447-lbt5f to kind-worker
metallb-system 3m41s Normal Pulling pod/controller-5c6b6c8447-lbt5f Pulling image "quay.io/metallb/controller:v0.13.10"
metallb-system 3m33s Normal Pulled pod/controller-5c6b6c8447-lbt5f Successfully pulled image "quay.io/metallb/controller:v0.13.10" in 8.232s (8.232s including waiting)
metallb-system 2m56s Normal Created pod/controller-5c6b6c8447-lbt5f Created container controller
metallb-system 2m55s Normal Started pod/controller-5c6b6c8447-lbt5f Started container controller
metallb-system 2m57s Warning Unhealthy pod/controller-5c6b6c8447-lbt5f Liveness probe failed: Get "http://10.244.1.2:7472/metrics": dial tcp 10.244.1.2:7472: connect: connection refused
metallb-system 2m55s Warning Unhealthy pod/controller-5c6b6c8447-lbt5f Readiness probe failed: Get "http://10.244.1.2:7472/metrics": dial tcp 10.244.1.2:7472: connect: connection refused
metallb-system 2m57s Normal Killing pod/controller-5c6b6c8447-lbt5f Container controller failed liveness probe, will be restarted
metallb-system 2m56s Normal Pulled pod/controller-5c6b6c8447-lbt5f Container image "quay.io/metallb/controller:v0.13.10" already present on machine
metallb-system 3m44s Normal SuccessfulCreate replicaset/controller-5c6b6c8447 Created pod: controller-5c6b6c8447-lbt5f
metallb-system 3m44s Normal ScalingReplicaSet deployment/controller Scaled up replica set controller-5c6b6c8447 to 1
metallb-system 3m39s Normal Scheduled pod/speaker-9bbs6 Successfully assigned metallb-system/speaker-9bbs6 to kind-worker3
metallb-system 3m38s Normal Pulling pod/speaker-9bbs6 Pulling image "quay.io/metallb/speaker:v0.13.10"
metallb-system 3m25s Normal Pulled pod/speaker-9bbs6 Successfully pulled image "quay.io/metallb/speaker:v0.13.10" in 12.404s (12.404s including waiting)
... skipping 16 lines ...
metallb-system 3m22s Normal Started pod/speaker-zn552 Started container speaker
metallb-system 3m44s Normal SuccessfulCreate daemonset/speaker Created pod: speaker-lnbvb
metallb-system 3m42s Normal SuccessfulCreate daemonset/speaker Created pod: speaker-zn552
metallb-system 3m39s Normal SuccessfulCreate daemonset/speaker Created pod: speaker-9bbs6
metallb-system 3m39s Normal SuccessfulCreate daemonset/speaker Created pod: speaker-f7kqf
***************************************
*** E2E TEST FAILED ***
*** End of information dump ***
***************************************
+ EXIT_VALUE=1
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
... skipping 4 lines ...
