Bug 1716427 - vSphere UPI: document that patching the storage registry backend for image registry may fail early into installation
Summary: vSphere UPI: document that patching the storage registry backend for image re...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Kathryn Alexander
QA Contact: Johnny Liu
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-03 13:34 UTC by Matthew Staebler
Modified: 2019-06-11 18:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-11 18:23:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matthew Staebler 2019-06-03 13:34:39 UTC
Document URL: https://docs.openshift.com/container-platform/4.1/installing/installing_vsphere/installing-vsphere.html#installation-registry-storage-non-production_installing-vsphere

Describe the issue: Patching the storage backend for the image registry may fail during the early stages of the installation since the applicable resource is not available until the image-registry operator creates it. The vSphere UPI documentation should recommend to the user to re-attempt the patch if it fails with the following error.

> Error from server (NotFound): configs.imageregistry.operator.openshift.io "cluster" not found

Comment 1 Kathryn Alexander 2019-06-03 15:49:13 UTC
We're frozen for new issues for GA, but I'll push the PR forward after we freeze: https://github.com/openshift/openshift-docs/pull/15119

Comment 2 Kathryn Alexander 2019-06-04 17:43:18 UTC
Jianlin, will you PTAL at https://github.com/openshift/openshift-docs/pull/15119?

Comment 3 Johnny Liu 2019-06-06 01:35:04 UTC
LGTM.

Comment 4 Kathryn Alexander 2019-06-06 12:50:24 UTC
Thanks! I've merged the change and am waiting for it to go live.


Note You need to log in before you can comment on or make changes to this bug.