Bug 1812748
| Summary: | Cluster operator image-registry can't create when launch a IPI on Azure | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | wang lin <lwan> | |
| Component: | Image Registry | Assignee: | Oleg Bulatov <obulatov> | |
| Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.5 | CC: | aos-bugs, erich, jialiu, lwan, mlacours, sbatsche | |
| Target Milestone: | --- | Keywords: | TestBlocker | |
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1823590 (view as bug list) | Environment: | ||
| Last Closed: | 2020-08-04 18:04:46 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: | 1823590 | |||
|
Description
wang lin
2020-03-12 03:52:32 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: It has fixed on payload: 4.5.0-0.nightly-2020-03-13-031038 This bug exists in 4.4 and is causing at least failure in `e2e-azure-compact-4.4`[1]. [1]https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-azure-compact-4.4/81/artifacts/e2e-azure/pods/openshift-image-registry_cluster-image-registry-operator-647ff67658-b2v8d_cluster-image-registry-operator.log 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. The fix for 4.3 is bug 1836753 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 |