swift3 and s3token middlewares were not set in correct order in
/etc/swift/proxy-server.conf when the swift3 service is enabled
with keystone. swift3 must be set before s3token.
Fixes: bug #1166123
Change-Id: I97c051af95cbdc26ccfe9753c5719394e1875dde
| ... | ... |
@@ -169,7 +169,7 @@ function configure_swift() {
|
| 169 | 169 |
# configured keystone it will configure swift with it. |
| 170 | 170 |
if is_service_enabled key;then |
| 171 | 171 |
if is_service_enabled swift3;then |
| 172 |
- swift_pipeline=" s3token swift3 " |
|
| 172 |
+ swift_pipeline=" swift3 s3token " |
|
| 173 | 173 |
fi |
| 174 | 174 |
swift_pipeline+=" authtoken keystoneauth " |
| 175 | 175 |
else |