Bug 1615245 – [Priority] Client still using v1alph1.scheduling.k8s.io for the creation of priorityClass

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

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...

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Command Line Interface (Show other bugs)
Sub Component:
Version:	3.11.0
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	3.11.0
Assigned To:	Juan Vallejo
QA Contact:	Xingxing Xia
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-08-13 02:55 EDT by weiwei jiang
Modified:	2018-10-11 03:25 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-10-11 03:24:39 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-2018:2652	None	None	None	2018-10-11 03:25 EDT

Groups: None (edit)

Description weiwei jiang 2018-08-13 02:55:19 EDT

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

PR https://github.com/kubernetes/kubernetes/pull/65686 has been fixed this but not rebased to release-1.11 for kubernetes

Comment 2 Juan Vallejo 2018-08-13 14:43:47 EDT

Pick of https://github.com/kubernetes/kubernetes/pull/65686 into Origin: https://github.com/openshift/origin/pull/20624

Comment 3 Juan Vallejo 2018-08-15 09:54:17 EDT

PR has merged. Moving to MODIFIED

Comment 4 weiwei jiang 2018-08-16 04:30:14 EDT

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 01:50:55 EDT

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 03:24:39 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-2018:2652

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