Bug 1836931

Summary: `oc explain localvolume` returns empty description
Product: OpenShift Container Platform Reporter: Qin Ping <piqin>
Component: StorageAssignee: OpenShift Storage Bugzilla Bot <ocp-storage-bot>
Storage sub component: Storage QA Contact: Wei Duan <wduan>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs, jsafrane, vlaad
Version: 4.5   
Target Milestone: ---   
Target Release: 4.6.0   
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: 2022-08-25 21:03:58 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 Qin Ping 2020-05-18 14:01:30 UTC
Description of problem:

Version-Release number of selected component (if applicable):
$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.5.0-0.nightly-2020-05-18-051243   True        False         3h50m   Cluster version is 4.5.0-0.nightly-2020-05-18-051243
$ oc get csv -n local-storage|grep local-storage
local-storage-operator.4.5.0-202005161517   Local Storage            4.5.0-202005161517   local-storage-operator.4.3.21-202005160952   Succeeded


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
$ oc explain localvolume
KIND:     LocalVolume
VERSION:  local.storage.openshift.io/v1

DESCRIPTION:
     <empty>


Expected results:
Should return detailed description information and related fields explanation.

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

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

Additional info:

Comment 1 Hemant Kumar 2020-06-02 04:11:15 UTC
The reason this does not work is because when upstream moved CRDs to v1, they introduced Structural schema - https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#specifying-a-structural-schema and it is somewhat stricter than what is currently coded in LocalVolume CRD. It also appears that I can't directly use CRD v1 without making some changes into LocalVolume CRD.

Comment 4 Qin Ping 2020-07-24 07:16:50 UTC
Verified with: local-storage-operator.4.6.0-202007221854.p0