Bug 1836750
| Summary: | Cluster operator image-registry can't create when launch a IPI on Azure | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Wenjing Zheng <wzheng> |
| Component: | Image Registry | Assignee: | Oleg Bulatov <obulatov> |
| Status: | CLOSED DUPLICATE | QA Contact: | Wenjing Zheng <wzheng> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.3.z | CC: | aos-bugs |
| Target Milestone: | --- | ||
| Target Release: | 4.3.z | ||
| 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: | 2020-05-18 04:06:30 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Wenjing Zheng
2020-05-18 04:02:13 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: *** This bug has been marked as a duplicate of bug 1836753 *** |