Bug 1463576 – oc get/describe could not work when using 3.5 client to login 3.6 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 1463576 - oc get/describe could not work when using 3.5 client to login 3.6 server

Summary:	oc get/describe could not work when using 3.5 client to login 3.6 server

Status:	CLOSED ERRATA

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	3.5.z
Assigned To:	Michal Fojtik
QA Contact:	Chuan Yu
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1441089
Blocks:
	Show dependency tree / graph

Reported:	2017-06-21 05:11 EDT by Michal Fojtik
Modified:	2017-10-25 09:02 EDT (History)
CC List:	10 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Cause: The upstream discovery was not set to prefer version v1 and instead it preferred the API group version. Consequence: Old oc client can get this discovery info when talking to newer server and prefer the grouped API version of the resource which it could not handle as it does not recognize it. Fix: Prefer v1 in discovery Result:
Story Points:	---
Clone Of:	1441089
Environment:
Last Closed:	2017-10-25 09:02:19 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	RHBA-2017:3049	normal	SHIPPED_LIVE	OpenShift Container Platform 3.6, 3.5, and 3.4 bug fix and enhancement update	2017-10-25 11:57:15 EDT

Groups: None (edit)

Comment 1 Chuan Yu 2017-06-21 05:18:58 EDT

The issue fixed with OCP 3.5.5.28

Comment 3 errata-xmlrpc 2017-10-25 09:02:19 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/RHBA-2017:3049

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