-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vendor: Bump OpenShift API to Add Alibaba Platform #5216
vendor: Bump OpenShift API to Add Alibaba Platform #5216
Conversation
d86b385
to
d41ddfc
Compare
@sttts I wonder if you could take a look, as you were involved with the upstream PRs: It seems like the upstream API change to remove go-openapi, kubernetes/kube-openapi#234 has broken one of our dependencies, kubervirt/containerized-data-importer. When I update the API & client-go
I start getting compilation errors all similar to this:
So it seems this API change and removal of go-openapi is causing a failure in this generated code here as it is attempting to use go-openapi instead of kube-openapi: https://github.com/kubevirt/containerized-data-importer/blob/release-v1.12/pkg/apis/core/v1alpha1/openapi_generated.go#L26 Are issues like this expected? I have resolved the issue in this PR by replacing the kube-openapi version with one that is compatible with our dependency. Presumably this will be pinned until the dependency is fixed (the installer does not directly depend on kube-openapi). Do you think this is an acceptable fix or have any further suggestions? |
/retitle vendor: Bump OpenShift API to Add Alibaba Platform Removing this from WIP as it seems like this is an accepted way to deal with these dependencies. @jhixson74 PTAL I do need to add a comment in the code explaining the dependency Replaces #5198 |
d41ddfc
to
e87cf44
Compare
@patrickdillon Thanks for the help with this. I was able to build the Alibaba PR #5018 on top of this PR and get the code to compile. /lgtm |
/rerun |
/retest |
2 similar comments
/retest |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: staebler The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
@patrickdillon
Test okd-unit failed with similar message but I believe the test might be out-of-date?
There must be an issue with the |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
5 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
8 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/hold |
/test okd-unit |
@patrickdillon Looks like a vendor issue in the okd unit test?
|
Correct but I don't understand the issue. Why is it only failing on the okd-unit test? It looks like this okd-unit test is using a different image with go 1-14 but I'm not that familiar with these tests. |
Looks like that package may require go 1-16, so maybe we need to update the okd-unit images |
/test e2e-azurestack |
/test e2e-azurestack-upi |
2 similar comments
/test e2e-azurestack-upi |
/test e2e-azurestack-upi |
/test e2e-azurestack-upi |
let's retry this once openshift/release#22357 lands |
/hold cancel |
@patrickdillon: The following tests failed, say
Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
/test okd-unit |
/skip |
Bumps the OpenShift & k8s APIs. There seems to be a breaking change
in kube-openshift which breaks our kubevirt.io dependencies. I'm pinning
this to the earlier kube-openapi until these dependencies can be
updated.
cc @kwoodson
I believe this is a functional solution. I'm marking this as a work in progress as I am still looking into this breaking change from the kube-openapi, which were introduced, I believe in kubernetes/kube-openapi#234