Bug 1441755

Summary:	oc expose fails when run against older server
Product:	OpenShift Container Platform	Reporter:	Ben Parees <bparees>
Component:	Node	Assignee:	Jordan Liggitt <jliggitt>
Status:	CLOSED ERRATA	QA Contact:	Xiaolin <xxing>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	aos-bugs, ccoleman, eparis, jokerman, mfojtik, mmccomas, smunilla, wmeng, xxia, yinzhou
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-10 05:20:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ben Parees 2017-04-12 15:45:54 UTC

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)

Comment 1 Ben Parees 2017-04-12 15:47:36 UTC

(guessing the issue here is the client trying to use api groups instead of legacy resources)

Comment 2 Eric Paris 2017-04-17 18:00:57 UTC

*** Bug 1442012 has been marked as a duplicate of this bug. ***

Comment 3 Clayton Coleman 2017-04-17 18:22:05 UTC

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.

Comment 4 Andy Goldstein 2017-04-17 19:14:37 UTC

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.

Comment 5 Andy Goldstein 2017-04-17 20:40:47 UTC

https://github.com/openshift/origin/pull/13791

Comment 7 Xiaolin 2017-06-05 09:12:00 UTC

Verified on,

Client,
oc v3.6.94

Master,
openshift v3.5.5.23
kubernetes v1.5.2+43a9be4

Comment 9 errata-xmlrpc 2017-08-10 05:20:02 UTC

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