Bug 1441755 – oc expose fails when run against older server

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1441755 - oc expose fails when run against older server

Summary:	oc expose fails when run against older server

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Pod (Show other bugs)
Sub Component:
Version:	3.6.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jordan Liggitt
QA Contact:	Xiaolin
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	1442012 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-04-12 11:45 EDT by Ben Parees
Modified:	2017-08-16 15 EDT (History)
CC List:	10 users (show)

See Also:
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:	undefined
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-08-10 01:20:02 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2017:1716	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.6 RPM Release Advisory	2017-08-10 05:02:50 EDT

Groups: None (edit)

Description Ben Parees 2017-04-12 11:45:54 EDT

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@redhat.com" 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 11:47:36 EDT

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

Comment 2 Eric Paris 2017-04-17 14:00:57 EDT

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

Comment 3 Clayton Coleman 2017-04-17 14:22:05 EDT

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 15:14:37 EDT

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 16:40:47 EDT

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

Comment 7 Xiaolin 2017-06-05 05:12:00 EDT

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 01:20:02 EDT

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

Note You need to log in before you can comment on or make changes to this bug.