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.
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.
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]+)*$'
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.