Bug 1827807 - image registry operator keeps creating new storage accounts on Azure
Summary: image registry operator keeps creating new storage accounts on Azure
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.3.z
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.0
Assignee: Ricardo Maraschini
QA Contact: Wenjing Zheng
Depends On:
Blocks: 1832140
TreeView+ depends on / blocked
Reported: 2020-04-24 20:40 UTC by Jim Minter
Modified: 2020-07-13 17:31 UTC (History)
3 users (show)

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.
Clone Of:
: 1832140 (view as bug list)
Last Closed: 2020-07-13 17:31:30 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Github openshift cluster-image-registry-operator pull 539 None closed Bug 1827807: Assure storage bucket names in lowercase 2020-08-23 09:51:11 UTC
Red Hat Product Errata RHBA-2020:2409 None None None 2020-07-13 17:31:47 UTC

Description Jim Minter 2020-04-24 20:40:30 UTC
On 4.3.13 in Azure (IPI), if the infrastructure ID of the cluster contains capital letters, image registry operator creates a storage account, but then fails to create a storage container inside because it uses the infrastructure ID in the name and Azure does not permit capital letters in the name.

The backoff behaviour is then horrible.  Having failed to create a storage container, it then keeps retrying, creating new storage *accounts* until the end user's storage account quota is exhausted.

An ARO bug caused us to set the infrastructure ID in capital letters.  I don't know if the standard installer or UPI make it feasible to do this -- if so, it would be good to fix the backoff behaviour.

Comment 1 Stephen Cuppett 2020-04-24 20:50:36 UTC
Setting target release to current development version (4.5) for investigation. Where fixes (if any) are required/requested for prior versions, cloned BZs will be created when appropriate.

Comment 5 Wenjing Zheng 2020-05-26 08:07:32 UTC
Image registry not allow capital letter in bucket name now on 4.5.0-0.nightly-2020-05-25-232952: 
# 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]+)*$'

Comment 6 errata-xmlrpc 2020-07-13 17:31:30 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.


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