Bug 1815649

Summary: Go client for ClusterOperator.config.openshift.io is not generated
Product: OpenShift Container Platform Reporter: Jim Minter <jminter>
Component: OLMAssignee: Nick Hale <nhale>
OLM sub component: OperatorHub QA Contact: Fan Jia <jfan>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: ecordell, nhale, shurley
Version: 4.5   
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: The OperatorHub type definition is missing an additional `+genclient` marker comment required for Kubernetes client generation. Consequence: The generated client is not available in openshift/client-go config client. Fix: Add the missing `+genclient` marker comment to the OperatorHub config type. Result: The generated client is available in the openshift/client-go config client.
Story Points: ---
Clone Of:
: 1815655 (view as bug list) Environment:
Last Closed: 2020-07-13 17:23:29 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:
Bug Depends On: 1816483    
Bug Blocks: 1815655    

Description Jim Minter 2020-03-20 19:53:55 UTC
At https://github.com/openshift/api/blob/master/config/v1/types_operatorhub.go#L39-L41, there is a missing `// +genclient`. As a result no client is built for the ClusterOperator.config.openshift.io resource.  Witness the lack of a operatorhub.go file at https://github.com/openshift/client-go/tree/master/config/clientset/versioned/typed/config/v1 , for example.

Please can this be fixed in master and backported back to 4.3?

Comment 3 Fan Jia 2020-04-10 01:07:37 UTC
There is operatorhub.go in https://github.com/openshift/client-go/tree/master/config/clientset/versioned/typed/config/v1, and all the operatorhub function is ok in cluster.

Comment 5 errata-xmlrpc 2020-07-13 17:23:29 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