Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1816624

Summary:	Missing openapi CRD definitions for oc explain to work for MHC
Product:	OpenShift Container Platform	Reporter:	Alberto <agarcial>
Component:	Cloud Compute	Assignee:	Alberto <agarcial>
Cloud Compute sub component:	BareMetal Provider	QA Contact:	Milind Yadav <miyadav>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	unspecified	CC:	agarcial, ccoleman, jhou, maszulik, miyadav, sople, stbenjam
Version:	4.3.0
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1769004
Clones:	1823692 (view as bug list)		Environment:
Last Closed:	2020-08-27 22:34:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1769004, 1820474, 1823692, 1823693, 1823715, 1823717

Description Alberto 2020-03-24 11:57:56 UTC

+++ This bug was initially created as a clone of Bug #1769004 +++

The following PR https://github.com/openshift/origin/pull/22696 introduced an e2e which is verifying that all the operators provide descriptive information as part of their schema which is then available through oc explain command. 
This was recently updated and brought back in https://github.com/openshift/origin/pull/24058. 

Your component has a few missing bits, see the commented out lines from the PR.

This should be fixed similarly to https://github.com/openshift/cluster-kube-controller-manager-operator/pull/302, 
iow. it should be using openshift/api's generated CRD yamls. 

Once done update origin's e2e test and uncomment the lines from your components.

--- Additional comment from Alberto on 2020-01-23 10:07:36 UTC ---



--- Additional comment from Alberto on 2020-03-04 15:13:55 UTC ---

Comment 3 Milind Yadav 2020-03-27 08:21:17 UTC

Verified on :


[miyadav@miyadav ManualRun]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.5.0-0.nightly-2020-03-26-211208   True        False         5h23m   Cluster version is 4.5.0-0.nightly-2020-03-26-211208

[miyadav@miyadav ManualRun]$ oc explain machineset
KIND:     MachineSet
VERSION:  machine.openshift.io/v1beta1

DESCRIPTION:
     <empty>
[miyadav@miyadav ManualRun]$ oc explain mhc
KIND:     MachineHealthCheck
VERSION:  machine.openshift.io/v1beta1

DESCRIPTION:
     MachineHealthCheck is the Schema for the machinehealthchecks API

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>
     Specification of machine health check policy

   status	<Object>
     Most recently observed status of MachineHealthCheck resource

Comment 4 Alberto 2020-04-14 10:16:57 UTC

*** Bug 1823692 has been marked as a duplicate of this bug. ***

Comment 5 Luke Meyer 2020-08-27 22:34:44 UTC

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-2020:2409'