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

Bug 1734402

Summary: oc explain does not work with imageregistry samples
Product: OpenShift Container Platform Reporter: Eric Rich <erich>
Component: ImageStreamsAssignee: Gabe Montero <gmontero>
Status: CLOSED DUPLICATE QA Contact: XiuJuan Wang <xiuwang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.1.zCC: aos-bugs, jokerman, mfojtik, nmukherj, tnozicka, wzheng
Target Milestone: ---Flags: erich: needinfo-
Target Release: 4.2.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: 2019-08-19 18:44:55 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: 1705753, 1743376    
Bug Blocks:    

Description Eric Rich 2019-07-30 12:50:37 UTC
Description of problem:

> $ oc explain config.samples.operator.openshift.io
> KIND:     Config
> VERSION:  imageregistry.operator.openshift.io/v1
> DESCRIPTION:
>      <empty>

Version-Release number of selected component (if applicable): 4.1.7
How reproducible: 100%

Expected results: This should show me the details about what fields we can be put into the config. 

Additional info:

Comment 1 Maciej Szulik 2019-08-07 13:18:40 UTC
Sending this over to Image Registry folks since they own the CRD and that's where the information for oc explain come from.

Comment 2 Oleg Bulatov 2019-08-19 13:51:10 UTC
Apparently the proper command is `oc explain --api-version=samples.operator.openshift.io/v1 configs` and we should backport the fix from the bug 1705753 to 4.1.z.

The output for the image registry of `oc explain --api-version=imageregistry.operator.openshift.io/v1 configs` is covered by the bug 1714775.

Comment 3 Gabe Montero 2019-08-19 14:05:31 UTC
@Eric - to facilitate our 4.1.z update process, it is is required that the bug targeted to 4.1.z has a clone relationship with the 4.2 bug.  The bot in fact verifies that the 4.2 bug has been verified 
before accepting the cherry-pick.

Can you close this out and clone https://bugzilla.redhat.com/show_bug.cgi?id=1705753 to 4.1, or do you need me to do it?

Comment 4 Gabe Montero 2019-08-19 18:44:55 UTC

*** This bug has been marked as a duplicate of bug 1743376 ***