[18.0-fr5] Remove go.work before container build#872
Conversation
The go.work file is generated by the CI environment which may have a higher Go version than the build image (go-toolset). This causes build failures when go.work references a Go version that the build image does not provide. Since the Dockerfile builds a single module, go.work is not needed and can be safely removed before building. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Martin Schuppert <mschuppert@redhat.com>
|
/retest |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/ef11f11f428247cab395953991a61db9 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 51m 14s |
|
recheck |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: openshift-cherrypick-robot, stuggi The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/cd758969c668476792958c9b7a79264e ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 17m 55s |
|
recheck |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/a549f9ef76ec4d90979d13ee7d386192 ❌ openstack-k8s-operators-content-provider FAILURE in 4m 22s |
|
recheck |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/ad1a18ccd1864cf89e20da3124ea9b16 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 47m 06s |
|
not sure if this is a real issue with the minio setup for fr5 branch tests? |
|
@stuggi I think I've seen most of the issue previously and it usually didn't result in a CI failure. What I think is the interesting part of that message is: I've seen that fail in the past and I've added waits for the CRD to be present. I'll try it again, maybe we'll get more lucky. I'll take a look at our playbooks and maybe move the route CRD wait around, so that it catches this issue as well. |
|
recheck |
|
I see. I never cherry-picked the "route wait PR" into fr-5. I created the PR #874 |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/7e31cac2884a4ea882179ca3f2108b74 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 27m 46s |
This is an automated cherry-pick of #871
/assign stuggi