Bug 1803970

Summary:	Image registry failing to start on baremetal IPI
Product:	OpenShift Container Platform	Reporter:	Stephen Benjamin <stbenjam>
Component:	Image Registry	Assignee:	Ricardo Maraschini <rmarasch>
Status:	CLOSED ERRATA	QA Contact:	Wenjing Zheng <wzheng>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, augol, obulatov, rbartal, rmarasch, ukalifon
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-13 21:58: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 Stephen Benjamin 2020-02-17 20:54:24 UTC

Description of problem:

Registry is not available on baremetal IPI.  The installer is stuck waiting on image-registry:

> level=info msg="Waiting up to 1h0m0s for the cluster at https://api.ostest.test.metalkube.org:6443 to initialize..."
> level=debug msg="Still waiting for the cluster to initialize: Cluster operator > image-registry has not yet reported success"
> level=debug msg="Still waiting for the cluster to initialize: Cluster operator > image-registry has not yet reported success"

The logs for image-registry operator say this:

> E0217 20:34:34.936684      12 clusteroperator.go:94] unable to sync ClusterOperatorStatusController: storage backend not configured, requeuing
> E0217 20:34:34.936831      12 controller.go:353] unable to sync: unable to get generators: storage backend not configured, requeuing


Version-Release number of selected component (if applicable):

4.4.0-0.ci-2020-02-17-143917

How reproducible:

Always

Comment 1 Stephen Benjamin 2020-02-17 20:55:28 UTC

There may also be a secondary bug, related to this. If image-registry fails to start, the clusteroperator never gets reported.  `oc get clusteroperators` is not showing image-registry at all.

Comment 4 Udi Kalifon 2020-02-19 07:49:54 UTC

In IPI installations, the registry is initially in "Removed" state. This is by design, until the user sets up persistent storage for it: https://docs.openshift.com/container-platform/4.3/registry/configuring_registry_storage/configuring-registry-storage-baremetal.html

Comment 6 errata-xmlrpc 2020-05-13 21:58:21 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:0581