Description of problem:
GCP should (as Azure driver does) create the bucket provided by user if it does not exist. What is happening is that if user manually provides a bucket name the driver does not create it and the operator remains in Progressing.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Edit the image registry operator config
2. Change the bucket name (spec.storage.gcs.bucket) to a random name
Operator remains in Progressing with the following condition:
$ oc get -o json configs.imageregistry.operator.openshift.io/cluster | jq
"message": "storage: bucket doesn't exist",
"reason": "Unknown Error Occurred",
"message": "Unable to apply resources: unable to sync storage configuration: storage: bucket doesn't exist",
Supplied bucket is created and the container leaves the Progressing.
Verified on 4.6.0-0.nightly-2020-08-25-222652, gcs.bucket can be changed to random one:
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.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.