Bug 1812748 - Cluster operator image-registry can't create when launch a IPI on Azure
Summary: Cluster operator image-registry can't create when launch a IPI on Azure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.5.0
Assignee: Oleg Bulatov
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks: 1823590
TreeView+ depends on / blocked
 
Reported: 2020-03-12 03:52 UTC by wang lin
Modified: 2020-08-04 18:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Cause: empty Azure container name is not omitted from the config object Consequence: when this object was sent to the api server, it was rejected because of validation Fix: omit empty fields Result: the operator can bootstrap the config object
Clone Of:
: 1823590 (view as bug list)
Environment:
Last Closed: 2020-08-04 18:04:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-08-04 18:04:49 UTC

Description wang lin 2020-03-12 03:52:32 UTC
Description of problem:
Cluster operator image-registry can't create successful


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 wang lin 2020-03-12 04:27:53 UTC
Description of problem:
Cluster operator image-registry can't be created when launch a IPI on Azure.


Version-Release number of selected component (if applicable):
4.5.0-0.nightly-2020-03-10-211937


How reproducible:
Always

Steps to Reproduce:
1.Lanuch a IPI on Azure
$./openshift create cluster --log-level debug(platform selects Azure)
2.Observe process of installation
Installation finished with image-registry error
3.login to cluster,and check logs of cluster-image-registry-operator pod
$oc logs deployment/cluster-image-registry-operator -c cluster-image-registry-operator


Actual results:
$oc logs deployment/cluster-image-registry-operator -c cluster-image-registry-operator
.....
E0312 03:17:18.609395      13 clusteroperator.go:95] unable to sync ClusterOperatorStatusController: config.imageregistry.operator.openshift.io "cluster" not found, requeuing
E0312 03:17:20.640480      13 controllerimagepruner.go:260] (imaeg pruner) unable to sync: unable to apply objects: failed to create object *v1beta1.CronJob, Namespace=openshift-image-registry, Name=image-pruner: config.imageregistry.operator.openshift.io "cluster" not found, requeuing
I0312 03:17:21.208549      13 bootstrap.go:47] generating registry custom resource
E0312 03:17:21.216806      13 controller.go:250] unable to sync: Config.imageregistry.operator.openshift.io "cluster" is invalid: spec.storage.azure.container: Invalid value: "": spec.storage.azure.container in body should be at least 3 chars long, requeuing



Expected results:
Cluster operator image-registry can be created successfully

Additional info:

Comment 4 wang lin 2020-03-13 08:13:11 UTC
It has fixed on payload: 4.5.0-0.nightly-2020-03-13-031038

Comment 7 Michael LaCourse 2020-06-02 19:23:45 UTC
We experienced the same error using 4.3.22 Installer.  We reverted installer to 4.3.19 and the install worked.

Seems this needs to be back ported in 4.3 also.

Comment 8 Oleg Bulatov 2020-06-05 15:54:46 UTC
The fix for 4.3 is bug 1836753

Comment 10 errata-xmlrpc 2020-08-04 18:04:46 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 (OpenShift Container Platform 4.5 image release 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:2409


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