Skip to content

Conversation

@adambkaplan
Copy link

Description of the change:

Golang reports that the current checksum for kubebuilder/v4 is invalid. This fixes the checksum in go.sum to the current version, which unblocks builds. That said, this change should be held until the proper checksum for the v4.1.1 tag can be verified.

Motivation for the change:

Golang 1.22.5 is reporting compile errors due to checksum mismatch.

Checklist

If the pull request includes user-facing changes, extra documentation is required:

@adambkaplan
Copy link
Author

fyi @camilamacedo86 - I ran into this issue today while trying to experiment with a potential feature.

Golang reports that the current checksum for kubebuilder/v4 is invalid.
This fixes the checksum in `go.sum` to the current version, which
unblocks builds. That said, this change should be held until the proper
checksum for the `v4.1.1` tag can be verified.

Signed-off-by: Adam Kaplan <adam.kaplan@redhat.com>
@acornett21
Copy link
Contributor

@adambkaplan I'm not sure I follow, this was built with go 1.22.5 with no issues.

@adambkaplan
Copy link
Author

I'm getting this error when I attempt to build locally (Fedora 40, go 1.22.7):

$ make build
/usr/bin/go build -gcflags "all=-trimpath=/home/adkaplan/go/src/github.com/operator-framework" -asmflags "all=-trimpath=/home/adkaplan/go/src/github.com/operator-framework" -ldflags " -X 'github.com/operator-framework/operator-sdk/internal/version.Version=v1.38.0' -X 'github.com/operator-framework/operator-sdk/internal/version.GitVersion=v1.38.0' -X 'github.com/operator-framework/operator-sdk/internal/version.GitCommit=0735b20c84e5c33cda4ed87daa3c21dcdc01bb79' -X 'github.com/operator-framework/operator-sdk/internal/version.KubernetesVersion=v1.30.0' -X 'github.com/operator-framework/operator-sdk/internal/version.ImageVersion=v1.38.0' "  -o build ./cmd/{operator-sdk,helm-operator}
verifying sigs.k8s.io/kubebuilder/v4@v4.1.1: checksum mismatch
        downloaded: h1:cYSgEfjS5qzTdc1RgPHWZgCrgd1USbz2iO+mFr7BPls=
        go.sum:     h1:aUdzTq3FjpuNIqzlJRTtRJMKZBNQnTwd05PCu7xVeAY=

SECURITY ERROR
This download does NOT match an earlier download recorded in go.sum.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

For more information, see 'go help module-auth'.
make: *** [Makefile:85: build] Error 1

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 16, 2025
@openshift-merge-robot
Copy link

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 17, 2025
@acornett21 acornett21 closed this Apr 17, 2025
@porridge
Copy link
Member

porridge commented Sep 4, 2025

My copy fetched in Feb this year has the checksum expected by operator-sdk's go.sum (h1:aUdzTq3FjpuNIqzlJRTtRJMKZBNQnTwd05PCu7xVeAY=)
When my colleague does go get sigs.k8s.io/kubebuilder/v4@v4.1.1 he gets: downloaded: h1:cYSgEfjS5qzTdc1RgPHWZgCrgd1USbz2iO+mFr7BPls=

The difference between the two is exactly this change: kubernetes-sigs/kubebuilder@e65415f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants