Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1802647

Summary:	Any oc against 4.3 cluster prefers extensions over apps when getting deployments
Product:	OpenShift Container Platform	Reporter:	Maciej Szulik <maszulik>
Component:	kube-apiserver	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED NOTABUG	QA Contact:	Xingxing Xia <xxia>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.3.0	CC:	aos-bugs, mfojtik
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1802648 (view as bug list)		Environment:
Last Closed:	2020-02-15 10:31:56 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:
Bug Depends On:
Bug Blocks:	1802648

Description Maciej Szulik 2020-02-13 15:50:40 UTC

With extensions API being deprecated oc still picks that over apps.
The easiest way to verify that is to do:

oc get deploy -v=6

and verify you're not seeing extensions like below:

round_trippers.go:443] GET https://api.example.com:6443/apis/extensions/v1beta1/namespaces/openshift-machine-api/deployments?limit=500 200 OK in 153 milliseconds

but:

round_trippers.go:443] GET https://api.example.com:6443/apis/apps/v1/namespaces/default/deployments?limit=500 200 OK in 115 milliseconds

Comment 1 Maciej Szulik 2020-02-13 19:31:01 UTC

This is not a problem for 4.4 since these APIs are disabled, but moving to qa so that we can merge the 4.3 fix linked here.

Comment 4 Xingxing Xia 2020-02-14 14:40:11 UTC

(In reply to Maciej Szulik from comment #1)
> This is not a problem for 4.4 since these APIs are disabled, but moving to qa so that we can merge the 4.3 fix linked here
I'm confused should this bug be verified using 4.x oc against 4.y cluster? Should x=4 and y=3? Or just x=4 and y=4? If should be x=4 and y=4, then this should be closed as not a bug since 4.4 works well. If x=4 and y=3, then still reproduced:
Though `oc create deployment` is good, `oc get deploy` still uses extensions/v1beta1/:
$ oc version -o yaml
clientVersion:
  buildDate: "2020-02-14T07:28:29Z"
  ...
  gitCommit: 5d7a12f03389b03b651f963cb5ee8ddfa9cff559
  ...
  gitVersion: v4.4.0
  ...
openshiftVersion: 4.3.2
...
$ oc create deployment hello-openshift --image openshift/hello-openshift --v 6
... POST https://api...openshift.com:6443/apis/apps/v1/namespaces/testuser-44/deployments ...
$ oc get deploy --v 6
... GET https://api...openshift.com:6443/apis/extensions/v1beta1/namespaces/testuser-44/deployments?limit=500 ...

Comment 5 Maciej Szulik 2020-02-14 15:54:50 UTC

You can take whichever oc you want and you only care about server version, here 4.4, moving back to qa since 4.4 does not server extensions at all.

Comment 7 Xingxing Xia 2020-02-15 10:31:56 UTC

Thx for clarifying. Since the title says "Any oc against 4.3 cluster", thus thought this is to verify server 4.4 :)
Since as of bug 1788812#c3 in Jan these extensions were verified disabled, thus this bug reported in Feb is not an issue