Bug 1467936

Summary:	Ceph: no kind "StorageClass" is registered for version "storage.k8s.io/v1"
Product:	OpenShift Container Platform	Reporter:	Vladislav Walek <vwalek>
Component:	Storage	Assignee:	Matthew Wong <mawong>
Status:	CLOSED NOTABUG	QA Contact:	Jianwei Hou <jhou>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.4.1	CC:	aos-bugs, bchilds, mawong
Target Milestone:	---	Keywords:	UpcomingRelease
Target Release:	---
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:	2017-07-10 08:11:43 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 Vladislav Walek 2017-07-05 14:42:26 UTC

Description of problem:

When creating dynamic provisioning with ceph, the error shows:

When adding the storage class with "oc create -f ceph-storageclass.yml" i get:
'unable to decode "dynamic_prov/ceph-storageclass.yml": no kind "StorageClass" is registered for version "storage.k8s.io/v1beta1" '

probably related to - https://github.com/openshift/origin/issues/14468


Version-Release number of selected component (if applicable):
OpenShift Container Platform 3.4

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


Description of problem:

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

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Comment 2 Matthew Wong 2017-07-05 15:42:48 UTC

What version is 'oc', the client? The output of 'oc version'? 'oc' probably needs to be upgraded, storage.k8s.io/v1beta1 is correct for 3.4

Comment 3 Vladislav Walek 2017-07-10 08:11:43 UTC

Hello Matthew,

yes, customer used 1.3. After upgrade to 1.5, it worked.
You can close the ticket.
Thx for help