Bug 2083466

Summary:	Failed to create clusters on AWS C2S/SC2S due to image-registry MissingEndpoint error
Product:	OpenShift Container Platform	Reporter:	Yunfei Jiang <yunjiang>
Component:	Image Registry	Assignee:	Oleg Bulatov <obulatov>
Status:	CLOSED ERRATA	QA Contact:	XiuJuan Wang <xiuwang>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.11	CC:	yunjiang
Target Milestone:	---	Keywords:	TestBlocker
Target Release:	4.11.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:	2022-08-10 11:11:01 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:
Bug Blocks:	2115267

Description Yunfei Jiang 2022-05-10 07:28:22 UTC

Try to install cluster on C2S/SC2S regions, image-registry operator degraded with error:

> oc get co
NAME                                       VERSION                              AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
image-registry                                                                  False       True          True       74m     Available: The deployment does not exist...

> oc get co image-registry -oyaml

status:
  conditions:
  - lastTransitionTime: "2022-05-10T05:51:52Z"
    message: |-
      Available: The deployment does not exist
      NodeCADaemonAvailable: The daemon set node-ca has available replicas
      ImagePrunerAvailable: Pruner CronJob has been created
    reason: DeploymentNotFound
    status: "False"
    type: Available
  - lastTransitionTime: "2022-05-10T05:51:52Z"
    message: 'Progressing: Unable to apply resources: unable to sync storage configuration:
      MissingEndpoint: ''Endpoint'' configuration is required for this service'
    reason: Error
    status: "True"
    type: Progressing
  - lastTransitionTime: "2022-05-10T05:53:10Z"
    message: 'Degraded: The deployment does not exist'
    reason: Unavailable
    status: "True"
    type: Degraded

Version-Release number of the following components: 
4.11.0-0.nightly-2022-05-09-224745

How reproducible: 
always 

Steps to Reproduce: 
1. Create a cluster on C2S or SC2S regions

Comment 1 Yunfei Jiang 2022-05-10 07:29:35 UTC

this issue blocks all tests on AWS C2S/SC2S regions.

Comment 4 Oleg Bulatov 2022-06-02 13:59:47 UTC

us-iso-east-1 doesn't have a dualstack endpoint for S3, so the operator fails on this region.

Workaround: explicitly provide s3 endpoint https://s3.us-iso-east-1.c2s.ic.gov

Comment 6 XiuJuan Wang 2022-06-13 06:26:16 UTC

Since there is no accpeted 4.11 nightly build, the bug can't move to verified automaticlly, so move this bug to verified manually. Have test this bug before pr merged

Comment 8 errata-xmlrpc 2022-08-10 11:11:01 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069