Activity log for bug #2065366

Date Who What changed Old value New value Message
2024-05-10 06:12:02 Kottur bug added bug
2024-05-10 15:32:04 Kottur 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 s3_acl is set, then this allow_no_owner makes sense (to be set to true). What is it actually? 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?
2024-05-10 18:46:28 Kottur 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? 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.