Bug 1549873

Summary:	no n-1 compatibility for oc scale
Product:	OpenShift Container Platform	Reporter:	Candace Sheremeta <cshereme>
Component:	oc	Assignee:	Juan Vallejo <jvallejo>
Status:	CLOSED ERRATA	QA Contact:	Xingxing Xia <xxia>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.7.0	CC:	aos-bugs, cshereme, david_hocky, erich, jokerman, mmccomas, rbost
Target Milestone:	---
Target Release:	3.7.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-05 09:39:53 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 Candace Sheremeta 2018-02-27 23:43:55 UTC

Description of problem:
Running the following command with oc-3.7.23 in OSCP 3.6 cluster gives the following error:

$ oc scale dc/app-cli --replicas=2
error: no kind "Scale" is registered for version "extensions/v1beta1"

but running the command with oc-3.6.173.0.96 gives:

$ ./oc scale dc/app-cli --replicas=2
deploymentconfig "app-cli" scaled

Version-Release number of selected component (if applicable):
oc-3.7.23

How reproducible:
100%

Steps to Reproduce:
1. Set up container app on OSCP 3.6 (I used PHP 7.0)
2. Install oc-3.7.23 on local machine and login to cluster
3. Try to scale with above command

Actual results:
error: no kind "Scale" is registered for version "extensions/v1beta1"

Expected results:
deploymentconfig "app-cli" scaled

Additional info:
@erich mentioned that he thought we were supposed to have n-1 compatibility for oc. I found https://docs.openshift.com/container-platform/3.7/release_notes/index.html which seems to agree (at least according to my interpretation). Setting needinfo on him to confirm.

Comment 2 Xingxing Xia 2018-02-28 02:59:45 UTC

Also double checked other oc versions (v3.7.23, v3.7.27) against server version v3.6.173.0.104. v3.7.23 indeed reproduces issue, while v3.7.27 works:
$ v3.7.27/oc scale dc/hello-openshift --replicas=2
deploymentconfig "hello-openshift" scaled

It is fixed in v3.7.27

Comment 3 Eric Rich 2018-02-28 14:17:47 UTC

(In reply to Xingxing Xia from comment #2)
> Also double checked other oc versions (v3.7.23, v3.7.27) against server
> version v3.6.173.0.104. v3.7.23 indeed reproduces issue, while v3.7.27 works:
> $ v3.7.27/oc scale dc/hello-openshift --replicas=2
> deploymentconfig "hello-openshift" scaled
> 
> It is fixed in v3.7.27

Based on this it should be save to say this is fixed in the current release! 
Candace if you can confirm, we can close this.

Comment 4 Eric Rich 2018-02-28 14:30:17 UTC

(In reply to Eric Rich from comment #3)
> (In reply to Xingxing Xia from comment #2)
> > Also double checked other oc versions (v3.7.23, v3.7.27) against server
> > version v3.6.173.0.104. v3.7.23 indeed reproduces issue, while v3.7.27 works:
> > $ v3.7.27/oc scale dc/hello-openshift --replicas=2
> > deploymentconfig "hello-openshift" scaled
> > 
> > It is fixed in v3.7.27
> 
> Based on this it should be save to say this is fixed in the current release! 
> Candace if you can confirm, we can close this.

According to https://access.redhat.com/downloads/content/290/ver=3.7/rhel---7/3.7.23/x86_64/product-software v3.7.23 is latest so this likely needs to be attached to the errata shipping v3.7.27 (moving to Modified).

Comment 7 Candace Sheremeta 2018-02-28 18:13:55 UTC

Can confirm issue fixed in oc-3.7.27

Comment 8 Eric Rich 2018-02-28 19:13:43 UTC

(In reply to Candace Sheremeta from comment #7)
> Can confirm issue fixed in oc-3.7.27

(In reply to Xingxing Xia from comment #2)
> Also double checked other oc versions (v3.7.23, v3.7.27) against server
> version v3.6.173.0.104. v3.7.23 indeed reproduces issue, while v3.7.27 works:
> $ v3.7.27/oc scale dc/hello-openshift --replicas=2
> deploymentconfig "hello-openshift" scaled
> 
> It is fixed in v3.7.27

Based on these moving to VERIFIED

Comment 12 errata-xmlrpc 2018-04-05 09:39:53 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/RHBA-2018:0636