Bump openshift/api and mention failure.#73
Bump openshift/api and mention failure.#73openshift-merge-bot[bot] merged 3 commits intoopenshift:mainfrom
Conversation
|
@kannon92 That looks like you may be using a version of controller-gen that doesn't have the changes to support the With this being an OpenShift repo, would it make sense to point the controller-gen reference in this repo to https://github.com/openshift/kubernetes-sigs-controller-tools ? We do have this change merged into this fork in the |
a4c99c3 to
5671c59
Compare
|
@everettraven I'm having some trouble importing this. kehannon@kehannon-thinkpadp1gen4i:~/Work/openshift/kueue-operator$ go get github.com/openshift/kubernetes-sigs-controller-tools@latest
go: github.com/openshift/kubernetes-sigs-controller-tools@latest (v0.12.0) requires github.com/openshift/kubernetes-sigs-controller-tools@v0.12.0: parsing go.mod:
module declares its path as: sigs.k8s.io/controller-tools
but was required as: github.com/openshift/kubernetes-sigs-controller-toolsAny ideas on how to fix this? |
5671c59 to
b516b70
Compare
|
/hold cancel |
|
/retest |
|
Thank you to @everettraven! He pointed out the fix and I think we are good to go with merging this. We have to switch to controller-tools from openshift to get some patches that are tracking ahead of upstream. |
|
/retest |
1 similar comment
|
/retest |
b516b70 to
c7a6202
Compare
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
@kannon92: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kannon92, PannagaRao 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 |
If we take the latest sha of openshift/api, we are hitting the following failure:
Tracking this down, I think openshift/api@6b76c18 is causing an error for us.
cc @everettraven
Note, our CI says this passes because we don't check CRD generation yet.