Swift S3 API Broken In Zed
Bug #2060121 reported by
lakcaj
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
Undecided
|
Sven Kieske | ||
Antelope |
Fix Released
|
Undecided
|
Unassigned | ||
Bobcat |
Fix Released
|
Undecided
|
Unassigned | ||
Caracal |
Fix Released
|
Undecided
|
Sven Kieske | ||
Zed |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
What Happened:
Between Yoga and Zed, the /v3 suffix for the auth_url in the [filter:s3token] section was removed:
With debug logging enabled, Keystone returns a 404 when Swift queries for credentials, and the S3 API completely breaks.
Re-adding the /v3 suffix has been confirmed to fix the S3 API in two separate test deployments.
What I Expect To Happen: The Swift S3 API working correctly
How To Reproduce: On any Zed deployment, enable the Swift S3 API, add ec2 credentials, and attempt to use the S3 API through any type of client (Ansible, awscli, mc, etc)
Changed in kolla-ansible: | |
assignee: | nobody → Sven Kieske (s-kieske) |
no longer affects: | kolla-ansible/yoga |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/c/openstack /kolla- ansible/ +/914965
Review: https:/