| Summary: | S3 storage is not configured, but is listed in Keystone endpoints | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Arx Cruz <acruz> |
| Component: | openstack-packstack | Assignee: | Ivan Chavero <ichavero> |
| Status: | CLOSED DUPLICATE | QA Contact: | yeylon <yeylon> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 8.0 (Liberty) | CC: | aortega, apevec, derekh, ichavero, jschluet, lbezdick, mkollaro, mmagr, srevivo, tkammer, yeylon |
| Target Milestone: | --- | Keywords: | Automation, AutomationBlocker, ZStream |
| Target Release: | 8.0 (Liberty) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1138740 | Environment: | |
| Last Closed: | 2016-03-23 00:16:52 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: | |
| Bug Depends On: | 1138740 | ||
| Bug Blocks: | |||
|
Comment 1
Alan Pevec
2016-02-26 19:23:57 UTC
So the issue is that puppet-swift enables this endpoint by default: https://github.com/openstack/puppet-swift/blob/master/manifests/keystone/auth.pp#L165 which is wrong, it should be defined ONLY when swift3 is enabled: https://github.com/openstack/puppet-swift/blob/master/manifests/proxy/swift3.pp Workaround in packstack could be to set explicit configure_s3_endpoint = false This change added s3 endpoints as a part of a bigger change: https://review.openstack.org/#/c/275617/1/packstack/puppet/templates/keystone_swift.pp@5 Lukas, ^ check comment there Added patch that sets configure_s3_endpoint = false https://review.openstack.org/#/c/287002/ 287002 was merged upstream - please backport where required Backported patch https://review.openstack.org/#/c/291048 Looks like this was duplicated and fixed as bug 1317110. *** This bug has been marked as a duplicate of bug 1317110 *** |