conflicting settings for s3 tests

Bug #2065366 reported by Kottur
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
New
Undecided
Unassigned

Bug Description

Test configuration requires s3_acl to be set to True in proxy server, but in https://github.com/openstack/swift/blob/master/test/cors/README.rst requires s3_acl = false for s3 tests.

This totally conflicts for s3_acl.

https://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L568
Also, allow_no_owner = False for s3 compatibility, but then says, if s3_acl is True, then this allow_no_owner need to be set to true.

What is it actually?

# s3api requires the same account with the primary one and different users
# one swift owner:
s3_access_key2 = test:tester2
s3_secret_key2 = testing2
# one unprivileged:
s3_access_key3 = test:tester3
s3_secret_key3 = testing

That is not what the comment says. What account users need to be set. Please, ec2-credentials and not tempauth. tempauth is for home lab.

Kottur (skottur)
description: updated
Kottur (skottur)
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.