Bug 1615245 - [Priority] Client still using v1alph1.scheduling.k8s.io for the creation of priorityClass
Summary: [Priority] Client still using v1alph1.scheduling.k8s.io for the creation of p...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.0
Assignee: Juan Vallejo
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-13 06:55 UTC by weiwei jiang
Modified: 2018-10-11 07:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-11 07:24:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 0 None None None 2018-10-11 07:25:07 UTC

Description weiwei jiang 2018-08-13 06:55:19 UTC
Description of problem:
when create priorityclass with oc create priorityclass, got error 'error: no matches for kind "PriorityClass" in version "scheduling.k8s.io/v1alpha1"'

Version-Release number of selected component (if applicable):
# oc version 
oc v3.11.0-0.13.0
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://qe-wjiang-master-etcd-1:8443
openshift v3.11.0-0.13.0
kubernetes v1.11.0+d4cacc0


How reproducible:
Always

Steps to Reproduce:
1.  oc create priorityclass dp --value=-1 --global-default=false --description="aoeuoae"

2.
3.

Actual results:
# oc create priorityclass dp --value=-1 --global-default=false --description="aoeuoae"
error: no matches for kind "PriorityClass" in version "scheduling.k8s.io/v1alpha1"


Expected results:
Should use v1beta1 to do the restapi requests

Additional info:

Comment 1 weiwei jiang 2018-08-13 06:56:01 UTC
PR https://github.com/kubernetes/kubernetes/pull/65686 has been fixed this but not rebased to release-1.11 for kubernetes

Comment 3 Juan Vallejo 2018-08-15 13:54:17 UTC
PR has merged. Moving to MODIFIED

Comment 4 weiwei jiang 2018-08-16 08:30:14 UTC
Checked on 
# oc version                                                                  
oc v3.11.0-0.16.0                                                                                           
kubernetes v1.11.0+d4cacc0                                                                                     
features: Basic-Auth GSSAPI Kerberos SPNEGO                                                                    

Server https://qe-wjiang-master-etcd-1:8443                                                                    
openshift v3.11.0-0.16.0
kubernetes v1.11.0+d4cacc0

and the issue has been fixed

Comment 6 weiwei jiang 2018-08-27 05:50:55 UTC
Checked again with 
# oc version 
oc v3.11.0-0.22.0
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://qe-wjiang-master-etcd-1:8443
openshift v3.11.0-0.22.0
kubernetes v1.11.0+d4cacc0

And the issue has been fixed

Comment 8 errata-xmlrpc 2018-10-11 07:24:39 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:2652


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