Description of problem: No output from `oc explain`. Version-Release number of selected component (if applicable): 2.3.0 How reproducible: Always. Steps to Reproduce: 1. Install CNV 2. Run `oc explain KubeVirt` (Or any other API in kubevirt.io) 3. Actual results: KIND: KubeVirt VERSION: kubevirt.io/v1alpha3 DESCRIPTION: <empty> Expected results: Output similar to this: ``` oc explain Network KIND: Network VERSION: config.openshift.io/v1 DESCRIPTION: Network holds cluster-wide information about Network. The canonical name is `cluster`. It is used to configure the desired network configuration, such as: IP address pools for services/pod IPs, network plugin, etc. Please view network.spec for an explanation on what applies when configuring this resource. FIELDS: apiVersion <string> APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources kind <string> Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds metadata <Object> Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata spec <Object> -required- spec holds user settable values for configuration. As a general rule, this SHOULD NOT be read directly. Instead, you should consume the NetworkStatus, as it indicates the currently deployed configuration. Currently, most spec fields are immutable after installation. Please view the individual ones for further details on each. status <Object> status holds observed values from the cluster. They may not be overridden. ``` Additional info:
verify with cnv 2.6.0 $ oc version Client Version: 4.6.0-0.nightly-2020-07-25-091217 Server Version: 4.7.0-0.nightly-2020-12-13-224840 Kubernetes Version: v1.19.2+8ed9339 $ oc explain kubevirt KIND: KubeVirt VERSION: kubevirt.io/v1 DESCRIPTION: KubeVirt represents the object deploying all KubeVirt resources FIELDS: apiVersion <string> APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources kind <string> Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds metadata <Object> Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata spec <Object> -required- status <Object> KubeVirtStatus represents information pertaining to a KubeVirt deployment.
Storage related tickets: https://issues.redhat.com/browse/CNV-4670 https://issues.redhat.com/browse/CNV-4532
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 (Moderate: OpenShift Virtualization 2.6.0 security and bug fix update), 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/RHSA-2021:0799