Prow jobs use the incorrect Go version #20576
Description
Bug report criteria
- This bug report is not security related, security issues should be disclosed privately via security@etcd.io.
- This is not a support request or question, support requests or questions should be raised in the etcd discussion forums.
- You have read the etcd bug reporting guidelines.
- Existing open issues along with etcd frequently asked questions have been checked and this is not a duplicate.
What happened?
The Prow jobs in test-infra, are using the Go version provided by the kubekins image. Even though we have the toolchain defined in the go.mod. According to the Go toolchain documentation:
When the go or toolchain line is newer than the bundled toolchain, the go command runs the newer toolchain instead.
Therefore, because the kubekins image is using Go 1.24, and our release branches were using 1.23, that means that testing was done with Go 1.23.
Follow up on kubernetes/test-infra#35363 (comment)
What did you expect to happen?
We should use the Go version defined in the go.mod toolchain (or .go-version). We can do this by setting GOTOOLCHAIN in all of our Prow jobs.
How can we reproduce it (as minimally and precisely as possible)?
Any Prow job from the stable release branches has this behavior.
Anything else we need to know?
No response
Etcd version (please run commands below)
$ etcd --version
# paste output here
$ etcdctl version
# paste output hereEtcd configuration (command line flags or environment variables)
paste your configuration here
Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)
$ etcdctl member list -w table
# paste output here
$ etcdctl --endpoints=<member list> endpoint status -w table
# paste output here