Bug 1700487
Summary: | [api-freeze] Experimental Support for Swift Storage Backend | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Adam Kaplan <adam.kaplan> |
Component: | Image Registry | Assignee: | Oleg Bulatov <obulatov> |
Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 4.1.0 | CC: | aos-bugs, bparees, pweil |
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:47:40 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Adam Kaplan
2019-04-16 17:31:49 UTC
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? @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 |