Description of problem: Customer contributed API for swift (OpenStack) storage backend. For GA API freeze, this needs to either be: a) removed b) marked "Experimental" Version-Release number of selected component (if applicable): 4.0.0-0.ci-2019-04-16-154201 Additional info: https://github.com/openshift/cluster-image-registry-operator/pull/257
PR has merged. We are introducing experimental support for Swift and EmptyDir storage (latter is for non-production use only).
@adam, I can prove emmtyDir is changed like "oc patch configs.imageregistry.operator.openshift.io cluster -p '{"spec":{"emptyDir":{}}}' --type='merge', what else needs to be checked to verify this bug?
@Wenjing you could test a similar patch - `oc patch configs.imageregistry.operator.openshift.io/cluster -p '{"spec":{"storage":{"swift":{}}}}' --type='merge'`. Note that with this patch storage the registry itself may not come up because that storage config won't connect to a swift backend.
(In reply to Adam Kaplan from comment #4) > @Wenjing you could test a similar patch - `oc patch > configs.imageregistry.operator.openshift.io/cluster -p > '{"spec":{"storage":{"swift":{}}}}' --type='merge'`. > > Note that with this patch storage the registry itself may not come up > because that storage config won't connect to a swift backend. Operator rollback my config to s3 if I test on AWS when I set storage to swift, is it on purpose?
No, it's not. https://github.com/openshift/cluster-image-registry-operator/pull/262
@Wenjing Oleg's PR merged with his fix
Thanks, Oleg and Adam! I can verify with 4.1.0-0.nightly-2019-04-28-064010 now: $ oc get pods NAME READY STATUS RESTARTS AGE cluster-image-registry-operator-75c9b4f765-kzj6m 1/1 Running 0 103m image-registry-5ddfc9786c-mfckl 0/1 CreateContainerConfigError 0 2m40s Normal Pulled 3s (x4 over 15s) kubelet, ip-172-31-140-51.eu-west-2.compute.internal Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:5f053184bb80722d9d23686526dc18b05b53e7b02e12cf57118028895aefcc4b" already present on machine Warning Failed 3s (x4 over 15s) kubelet, ip-172-31-140-51.eu-west-2.compute.internal Error: Couldn't find key REGISTRY_STORAGE_SWIFT_USERNAME in Secret openshift-image-registry/image-registry-private-configuration
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-2019:0758