swift proxy is configured with keystone v2.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Juan Antonio Osorio Robles |
Bug Description
Originally filed by Rys Oxenham.
Description of problem:
When deploying an overcloud with OSP director/TripleO, it deploys Swift with a configuration to use Keystone v2.0 API. With the initiative to move to v3 for all OpenStack services, this one is not consistent. I've tested Swift with v3 and it works just fine, even disabling v2.0 just to make sure there was nothing hanging around.
Version-Release number of selected component (if applicable):
openstack-
openstack-
openstack-
openstack-
openstack-
python-
openstack-
puppet-
openstack-
How reproducible:
Every time
Steps to Reproduce:
1. Deploy an overcloud with the above package versions
2. Observe that Swift is configured to use v2.0 keystone API
3. Realise that this is inconsistent with the rest of the OpenStack services :)
Actual results:
Deployed using v2.0 Keystone API
Expected results:
Deployed using v3 Keystone API like all other OpenStack services
Additional info:
Before...
[root@overcloud
./swift/
After...
[root@overcloud
auth_uri=http://
auth_version=v3
Changed in tripleo: | |
status: | New → Triaged |
assignee: | nobody → Juan Antonio Osorio Robles (juan-osorio-robles) |
importance: | Undecided → Medium |
milestone: | none → queens-3 |
Changed in tripleo: | |
milestone: | queens-3 → queens-rc1 |
no longer affects: | tripleo/pike |
Fix proposed to branch: master /review. openstack. org/532794
Review: https:/