CI issues (1)

Open
#340 1 comment 0 reactions 3 assignees View on GitHub

@jschoone is already working on this.

Since Jun 2, 2026.

Assessment

This issue has not been assessed yet.

Description

bug Container

We currently don't pass the CI test due to fails to get kubebuilder/kind/etcd running:

Run make test-unit
unable to fetch checksum for requested version: unable fetch metadata for kubebuilder-tools-1.29.3-linux-amd64.tar.gz -- got status "401 Unauthorized" from GCS
CREATE_KIND_CLUSTER=false KUBEBUILDER_ASSETS="" /home/runner/work/cluster-stack-operator/cluster-stack-operator/hack/tools/bin/gotestsum --junitfile=.coverage/junit.xml --format testname -- -mod=vendor \
-covermode=atomic -coverprofile=.coverage/cover.out -p=4 ./internal/controller/...
PASS internal/controller.TestMakeDiff (0.00s)
PASS internal/controller.TestGetLatestReadyClusterStackRelease/a_ready,_latest_cluster_stack_release_present (0.00s)
PASS internal/controller.TestGetLatestReadyClusterStackRelease/No_ready_cluster_stack_releases (0.00s)
PASS internal/controller.TestGetLatestReadyClusterStackRelease (0.00s)
PASS internal/controller.TestGetUsableClusterStackReleaseVersions/two_ready_cluster_stack_releases (0.00s)
PASS internal/controller.TestGetUsableClusterStackReleaseVersions/no_ready_cluster_stack_releases (0.00s)
PASS internal/controller.TestGetUsableClusterStackReleaseVersions (0.00s)
PASS internal/controller.TestGetClusterStackReleasesInSpec (0.00s)
FAIL internal/controller
=== RUN   TestControllers
Running Suite: Controller Suite - /home/runner/work/cluster-stack-operator/cluster-stack-operator/internal/controller
=====================================================================================================================
Random Seed: 1780379897

Will run 40 of 40 specs
E0602 05:58:17.429576   14191 server.go:328] "unable to start the controlplane" err="exec: \"etcd\": executable file not found in $PATH" logger="controller-runtime.test-env" tries=0
Dominant language
Go
Stars
18
Forks
5
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SovereignCloudStack/cluster-stack-operator

All issues in SovereignCloudStack/cluster-stack-operator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.