I think you're hitting issue #8587 (http://tracker.ceph.com/issues/8587). This issue has been fixed at 0.80.8, so you might want to upgrade to that version (available with ICE 1.2.3). Yehuda ----- Original Message ----- > From: "alistair whittle" <alistair.whittle@xxxxxxxxxxxx> > To: yehuda@xxxxxxxxxx > Cc: ceph-users@xxxxxxxxxxxxxx > Sent: Thursday, April 23, 2015 10:47:28 AM > Subject: Re: Swift and Ceph > > Can you explain this a bit more? You mean try and create a second subuser > for testuser1 or testuser2? > > As an aside, I am running Ceph 0.80.7 as is packaged with ICE 1.2.2. I > believe that is the Firefly release. > > > -----Original Message----- > From: Yehuda Sadeh-Weinraub [mailto:yehuda@xxxxxxxxxx] > Sent: Thursday, April 23, 2015 6:18 PM > To: Whittle, Alistair: Investment Bank (LDN) > Cc: ceph-users@xxxxxxxxxxxxxx > Subject: Re: Swift and Ceph > > Sounds like you're hitting a known issue that was fixed a while back > (although might not be fixed on the specific version you're running). Can > you try creating a second subuser for the same user, see if that one works? > > Yehuda > > ----- Original Message ----- > > From: "alistair whittle" <alistair.whittle@xxxxxxxxxxxx> > > To: ceph-users@xxxxxxxxxxxxxx > > Sent: Thursday, April 23, 2015 8:38:44 AM > > Subject: Swift and Ceph > > > > > > > > All, > > > > > > > > I was hoping for some advice. I have recently built a Ceph cluster on > > RHEL > > 6.5 and have configured RGW. I want to test Swift API access, and as a > > result have created a user, swift subuser and swift keys as per the > > output > > below: > > > > > > > > 1. Create user > > > > > > > > radosgw-admin user create --uid="testuser1" --display-name="Test User1" > > > > { "user_id": "testuser1", > > > > "display_name": "Test User1", > > > > "email": "", > > > > "suspended": 0, > > > > "max_buckets": 1000, > > > > "auid": 0, > > > > "subusers": [], > > > > "keys": [ > > > > { "user": "testuser1", > > > > "access_key": "MJBEZLJ7BYG8XODXT71V", > > > > "secret_key": "tGnsm8JeEgPGAy1MGCKSVVoSIEs8iWNUOgiJ981p"}], > > > > "swift_keys": [], > > > > "caps": [], > > > > "op_mask": "read, write, delete", > > > > "default_placement": "", > > > > "placement_tags": [], > > > > "bucket_quota": { "enabled": false, > > > > "max_size_kb": -1, > > > > "max_objects": -1}, > > > > "user_quota": { "enabled": false, > > > > "max_size_kb": -1, > > > > "max_objects": -1}, > > > > "temp_url_keys": []} > > > > > > > > 2. Create subuser. > > > > > > > > radosgw-admin subuser create --uid=testuser1 --subuser=testuser1:swift > > --access=full > > > > { "user_id": "testuser1", > > > > "display_name": "Test User1", > > > > "email": "", > > > > "suspended": 0, > > > > "max_buckets": 1000, > > > > "auid": 0, > > > > "subusers": [ > > > > { "id": "testuser1:swift", > > > > "permissions": "full-control"}], > > > > "keys": [ > > > > { "user": "testuser1:swift", > > > > "access_key": "HX9Q30EJWCZG825AT7B0", > > > > "secret_key": ""}, > > > > { "user": "testuser1", > > > > "access_key": "MJBEZLJ7BYG8XODXT71V", > > > > "secret_key": "tGnsm8JeEgPGAy1MGCKSVVoSIEs8iWNUOgiJ981p"}], > > > > "swift_keys": [], > > > > "caps": [], > > > > "op_mask": "read, write, delete", > > > > "default_placement": "", > > > > "placement_tags": [], > > > > "bucket_quota": { "enabled": false, > > > > "max_size_kb": -1, > > > > "max_objects": -1}, > > > > "user_quota": { "enabled": false, > > > > "max_size_kb": -1, > > > > "max_objects": -1}, > > > > "temp_url_keys": []} > > > > > > > > 3. Create key > > > > > > > > radosgw-admin key create --subuser=testuser1:swift --key-type=swift > > --gen-secret > > > > { "user_id": "testuser1", > > > > "display_name": "Test User1", > > > > "email": "", > > > > "suspended": 0, > > > > "max_buckets": 1000, > > > > "auid": 0, > > > > "subusers": [ > > > > { "id": "testuser1:swift", > > > > "permissions": "full-control"}], > > > > "keys": [ > > > > { "user": "testuser1:swift", > > > > "access_key": "HX9Q30EJWCZG825AT7B0", > > > > "secret_key": ""}, > > > > { "user": "testuser1", > > > > "access_key": "MJBEZLJ7BYG8XODXT71V", > > > > "secret_key": "tGnsm8JeEgPGAy1MGCKSVVoSIEs8iWNUOgiJ981p"}], > > > > "swift_keys": [ > > > > { "user": "testuser1:swift", > > > > "secret_key": "KpQCfPLstJhSMsR9qUzY9WfA1ebO4x7VRXkr1KSf"}], > > > > "caps": [], > > > > "op_mask": "read, write, delete", > > > > "default_placement": "", > > > > "placement_tags": [], > > > > "bucket_quota": { "enabled": false, > > > > "max_size_kb": -1, > > > > "max_objects": -1}, > > > > "user_quota": { "enabled": false, > > > > "max_size_kb": -1, > > > > "max_objects": -1}, > > > > "temp_url_keys": []} > > > > > > > > When I try and do anything using the credentials above, I get “Account > > not found” errors as per the example below: > > > > > > > > swift -A https://<FQDN>/auth/1.0 -U testuser1:swift -K > > "KpQCfPLstJhSMsR9qUzY9WfA1ebO4x7VRXkr1KSf" list > > > > > > > > That’s the first thing. > > > > > > > > Secondly, when I follow the process above to create a second user > > “testuser2”, the user and subuser is created, however, when I try and > > generate a swift key for it, I get the following error: > > > > > > > > radosgw-admin key create --subuser=testuser2:swift --key-type=swift > > --gen-secret > > > > could not create key: unable to add access key, unable to store user > > info > > > > 2015-04-23 15:42:38.897090 7f38e157d820 0 WARNING: can't store user > > info, swift id () already mapped to another user (testuser2) > > > > > > > > This suggests there is something wrong with the users or the > > configuration of the gateway somewhere. Can someone provide some > > advice on what might be wrong, or where I can look to find out. I have > > gone through whatever log files I can and don’t see anything of any use at > > the moment. > > > > > > > > Any help appreciated. > > > > > > > > Thanks > > > > > > > > Alistair > > > > > > _______________________________________________ > > > > This message is for information purposes only, it is not a > > recommendation, advice, offer or solicitation to buy or sell a product > > or service nor an official confirmation of any transaction. It is > > directed at persons who are professionals and is not intended for > > retail customer use. Intended for recipient only. This message is subject > > to the terms at: > > www.barclays.com/emaildisclaimer . > > > > For important disclosures, please see: > > www.barclays.com/salesandtradingdisclaimer regarding market commentary > > from Barclays Sales and/or Trading, who are active market > > participants; and in respect of Barclays Research, including > > disclosures relating to specific issuers, please see > > http://publicresearch.barclays.com . > > > > _______________________________________________ > > > > _______________________________________________ > > ceph-users mailing list > > ceph-users@xxxxxxxxxxxxxx > > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > > > _______________________________________________ > > This message is for information purposes only, it is not a recommendation, > advice, offer or solicitation to buy or sell a product or service nor an > official confirmation of any transaction. It is directed at persons who are > professionals and is not intended for retail customer use. Intended for > recipient only. This message is subject to the terms at: > www.barclays.com/emaildisclaimer. > > For important disclosures, please see: > www.barclays.com/salesandtradingdisclaimer regarding market commentary from > Barclays Sales and/or Trading, who are active market participants; and in > respect of Barclays Research, including disclosures relating to specific > issuers, please see http://publicresearch.barclays.com. > > _______________________________________________ > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |