Description of problem:
`oc explain bmh` returns empty description
Version-Release number of selected component (if applicable):
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.5.0-0.nightly-2020-06-11-183238 True False 32m Cluster version is 4.5.0-0.nightly-2020-06-11-183238
Steps to Reproduce:
1.oc explain bmh
$ oc explain bmh
Should return detailed description and related fields explanation.
$ oc version
Client Version: 4.5.0-202005291417-9933eb9
Each API is responsible for providing their own description, thus moving accordingly to bare metal team to update their API.
This is fixed in 4.6 by https://github.com/openshift/baremetal-operator/commit/37520539587120fa54e4ace7992225a7516ac1ca and https://github.com/openshift/machine-api-operator/commit/6967e241b653911029a308c75cb6297056924b4c.
Verified in virtual baremetal disconnected setup with IPv6 provisioning, and IPv6 baremetal network:
[kni@provisionhost-0-0 ~]$ oc explain bmh
BareMetalHost is the Schema for the baremetalhosts API
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:
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:
Standard object's metadata. More info:
BareMetalHostSpec defines the desired state of BareMetalHost
BareMetalHostStatus defines the observed state of BareMetalHost
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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.