-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
swift container ACL set failing #24
Comments
This does not occur with the local test: heather@mitaka: |
I get a different error, but it also fails for me:
|
And a different error again when run against Rackspace:
|
This one looks more similar to the one I got for this bug. Is there a rackspace utility to do the equivalent of a “swift stat” on the container listed, look at the ACL info? In my case, the containers were left behind. -Heather On Oct 4, 2016, at 6:55 PM, Andrew Wilkins <[email protected]mailto:[email protected]> wrote: And a different error again when run against Rackspace: ... value _errors.gooseError = &errors.gooseError{error:(_errors.errorString)(0xc420397770), errcode:"Unspecified", cause:(*errors.gooseError)(0xc420305590)} ("failed to list contents of container: test_container6d85582b6e650244\ncaused by: Unauthorised URL https://storage101.syd2.clouddrive.com/v1/MossoCloudFS_945896/test_container6d85582b6e650244?delimiter=&format=json&marker=&prefix=\ncaused by: request (https://storage101.syd2.clouddrive.com/v1/MossoCloudFS_945896/test_container6d85582b6e650244?delimiter=&format=json&marker=&prefix=) returned unexpected status: 401; error info: UnauthorizedThis server could not verify that you are authorized to access the document you requested. ")— |
rackspace is an openstack, so the swift CLI works. In my case, I get:
|
Running the swift live test produces from TestPublicList(). The contents can't be listed, the container has no ACL settings to allow this. Ran with both admin and user credentials for OpenStack (Mitaka).
I noticed this behavior on the command line for OpenStack previously also. If you set the ACLs for a container after creation, they are ignored. But if you sent the ACLs while creating the container it works.
heather@mitaka:
/work/src/gopkg.in/goose.v1/swift$ env | grep OS_/work/src/gopkg.in/goose.v1/swift$ go test -check.v -live ./... > results-live.out 2>&1OS_REGION_NAME=RegionOne
OS_PASSWORD=openstack
OS_AUTH_URL=http://10.172.45.216:5000/v2.0
OS_USERNAME=admin
OS_TENANT_NAME=admin
heather@mitaka:
FAIL: live_test.go:195: LiveTestsPublicContainer.TestPublicList
live_test.go:206:
c.Check(err, gc.IsNil)
... value _errors.gooseError = &errors.gooseError{error:(_errors.errorString)(0xc8201a9610), errcode:"Unspecified", cause:(*errors.gooseError)(0xc8201e46c0)} ("failed to list contents of container: test_containerd06997de54da7083\ncaused by: Unauthorised URL http://10.172.45.99:80/swift/v1/test_containerd06997de54da7083?delimiter=&format=json&marker=&prefix=\ncaused by: request (http://10.172.45.99:80/swift/v1/test_containerd06997de54da7083?delimiter=&format=json&marker=&prefix=) returned unexpected status: 401; error info: {"Code":"AccessDenied","BucketName":"test_containerd06997de54da7083","RequestId":"tx0000000000000000000c9-0057f3a77b-1081-default","HostId":"1081-default-default"}")
live_test.go:207:
c.Check(len(items), gc.Equals, len(files))
... obtained int = 0
... expected int = 2
heather@mitaka:
$ source novarc$ swift stat test_containerd06997de54da7083heather@mitaka:
Account: v1
Container: test_containerd06997de54da7083
Objects: 1
Bytes: 15
Read ACL:
Write ACL:
Sync To:
Sync Key:
Accept-Ranges: bytes
X-Storage-Policy: default-placement
X-Container-Bytes-Used-Actual: 4096
X-Timestamp: 0.00000
X-Trans-Id: tx0000000000000000000dd-0057f3b015-1081-default
Content-Type: text/plain; charset=utf-8
heather@mitaka:
$ swift list test_containerd06997de54da7083$ source heatherrctest_obj2
heather@mitaka:
heather@mitaka:~$ swift list test_containerd06997de54da7083
Container GET failed: http://10.172.45.99:80/swift/v1/test_containerd06997de54da7083?format=json 401 Unauthorized [first 60 chars of response] {"Code":"AccessDenied","RequestId":"tx0000000000000000000e1-
The text was updated successfully, but these errors were encountered: