We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
action url: https://github.com/spidernet-io/spiderpool/actions/runs/12755157985
The text was updated successfully, but these errors were encountered:
+ echo '===> load image quay.io/kubevirt/virt-operator:v1.4.0 to kind ...' ===> load image quay.io/kubevirt/virt-operator:v1.4.0 to kind ... + kind load docker-image quay.io/kubevirt/virt-operator:v1.4.0 --name spiderpool0113202032 Image: "quay.io/kubevirt/virt-operator:v1.4.0" with ID "sha256:ed38e09aeae413a25be6b5b00a03b1bb12631185fab9c0452e3d01a71f689fe7" not yet present on node "spiderpool0113202032-control-plane", loading... Image: "quay.io/kubevirt/virt-operator:v1.4.0" with ID "sha256:ed38e09aeae413a25be6b5b00a03b1bb12631185fab9c0452e3d01a71f689fe7" not yet present on node "spiderpool0113202032-worker", loading... + for IMAGE in ${KUBEVIRT_IMAGE_LIST} + grep quay.io/kubevirt/virt-api:v1.4.0 + echo '===> docker pull quay.io/kubevirt/virt-api:v1.4.0... ' ===> docker pull quay.io/kubevirt/virt-api:v1.4.0... + docker pull quay.io/kubevirt/virt-api:v1.4.0 Error response from daemon: received unexpected HTTP status: 502 Bad Gateway make[2]: *** [Makefile:45: kind-init] Error 1 make[2]: Leaving directory '/home/runner/work/spiderpool/spiderpool/test' make[1]: *** [Makefile:299: e2e_init] Error 2 make[1]: Leaving directory '/home/runner/work/spiderpool/spiderpool' make: *** [Makefile:327: e2e_init_cilium_ebpfservice] Error 2
failed to pull kubeVirt image.
Sorry, something went wrong.
same with #4574
weizhoublue
No branches or pull requests
action url: https://github.com/spidernet-io/spiderpool/actions/runs/12755157985
The text was updated successfully, but these errors were encountered: