| Summary: | [4.4] image registry operator keeps creating new storage accounts on Azure | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ricardo Maraschini <rmarasch> | |
| Component: | Image Registry | Assignee: | Ricardo Maraschini <rmarasch> | |
| Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.3.z | CC: | aos-bugs, jminter, obulatov, rmarasch, scuppett, wzheng | |
| Target Milestone: | --- | |||
| Target Release: | 4.4.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause:
Having an azure infrastructure name containing uppercase letters.
Consequence:
Azure containers and storage accounts are named using infrastructure name, in some circumstances the auto generated name (containing the infrastructure name) would be valid for a storage account but not for a container, making the operator to create the first but fail on the latter and forcing a retry.
Fix:
Adjusted the container name creation logic to discard invalid characters.
Result:
Image registry is correctly deployed on an infrastructure that contain invalid characters on its name.
|
Story Points: | --- | |
| Clone Of: | 1827807 | |||
| : | 1832144 (view as bug list) | Environment: | ||
| Last Closed: | 2020-06-17 22:26:05 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Bug Depends On: | 1827807 | |||
| Bug Blocks: | 1832144 | |||
|
Comment 2
Ricardo Maraschini
2020-05-29 08:03:17 UTC
Verified on 4.4.0-0.nightly-2020-06-03-225439: # configs.imageregistry.operator.openshift.io "cluster" was not valid: # * spec.storage.azure.container: Invalid value: "": spec.storage.azure.container in body should match '^[0-9a-z]+(-[0-9a-z]+)*$' 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:2445 |