Description of problem: When using a v3.6 oc client (one that has api groups) against an older server (3.5), oc expose fails. How reproducible: always Steps to Reproduce: 1. oc expose service someservice Actual results: Error from server (Forbidden): User "bparees" cannot create route.openshift.io.routes in project "bparees-parks" Expected results: route created (I have proper permissions to create routes)
(guessing the issue here is the client trying to use api groups instead of legacy resources)
*** Bug 1442012 has been marked as a duplicate of this bug. ***
We said we would do a reasonable job of having 3.6 talk to 3.5, so I think Michal does need to fix this.
This is happening because the types for the new api groups are being added to the scheme first, before the legacy types. I'm changing this so the legacy types are consistently added first.
https://github.com/openshift/origin/pull/13791
Verified on, Client, oc v3.6.94 Master, openshift v3.5.5.23 kubernetes v1.5.2+43a9be4
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1716