Bug 1784208
| Summary: | operator uses virtual hosted bucket addressing for custom region endpoints | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Oleg Bulatov <obulatov> | |
| Component: | Image Registry | Assignee: | Oleg Bulatov <obulatov> | |
| Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.1.z | CC: | adam.kaplan, aos-bugs, dahernan, hgomes, wewang, wzheng | |
| Target Milestone: | --- | |||
| Target Release: | 4.4.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: the operator always uses virtual hosted style addressing for S3 even if a custom region endpoint is provided
Consequence: it's not compatible with the registry that uses path style addressing for custom endpoints
Fix: when a custom endpoint is provided, use path style addressing
Result: the operator access the S3-compatible storage that same way as the registry does
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1815124 (view as bug list) | Environment: | ||
| Last Closed: | 2020-05-04 11:20:19 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1815124 | |||
|
Description
Oleg Bulatov
2019-12-16 23:41:46 UTC
But if use http://<bucketname>.<regionEndpoint>/<key>,UnmarshalError appears, so report a bug as below: https://bugzilla.redhat.com/show_bug.cgi?id=1797512 Re-verify on 4.4.0-0.nightly-2020-03-29-132004:
storage:
s3:
bucket: wzheng-44bug-bcwqr-image-registry-us-east-2-yfjbspjvnpcuouygwi
encrypt: true
keyID: ""
region: us-east-2
regionEndpoint: https://s3.us-east-2.amazonaws.com/
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-2020:0581 |