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

Bug 1641794

Summary: "Deploy an Internal Registry" instruction seems unneeded or possibly dangerous
Product: OpenShift Container Platform Reporter: Thomas Cameron <tcameron>
Component: DocumentationAssignee: Michael Burke <mburke>
Status: CLOSED DUPLICATE QA Contact: Xiaoli Tian <xtian>
Severity: unspecified Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, jokerman, mburke, mmccomas
Target Milestone: ---   
Target Release: ---   
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: 2022-01-07 21:00:21 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:

Description Thomas Cameron 2018-10-22 19:07:49 UTC 
Document URL: 

https://access.redhat.com/documentation/en-us/openshift_container_platform/3.11/html/getting_started/getting-started-configure-openshift#deploy-internal-registry

Section Number and Name: 

3.5. Deploy an Internal Registry

Describe the issue: 

The docs tell users to delete the registry that the installer created, and then create a new one. I can't figure out why. I did it, and it caused numerous problems with SSL certificates. I talked to a couple of folks on the OpenShift team, and no one can tell me why the docs say this.

Suggestions for improvement: 

If we leave this in, we should explain why we're recommending it. 

More likely, I think we should take this out, or make it conditional: "if you experience [problem], then you can delete and rebuild the registry with these steps." I am not sure what [problem] actually is, though.

Maybe docs can follow up with engineering to check what was meant in this section?

Additional information: 

I could be totally wrong. Maybe the registry created by the installer is busted and should be replaced. But for me, at least, I wound up having a ton of problems doing this.
Comment 1 Michael Burke 2022-01-07 21:00:21 UTC 

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