-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
OpenShiftClient cannot replace existing resource with API version =! v1 #2467
Labels
Comments
@rohanKanojia this is the problem that I thought would be corrected by #2453 |
oh, okay. I will try to reproduce this and provide a fix. |
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Sep 10, 2020
…with API version =! v1 BackwardCompatibilityInterceptor should only convert openshift4 to openshift3 requests on receiving 404
11 tasks
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Sep 10, 2020
…with API version =! v1 BackwardCompatibilityInterceptor should only convert openshift4 to openshift3 requests on receiving 404
11 tasks
@rohanKanojia it works perfectly in 4.12.0 thanks a lot! |
cool, Thanks! Apologies for inconvenience caused. In previous releases we released lots of breaking changes without notifying users about it. We're discussing this here: #2518 . Feel free to share your thoughts on it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
openshift version: 3.11
appeared since: 4.11.0
affected objects: any object that has an API version different than v1, imagestream (image.openshift.io/v1), route (route.openshift.io/v1), ...
It looks like the replace mechanism has changed and you now try to POST an object to catch the error 410 to detect if it already exists. I think the POST somehow sends the wrong API version, compared to what OCP is expecting.
code sample:
stacktrace:
The text was updated successfully, but these errors were encountered: