Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."

[ceph . novice]

Ups... thanks for your efforts, Ben!

 

This could explain some bit's. Still I have lot's of question as it seems different S3 tools/clients behaive different. We need to stick on CyberDuck on Windows and s3cms and boto on Linux and many things are not the same with RadosGW :|

 

And more on my to-test-list ;)

 

Regards

 Anton

 

Gesendet: Mittwoch, 12. April 2017 um 06:49 Uhr
Von: "Ben Hines" 
An: ceph.nov...@habmalnefrage.de
Cc: ceph-users , "Yehuda Sadeh-Weinraub" 
Betreff: Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."


After much banging on this and reading through the Ceph RGW source, i figured out Ceph RadosGW returns -13 ( EACCES - AcessDenied) if you dont pass in a 'Prefix' in your S3 lifecycle configuration setting. It also returns EACCES if the XML is invalid in any way, which is probably not the most correct /  user friendly result.
 

http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTlifecycle.html specifies 'Prefix' as Optional, so i'll put in a bug for this.

 

-Ben

 

 
On Mon, Apr 3, 2017 at 12:14 PM, Ben Hines  wrote:


Interesting.  
I'm wondering what the -13 return code for the op execution in my debug output is (can't find in the source..)

 

 

 

I just tried out setting the lifecycle with cyberduck and got this error, which is probably the other bug with AWSv4 auth, http://tracker.ceph.com/issues/17076   Not sure if cyberduck can be forced to use V2.


 


2017-04-03 12:07:15.093235 7f5617024700 10 op=20RGWPutLC_ObjStore_S3

2017-04-03 12:07:15.093248 7f5617024700  2 req 14:0.000438:s3:PUT /bentest/:put_lifecycle:authorizing


.


2017-04-03 12:07:15.093637 7f5617024700 10 delaying v4 auth

2017-04-03 12:07:15.093643 7f5617024700 10 ERROR: AWS4 completion for this operation NOT IMPLEMENTED

2017-04-03 12:07:15.093652 7f5617024700 10 failed to authorize request

2017-04-03 12:07:15.093658 7f5617024700 20 handler->ERRORHANDLER: err_no=-2201 new_err_no=-2201

2017-04-03 12:07:15.093844 7f5617024700  2 req 14:0.001034:s3:PUT /bentest/:put_lifecycle:op status=0

2017-04-03 12:07:15.093859 7f5617024700  2 req 14:0.001050:s3:PUT /bentest/:put_lifecycle:http status=501

2017-04-03 12:07:15.093884 7f5617024700  1 == req done req=0x7f561701e340 op status=0 http_status=501 ==

 

 


 

-Ben







 
On Mon, Apr 3, 2017 at 7:16 AM,  wrote:





... hmm, "modify" gives no error and may be the option to use, but I don't see anything related to an "expires" meta field

 


[root s3cmd-master]# ./s3cmd --no-ssl --verbose modify s3://Test/INSTALL --expiry-days=365
INFO: Summary: 1 remote files to modify
modify: 's3://Test/INSTALL'


[root s3cmd-master]# ./s3cmd --no-ssl --verbose info s3://Test/INSTALL
s3://Test/INSTALL (object):
   File size: 3123
   Last mod:  Mon, 03 Apr 2017 12:35:28 GMT
   MIME type: text/plain
   Storage:   STANDARD
   MD5 sum:   63834dbb20b32968505c4ebe768fc8c4
   SSE:   none
   policy:    http://s3.amazonaws.com/doc/2006-03-01/">Test1000falseINSTALL2017-04-03T12:35:28.533Z63834dbb20b32968505c4ebe768fc8c43123STANDARD666First UserREADME.TXT2017-03-31T22:36:38.380Z708efc3b9184c8b112e36062804aca1e88STANDARD666First User
   cors:    none
   ACL:   First User: FULL_CONTROL
   x-amz-meta-s3cmd-attrs: atime:1491218263/ctime:1490998096/gid:0/gname:root/md5:63834dbb20b32968505c4ebe768fc8c4/mode:33188/mtime:1488021707/uid:0/uname:root

 


 

Gesendet: Montag, 03. April 2017 um 14:13 Uhr
Von: ceph.nov...@habmalnefrage.de
An: ceph-users 



Betreff: Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."





... additional strange but a bit different info related to the "permission denied"
 
[root s3cmd-master]# ./s3cmd --no-ssl put INSTALL s3://Test/ --expiry-days=5
upload: 'INSTALL' -> 's3://Test/INSTALL' [1 of 1]
3123 of 3123 100% in 0s 225.09 kB/s done

[root s3cmd-master]# ./s3cmd info s3://Test/INSTALL
s3://Test/INSTALL (object):
File size: 3123
Last mod: Mon, 03 Apr 2017 12:01:47 GMT
MIME type: text/plain
Storage: STANDARD
MD5 sum: 63834dbb20b32968505c4ebe768fc8c4
SSE: none
policy: http://s3.amazonaws.com/doc/2006-03-01/">Test1000falseINSTALL2017-04-03T12:01:47.745Z63834dbb20b32968505c4ebe768fc8c43123STANDARD666First UserREADME.TXT2017-03-31T22:36:38.380Z708efc3b9184c8b112e36062804aca1e88STANDARD666First User
cors: none
ACL: First User: FULL_CONTROL
x-amz-meta-s3cmd-attrs: atime:1491218263/ctime:1490998096/gid:0/gname:root/md5:63834dbb20b32968505c4ebe768fc8c4/mode:33188/mtime:1488021707/uid:0/uname:root

[root s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/ --expiry-days=365
ERROR: Access to bucket 'Test' was denied
ERROR: S3 error: 403 (AccessDenied)

[root s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/INSTALL 

Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."

[Ben Hines]

After much banging on this and reading through the Ceph RGW source, i
figured out Ceph RadosGW returns -13 ( EACCES - AcessDenied) if you dont
pass in a 'Prefix' in your S3 lifecycle configuration setting. It also
returns EACCES if the XML is invalid in any way, which is probably not the
most correct /  user friendly result.

http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTlifecycle.html
specifies 'Prefix' as Optional, so i'll put in a bug for this.

-Ben


On Mon, Apr 3, 2017 at 12:14 PM, Ben Hines  wrote:

> Interesting.
> I'm wondering what the -13 return code for the op execution in my debug
> output is (can't find in the source..)
>
>
>
> I just tried out setting the lifecycle with cyberduck and got this error,
> which is probably the other bug with AWSv4 auth, http://tracker.ceph.com/
> issues/17076   Not sure if cyberduck can be forced to use V2.
>
> 2017-04-03 12:07:15.093235 7f5617024700 10 op=20RGWPutLC_ObjStore_S3
> 2017-04-03 12:07:15.093248 7f5617024700  2 req 14:0.000438:s3:PUT
> /bentest/:put_lifecycle:authorizing
> .
> 2017-04-03 12:07:15.093637 7f5617024700 10 delaying v4 auth
> 2017-04-03 12:07:15.093643 7f5617024700 10 ERROR: AWS4 completion for this
> operation NOT IMPLEMENTED
> 2017-04-03 12:07:15.093652 7f5617024700 10 failed to authorize request
> 2017-04-03 12:07:15.093658 7f5617024700 20 handler->ERRORHANDLER:
> err_no=-2201 new_err_no=-2201
> 2017-04-03 12:07:15.093844 7f5617024700  2 req 14:0.001034:s3:PUT
> /bentest/:put_lifecycle:op status=0
> 2017-04-03 12:07:15.093859 7f5617024700  2 req 14:0.001050:s3:PUT
> /bentest/:put_lifecycle:http status=501
> 2017-04-03 12:07:15.093884 7f5617024700  1 == req done
> req=0x7f561701e340 op status=0 http_status=501 ==
>
>
>
> -Ben
>
> On Mon, Apr 3, 2017 at 7:16 AM,  wrote:
>
>> ... hmm, "modify" gives no error and may be the option to use, but I
>> don't see anything related to an "expires" meta field
>>
>> [root s3cmd-master]# ./s3cmd --no-ssl --verbose modify s3://Test/INSTALL
>> --expiry-days=365
>> INFO: Summary: 1 remote files to modify
>> modify: 's3://Test/INSTALL'
>>
>> [root s3cmd-master]# ./s3cmd --no-ssl --verbose info s3://Test/INSTALL
>> s3://Test/INSTALL (object):
>>File size: 3123
>>Last mod:  Mon, 03 Apr 2017 12:35:28 GMT
>>MIME type: text/plain
>>Storage:   STANDARD
>>MD5 sum:   63834dbb20b32968505c4ebe768fc8c4
>>SSE:   none
>>policy:> xmlns="http://s3.amazonaws.com/doc/2006-03-01/;>Test> Name>1000> s>falseINSTALL> Key>2017-04-03T12:35:28.533Z<
>> ETag>63834dbb20b32968505c4ebe768fc8c4> e>3123STANDARD666First
>> UserREADME.T
>> XT2017-03-31T22:36:38.380Z> >708efc3b9184c8b112e36062804aca1e<
>> Size>88STANDARD666First
>> User
>>cors:none
>>ACL:   First User: FULL_CONTROL
>>x-amz-meta-s3cmd-attrs: atime:1491218263/ctime:1490998
>> 096/gid:0/gname:root/md5:63834dbb20b32968505c4ebe768fc8c4/mo
>> de:33188/mtime:1488021707/uid:0/uname:root
>>
>>
>> *Gesendet:* Montag, 03. April 2017 um 14:13 Uhr
>> *Von:* ceph.nov...@habmalnefrage.de
>> *An:* ceph-users 
>>
>> *Betreff:* Re: [ceph-users] Kraken release and RGW --> "S3 bucket
>> lifecycle API has been added. Note that currently it only supports object
>> expiration."
>> ... additional strange but a bit different info related to the
>> "permission denied"
>>
>> [root s3cmd-master]# ./s3cmd --no-ssl put INSTALL s3://Test/
>> --expiry-days=5
>> upload: 'INSTALL' -> 's3://Test/INSTALL' [1 of 1]
>> 3123 of 3123 100% in 0s 225.09 kB/s done
>>
>> [root s3cmd-master]# ./s3cmd info s3://Test/INSTALL
>> s3://Test/INSTALL (object):
>> File size: 3123
>> Last mod: Mon, 03 Apr 2017 12:01:47 GMT
>> MIME type: text/plain
>> Storage: STANDARD
>> MD5 sum: 63834dbb20b32968505c4ebe768fc8c4
>> SSE: none
>> policy: http://s3.amazonaws.com/doc/2006-03-01/;>Test> Name>1000> s>falseINSTALL> Key>2017-04-03T12:01:47.745Z<
>> ETag>63834dbb20b32968505c4ebe768fc8c4> e>3123STANDARD666First
>> UserREADME.T
>> XT2017-03-31T22:36:38.380Z> >708efc3b9184c8b112e36062804aca1e<
>> Size>88STANDARD666First
>> User
>> cors: none
>> ACL: First User: FULL_CONTROL
>> x-amz-meta-s3cmd-attrs: atime:1491218263/ctime:1490998
>> 096/gid:0/gname:root/md5:63834dbb20b32968505c4ebe768fc8c4/mo
>> de:33188/mtime:1488021707/uid:0/uname:root
>>
>> [root s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/ --expiry-days=365
>> ERROR: Access to bucket 'Test' was denied
>> ERROR: S3 error: 403 (AccessDenied)
>>
>> [root s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/INSTALL
>> --expiry-days=365
>> ERROR: Parameter problem: Expecting S3 URI with just the bucket name set
>> instead of 's3://Test/INSTALL'
>> [root@mucsds26 s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/
>> --expiry-days=365
>> ERROR: Access to bucket 'Test' was denied
>> ERROR: S3 error: 403 (AccessDenied)
>>
>> [root s3cmd-master]# ./s3cmd --no-ssl la expire s3://Test
>> 2017-04-03 12:01 3123 s3://Test/INSTALL
>> 

Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."

[Ben Hines]

Interesting.
I'm wondering what the -13 return code for the op execution in my debug
output is (can't find in the source..)



I just tried out setting the lifecycle with cyberduck and got this error,
which is probably the other bug with AWSv4 auth, http://tracker.ceph.com/
issues/17076   Not sure if cyberduck can be forced to use V2.

2017-04-03 12:07:15.093235 7f5617024700 10 op=20RGWPutLC_ObjStore_S3
2017-04-03 12:07:15.093248 7f5617024700  2 req 14:0.000438:s3:PUT
/bentest/:put_lifecycle:authorizing
.
2017-04-03 12:07:15.093637 7f5617024700 10 delaying v4 auth
2017-04-03 12:07:15.093643 7f5617024700 10 ERROR: AWS4 completion for this
operation NOT IMPLEMENTED
2017-04-03 12:07:15.093652 7f5617024700 10 failed to authorize request
2017-04-03 12:07:15.093658 7f5617024700 20 handler->ERRORHANDLER:
err_no=-2201 new_err_no=-2201
2017-04-03 12:07:15.093844 7f5617024700  2 req 14:0.001034:s3:PUT
/bentest/:put_lifecycle:op status=0
2017-04-03 12:07:15.093859 7f5617024700  2 req 14:0.001050:s3:PUT
/bentest/:put_lifecycle:http status=501
2017-04-03 12:07:15.093884 7f5617024700  1 == req done
req=0x7f561701e340 op status=0 http_status=501 ==



-Ben

On Mon, Apr 3, 2017 at 7:16 AM,  wrote:

> ... hmm, "modify" gives no error and may be the option to use, but I don't
> see anything related to an "expires" meta field
>
> [root s3cmd-master]# ./s3cmd --no-ssl --verbose modify s3://Test/INSTALL
> --expiry-days=365
> INFO: Summary: 1 remote files to modify
> modify: 's3://Test/INSTALL'
>
> [root s3cmd-master]# ./s3cmd --no-ssl --verbose info s3://Test/INSTALL
> s3://Test/INSTALL (object):
>File size: 3123
>Last mod:  Mon, 03 Apr 2017 12:35:28 GMT
>MIME type: text/plain
>Storage:   STANDARD
>MD5 sum:   63834dbb20b32968505c4ebe768fc8c4
>SSE:   none
>policy: xmlns="http://s3.amazonaws.com/doc/2006-03-01/;>
> Test1000<
> /MaxKeys>false
> INSTALL2017-04-03T12:35:28.533Z LastModified>63834dbb20b32968505c4ebe768fc8
> c43123STANDARD StorageClass>666First
> User
> README.TXT2017-03-31T22:36:38.380Z LastModified>708efc3b9184c8b112e36062804aca
> 1e88STANDARD StorageClass>666First
> User
>cors:none
>ACL:   First User: FULL_CONTROL
>x-amz-meta-s3cmd-attrs: atime:1491218263/ctime:
> 1490998096/gid:0/gname:root/md5:63834dbb20b32968505c4ebe768fc8
> c4/mode:33188/mtime:1488021707/uid:0/uname:root
>
>
> *Gesendet:* Montag, 03. April 2017 um 14:13 Uhr
> *Von:* ceph.nov...@habmalnefrage.de
> *An:* ceph-users 
>
> *Betreff:* Re: [ceph-users] Kraken release and RGW --> "S3 bucket
> lifecycle API has been added. Note that currently it only supports object
> expiration."
> ... additional strange but a bit different info related to the "permission
> denied"
>
> [root s3cmd-master]# ./s3cmd --no-ssl put INSTALL s3://Test/
> --expiry-days=5
> upload: 'INSTALL' -> 's3://Test/INSTALL' [1 of 1]
> 3123 of 3123 100% in 0s 225.09 kB/s done
>
> [root s3cmd-master]# ./s3cmd info s3://Test/INSTALL
> s3://Test/INSTALL (object):
> File size: 3123
> Last mod: Mon, 03 Apr 2017 12:01:47 GMT
> MIME type: text/plain
> Storage: STANDARD
> MD5 sum: 63834dbb20b32968505c4ebe768fc8c4
> SSE: none
> policy: http://s3.amazonaws.com/doc/2006-03-01/;>
> Test1000<
> /MaxKeys>false
> INSTALL2017-04-03T12:01:47.745Z LastModified>63834dbb20b32968505c4ebe768fc8
> c43123STANDARD StorageClass>666First
> User
> README.TXT2017-03-31T22:36:38.380Z LastModified>708efc3b9184c8b112e36062804aca
> 1e88STANDARD StorageClass>666First
> User
> cors: none
> ACL: First User: FULL_CONTROL
> x-amz-meta-s3cmd-attrs: atime:1491218263/ctime:
> 1490998096/gid:0/gname:root/md5:63834dbb20b32968505c4ebe768fc8
> c4/mode:33188/mtime:1488021707/uid:0/uname:root
>
> [root s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/ --expiry-days=365
> ERROR: Access to bucket 'Test' was denied
> ERROR: S3 error: 403 (AccessDenied)
>
> [root s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/INSTALL
> --expiry-days=365
> ERROR: Parameter problem: Expecting S3 URI with just the bucket name set
> instead of 's3://Test/INSTALL'
> [root@mucsds26 s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/
> --expiry-days=365
> ERROR: Access to bucket 'Test' was denied
> ERROR: S3 error: 403 (AccessDenied)
>
> [root s3cmd-master]# ./s3cmd --no-ssl la expire s3://Test
> 2017-04-03 12:01 3123 s3://Test/INSTALL
> 2017-03-31 22:36 88 s3://Test/README.TXT
>
>
> 
>
> Gesendet: Montag, 03. April 2017 um 12:31 Uhr
> Von: ceph.nov...@habmalnefrage.de
> An: "Ben Hines" , ceph-users 
> Betreff: Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle
> API has been added. Note that currently it only supports object expiration."
> Hi Cephers...
>
> I did set the "lifecycle" via Cyberduck.I do also get an error first, then
> suddenly Cyberduck refreshes the window aand the lifecycle is there.
>
> I see the following 

Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."

[ceph . novice]

... hmm, "modify" gives no error and may be the option to use, but I don't see anything related to an "expires" meta field

 


[root s3cmd-master]# ./s3cmd --no-ssl --verbose modify s3://Test/INSTALL --expiry-days=365
INFO: Summary: 1 remote files to modify
modify: 's3://Test/INSTALL'


[root s3cmd-master]# ./s3cmd --no-ssl --verbose info s3://Test/INSTALL
s3://Test/INSTALL (object):
   File size: 3123
   Last mod:  Mon, 03 Apr 2017 12:35:28 GMT
   MIME type: text/plain
   Storage:   STANDARD
   MD5 sum:   63834dbb20b32968505c4ebe768fc8c4
   SSE:   none
   policy:    Test1000falseINSTALL2017-04-03T12:35:28.533Z63834dbb20b32968505c4ebe768fc8c43123STANDARD666First UserREADME.TXT2017-03-31T22:36:38.380Z708efc3b9184c8b112e36062804aca1e88STANDARD666First User
   cors:    none
   ACL:   First User: FULL_CONTROL
   x-amz-meta-s3cmd-attrs: atime:1491218263/ctime:1490998096/gid:0/gname:root/md5:63834dbb20b32968505c4ebe768fc8c4/mode:33188/mtime:1488021707/uid:0/uname:root

 


 

Gesendet: Montag, 03. April 2017 um 14:13 Uhr
Von: ceph.nov...@habmalnefrage.de
An: ceph-users 
Betreff: Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."

... additional strange but a bit different info related to the "permission denied"
 
[root s3cmd-master]# ./s3cmd --no-ssl put INSTALL s3://Test/ --expiry-days=5
upload: 'INSTALL' -> 's3://Test/INSTALL' [1 of 1]
3123 of 3123 100% in 0s 225.09 kB/s done

[root s3cmd-master]# ./s3cmd info s3://Test/INSTALL
s3://Test/INSTALL (object):
File size: 3123
Last mod: Mon, 03 Apr 2017 12:01:47 GMT
MIME type: text/plain
Storage: STANDARD
MD5 sum: 63834dbb20b32968505c4ebe768fc8c4
SSE: none
policy: Test1000falseINSTALL2017-04-03T12:01:47.745Z63834dbb20b32968505c4ebe768fc8c43123STANDARD666First UserREADME.TXT2017-03-31T22:36:38.380Z708efc3b9184c8b112e36062804aca1e88STANDARD666First User
cors: none
ACL: First User: FULL_CONTROL
x-amz-meta-s3cmd-attrs: atime:1491218263/ctime:1490998096/gid:0/gname:root/md5:63834dbb20b32968505c4ebe768fc8c4/mode:33188/mtime:1488021707/uid:0/uname:root

[root s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/ --expiry-days=365
ERROR: Access to bucket 'Test' was denied
ERROR: S3 error: 403 (AccessDenied)

[root s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/INSTALL --expiry-days=365
ERROR: Parameter problem: Expecting S3 URI with just the bucket name set instead of 's3://Test/INSTALL'
[root@mucsds26 s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/ --expiry-days=365
ERROR: Access to bucket 'Test' was denied
ERROR: S3 error: 403 (AccessDenied)

[root s3cmd-master]# ./s3cmd --no-ssl la expire s3://Test
2017-04-03 12:01 3123 s3://Test/INSTALL
2017-03-31 22:36 88 s3://Test/README.TXT

 
 

Gesendet: Montag, 03. April 2017 um 12:31 Uhr
Von: ceph.nov...@habmalnefrage.de
An: "Ben Hines" , ceph-users 
Betreff: Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."
Hi Cephers...

I did set the "lifecycle" via Cyberduck.I do also get an error first, then suddenly Cyberduck refreshes the window aand the lifecycle is there.

I see the following when I check it via s3cmd (GitHub master version because the regular installed version doesn't offer the "getlifecycle" option):

[root s3cmd-master]# ./s3cmd getlifecycle s3://Test/README.txt


    
    Cyberduck-nVWEhQwE
    
    Enabled
    
    1
    
    

 
Here is my S3 "user info":

[root ~]# radosgw-admin user info --uid=666
{
"user_id": "666",
"display_name": "First User",
"email": "a...@c.de",
"suspended": 0,
"max_buckets": 1000,
"auid": 0,
"subusers": [],
"keys": [
{
"user": "666",
"access_key": "abc ;)",
"secret_key": "abc def ;)"
}
],
"swift_keys": [],
"caps": [],
"op_mask": "read, write, delete",
"default_placement": "",
"placement_tags": [],
"bucket_quota": {
"enabled": false,
"check_on_raw": false,
"max_size": -1,
"max_size_kb": 0,
"max_objects": -1
},
"user_quota": {
"enabled": false,
"check_on_raw": false,
"max_size": -1,
"max_size_kb": 0,
"max_objects": -1
},
"temp_url_keys": [],
"type": "rgw"
}

If someone has a working example how to set lifecycle via the s3cmd, I can try it and send the outcome...
 

Gesendet: Montag, 03. April 2017 um 01:43 Uhr
Von: "Ben Hines" 
An: "Orit Wasserman" 
Cc: ceph-users 
Betreff: Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."

Hmm, Nope, not using tenants feature. The users/buckets were created on prior ceph versions, perhaps i'll try with a newly created user + bucket.
radosgw-admin user info --uid=foo

 

{
    "user_id": "foo",
    

Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."

[ceph . novice]

... additional strange but a bit different info related to the "permission 
denied"
 
[root s3cmd-master]# ./s3cmd --no-ssl put INSTALL s3://Test/ --expiry-days=5
upload: 'INSTALL' -> 's3://Test/INSTALL'  [1 of 1]
 3123 of 3123   100% in0s   225.09 kB/s  done

[root s3cmd-master]# ./s3cmd info s3://Test/INSTALL
s3://Test/INSTALL (object):
   File size: 3123
   Last mod:  Mon, 03 Apr 2017 12:01:47 GMT
   MIME type: text/plain
   Storage:   STANDARD
   MD5 sum:   63834dbb20b32968505c4ebe768fc8c4
   SSE:   none
   policy:http://s3.amazonaws.com/doc/2006-03-01/;>Test1000falseINSTALL2017-04-03T12:01:47.745Z63834dbb20b32968505c4ebe768fc8c43123STANDARD666First
 
UserREADME.TXT2017-03-31T22:36:38.380Z708efc3b9184c8b112e36062804aca1e88STANDARD666First
 User
   cors:none
   ACL:   First User: FULL_CONTROL
   x-amz-meta-s3cmd-attrs: 
atime:1491218263/ctime:1490998096/gid:0/gname:root/md5:63834dbb20b32968505c4ebe768fc8c4/mode:33188/mtime:1488021707/uid:0/uname:root

[root s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/ --expiry-days=365
ERROR: Access to bucket 'Test' was denied
ERROR: S3 error: 403 (AccessDenied)

[root s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/INSTALL --expiry-days=365
ERROR: Parameter problem: Expecting S3 URI with just the bucket name set 
instead of 's3://Test/INSTALL'
[root@mucsds26 s3cmd-master]# ./s3cmd --no-ssl expire s3://Test/ 
--expiry-days=365
ERROR: Access to bucket 'Test' was denied
ERROR: S3 error: 403 (AccessDenied)

[root s3cmd-master]# ./s3cmd --no-ssl la expire s3://Test
2017-04-03 12:01  3123   s3://Test/INSTALL
2017-03-31 22:3688   s3://Test/README.TXT

 
 

Gesendet: Montag, 03. April 2017 um 12:31 Uhr
Von: ceph.nov...@habmalnefrage.de
An: "Ben Hines" , ceph-users 
Betreff: Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API 
has been added. Note that currently it only supports object expiration."
Hi Cephers...

I did set the "lifecycle" via Cyberduck.I do also get an error first, then 
suddenly Cyberduck refreshes the window aand the lifecycle is there.

I see the following when I check it via s3cmd (GitHub master version because 
the regular installed version doesn't offer the "getlifecycle" option):

[root s3cmd-master]# ./s3cmd getlifecycle s3://Test/README.txt

http://s3.amazonaws.com/doc/2006-03-01/;>
    
    Cyberduck-nVWEhQwE
    
    Enabled
    
    1
    
    

 
Here is my S3 "user info":

[root ~]# radosgw-admin user info --uid=666
{
"user_id": "666",
"display_name": "First User",
"email": "a...@c.de",
"suspended": 0,
"max_buckets": 1000,
"auid": 0,
"subusers": [],
"keys": [
{
"user": "666",
"access_key": "abc ;)",
"secret_key": "abc def ;)"
}
],
"swift_keys": [],
"caps": [],
"op_mask": "read, write, delete",
"default_placement": "",
"placement_tags": [],
"bucket_quota": {
"enabled": false,
"check_on_raw": false,
"max_size": -1,
"max_size_kb": 0,
"max_objects": -1
},
"user_quota": {
"enabled": false,
"check_on_raw": false,
"max_size": -1,
"max_size_kb": 0,
"max_objects": -1
},
"temp_url_keys": [],
"type": "rgw"
}

If someone has a working example how to set lifecycle via the s3cmd, I can try 
it and send the outcome...
 

Gesendet: Montag, 03. April 2017 um 01:43 Uhr
Von: "Ben Hines" 
An: "Orit Wasserman" 
Cc: ceph-users 
Betreff: Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API 
has been added. Note that currently it only supports object expiration."

Hmm, Nope, not using tenants feature. The users/buckets were created on prior 
ceph versions, perhaps i'll try with a newly created user + bucket.
radosgw-admin user info --uid=foo

 

{
    "user_id": "foo",
    "display_name": "foo",
    "email": "snip",
    "suspended": 0,
    "max_buckets": 1000,
    "auid": 0,
    "subusers": [
        {
            "id": "foo:swift",
            "permissions": "full-control"
        }
    ],
    "keys": [
        {
            "user": "foo:swift",
            "access_key": "xxx",
            "secret_key": ""
        },
        {
            "user": "foo",
            "access_key": "xxx",
            "secret_key": ""
        }
    ],
    "swift_keys": [],
    "caps": [
        {
            "type": "buckets",
            "perm": "*"
        },
        {
            "type": "metadata",
            "perm": "*"
        },
        {
            "type": "usage",
            "perm": "*"
        },
        {
            "type": "users",
            "perm": "*"
        },
        {
            "type": "zone",
            "perm": "*"
        }
    ],
    "op_mask": "read, write, delete",
    "default_placement": "",
    "placement_tags": [],
    "bucket_quota": {
        "enabled": false,
        "check_on_raw": false,
        "max_size": -1024,
        

Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."

[ceph . novice]

Hi Cephers...

I did set the "lifecycle" via Cyberduck.I do also get an error first, then 
suddenly Cyberduck refreshes the window aand the lifecycle is there.

I see the following when I check it via s3cmd (GitHub master version because 
the regular installed version doesn't offer the "getlifecycle" option):

[root s3cmd-master]# ./s3cmd getlifecycle s3://Test/README.txt

http://s3.amazonaws.com/doc/2006-03-01/;>
    
    Cyberduck-nVWEhQwE
    
    Enabled
    
    1
    
    

 
Here is my S3 "user info":

[root ~]# radosgw-admin user info --uid=666
{
"user_id": "666",
"display_name": "First User",
"email": "a...@c.de",
"suspended": 0,
"max_buckets": 1000,
"auid": 0,
"subusers": [],
"keys": [
{
"user": "666",
"access_key": "abc ;)",
"secret_key": "abc def ;)"
}
],
"swift_keys": [],
"caps": [],
"op_mask": "read, write, delete",
"default_placement": "",
"placement_tags": [],
"bucket_quota": {
"enabled": false,
"check_on_raw": false,
"max_size": -1,
"max_size_kb": 0,
"max_objects": -1
},
"user_quota": {
"enabled": false,
"check_on_raw": false,
"max_size": -1,
"max_size_kb": 0,
"max_objects": -1
},
"temp_url_keys": [],
"type": "rgw"
}

If someone has a working example how to set lifecycle via the s3cmd, I can try 
it and send the outcome...
 

Gesendet: Montag, 03. April 2017 um 01:43 Uhr
Von: "Ben Hines" 
An: "Orit Wasserman" 
Cc: ceph-users 
Betreff: Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API 
has been added. Note that currently it only supports object expiration."

Hmm, Nope, not using tenants feature. The users/buckets were created on prior 
ceph versions, perhaps i'll try with a newly created user + bucket.
radosgw-admin user info --uid=foo

 

{
    "user_id": "foo",
    "display_name": "foo",
    "email": "snip",
    "suspended": 0,
    "max_buckets": 1000,
    "auid": 0,
    "subusers": [
        {
            "id": "foo:swift",
            "permissions": "full-control"
        }
    ],
    "keys": [
        {
            "user": "foo:swift",
            "access_key": "xxx",
            "secret_key": ""
        },
        {
            "user": "foo",
            "access_key": "xxx",
            "secret_key": ""
        }
    ],
    "swift_keys": [],
    "caps": [
        {
            "type": "buckets",
            "perm": "*"
        },
        {
            "type": "metadata",
            "perm": "*"
        },
        {
            "type": "usage",
            "perm": "*"
        },
        {
            "type": "users",
            "perm": "*"
        },
        {
            "type": "zone",
            "perm": "*"
        }
    ],
    "op_mask": "read, write, delete",
    "default_placement": "",
    "placement_tags": [],
    "bucket_quota": {
        "enabled": false,
        "check_on_raw": false,
        "max_size": -1024,
        "max_size_kb": 0,
        "max_objects": -1
    },
    "user_quota": {
        "enabled": false,
        "check_on_raw": false,
        "max_size": -1024,
        "max_size_kb": 0,
        "max_objects": -1
    },
    "temp_url_keys": [],
    "type": "none"
}
 

 
 
 
On Sun, Apr 2, 2017 at 5:54 AM, Orit Wasserman 
 wrote:

I see : acct_user=foo, acct_name=foo,
Are you using radosgw with tenants?
If not it could be the problem
 
Orit

 
On Sat, Apr 1, 2017 at 7:43 AM, Ben Hines 
 wrote:
I'm also trying to use lifecycles (via boto3) but i'm getting permission denied 
trying to create the lifecycle. I'm bucket owner with full_control and 
WRITE_ACP for good measure. Any ideas?
 
This is debug ms=20 debug radosgw=20
 
 
 

2017-03-31 21:28:18.382217 7f50d0010700  2 req 8:0.000693:s3:PUT 
/bentest:put_lifecycle:verifying op permissions
2017-03-31 21:28:18.38 7f50d0010700  5 Searching permissions for 
identity=RGWThirdPartyAccountAuthApplier() -> 
RGWLocalAuthApplier(acct_user=foo, acct_name=foo, subuser=, perm_mask=15, 
is_admin=) mask=56
2017-03-31 21:28:18.382232 7f50d0010700  5 Searching permissions for uid=foo
2017-03-31 21:28:18.382235 7f50d0010700  5 Found permission: 15
2017-03-31 21:28:18.382237 7f50d0010700  5 Searching permissions for group=1 
mask=56
2017-03-31 21:28:18.382297 7f50d0010700  5 Found permission: 3
2017-03-31 21:28:18.382307 7f50d0010700  5 Searching permissions for group=2 
mask=56
2017-03-31 21:28:18.382313 7f50d0010700  5 Permissions for group not found
2017-03-31 21:28:18.382318 7f50d0010700  5 Getting permissions 
identity=RGWThirdPartyAccountAuthApplier() -> 
RGWLocalAuthApplier(acct_user=foo, acct_name=foo, subuser=, perm_mask=15, 
is_admin=) owner=foo 

Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."

[Ben Hines]

Hmm, Nope, not using tenants feature. The users/buckets were created on
prior ceph versions, perhaps i'll try with a newly created user + bucket.

radosgw-admin user info --uid=foo

{
"user_id": "foo",
"display_name": "foo",
"email": "snip",
"suspended": 0,
"max_buckets": 1000,
"auid": 0,
"subusers": [
{
"id": "foo:swift",
"permissions": "full-control"
}
],
"keys": [
{
"user": "foo:swift",
"access_key": "xxx",
"secret_key": ""
},
{
"user": "foo",
"access_key": "xxx",
"secret_key": ""
}
],
"swift_keys": [],
"caps": [
{
"type": "buckets",
"perm": "*"
},
{
"type": "metadata",
"perm": "*"
},
{
"type": "usage",
"perm": "*"
},
{
"type": "users",
"perm": "*"
},
{
"type": "zone",
"perm": "*"
}
],
"op_mask": "read, write, delete",
"default_placement": "",
"placement_tags": [],
"bucket_quota": {
"enabled": false,
"check_on_raw": false,
"max_size": -1024,
"max_size_kb": 0,
"max_objects": -1
},
"user_quota": {
"enabled": false,
"check_on_raw": false,
"max_size": -1024,
"max_size_kb": 0,
"max_objects": -1
},
"temp_url_keys": [],
"type": "none"
}




On Sun, Apr 2, 2017 at 5:54 AM, Orit Wasserman  wrote:

> I see : acct_user=foo, acct_name=foo,
> Are you using radosgw with tenants?
> If not it could be the problem
>
> Orit
>
> On Sat, Apr 1, 2017 at 7:43 AM, Ben Hines  wrote:
>
>> I'm also trying to use lifecycles (via boto3) but i'm getting permission
>> denied trying to create the lifecycle. I'm bucket owner with full_control
>> and WRITE_ACP for good measure. Any ideas?
>>
>> This is debug ms=20 debug radosgw=20
>>
>>
>>
>> 2017-03-31 21:28:18.382217 7f50d0010700  2 req 8:0.000693:s3:PUT
>> /bentest:put_lifecycle:verifying op permissions
>> 2017-03-31 21:28:18.38 7f50d0010700  5 Searching permissions for
>> identity=RGWThirdPartyAccountAuthApplier() ->
>> RGWLocalAuthApplier(acct_user=foo, acct_name=foo, subuser=,
>> perm_mask=15, is_admin=) mask=56
>> 2017-03-31 21:28:18.382232 7f50d0010700  5 Searching permissions for
>> uid=foo
>> 2017-03-31 21:28:18.382235 7f50d0010700  5 Found permission: 15
>> 2017-03-31 21:28:18.382237 7f50d0010700  5 Searching permissions for
>> group=1 mask=56
>> 2017-03-31 21:28:18.382297 7f50d0010700  5 Found permission: 3
>> 2017-03-31 21:28:18.382307 7f50d0010700  5 Searching permissions for
>> group=2 mask=56
>> 2017-03-31 21:28:18.382313 7f50d0010700  5 Permissions for group not found
>> 2017-03-31 21:28:18.382318 7f50d0010700  5 Getting permissions
>> identity=RGWThirdPartyAccountAuthApplier() ->
>> RGWLocalAuthApplier(acct_user=foo, acct_name=foo, subuser=,
>> perm_mask=15, is_admin=) owner=foo perm=8
>> 2017-03-31 21:28:18.382325 7f50d0010700 10  
>> identity=RGWThirdPartyAccountAuthApplier()
>> -> RGWLocalAuthApplier(acct_user=foo, acct_name=foo, subuser=,
>> perm_mask=15, is_admin=) requested perm (type)=8, policy perm=8,
>> user_perm_mask=8, acl perm=8
>> 2017-03-31 21:28:18.382330 7f50d0010700  2 req 8:0.000808:s3:PUT
>> /bentest:put_lifecycle:verifying op params
>> 2017-03-31 21:28:18.382334 7f50d0010700  2 req 8:0.000813:s3:PUT
>> /bentest:put_lifecycle:pre-executing
>> 2017-03-31 21:28:18.382339 7f50d0010700  2 req 8:0.000817:s3:PUT
>> /bentest:put_lifecycle:executing
>> 2017-03-31 21:28:18.382361 7f50d0010700 15 read len=183
>> data=http://s3.amazonaws.com
>> /doc/2006-03-01/">Enabled
>> 10
>> 2017-03-31 21:28:18.382439 7f50d0010700  2 req 8:0.000917:s3:PUT
>> /bentest:put_lifecycle:completing
>> 2017-03-31 21:28:18.382594 7f50d0010700  2 req 8:0.001072:s3:PUT
>> /bentest:put_lifecycle:op status=-13
>> 2017-03-31 21:28:18.382620 7f50d0010700  2 req 8:0.001098:s3:PUT
>> /bentest:put_lifecycle:http status=403
>> 2017-03-31 21:28:18.382665 7f50d0010700  1 == req done
>> req=0x7f50d000a340 op status=-13 http_status=403 ==
>>
>>
>> -Ben
>>
>> On Tue, Mar 28, 2017 at 6:42 AM, Daniel Gryniewicz 
>> wrote:
>>
>>> On 03/27/2017 04:28 PM, ceph.nov...@habmalnefrage.de wrote:
>>>
 Hi Cephers.

 Couldn't find any special documentation about the "S3 object expiration"
 so I assume it should work "AWS S3 like" (?!?) ...  BUT ...
 we have a test cluster based on 11.2.0 - Kraken and I set some object
 expiration dates via CyberDuck and DragonDisk, but the objects are still
 there, days after the applied date/time. Do I miss something?

 Thanks & regards


>>> It is intended to work like AWS S3, yes.  Not every feature of AWS
>>> lifecycle is supported, (for example no moving 

Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."

[Orit Wasserman]

I see : acct_user=foo, acct_name=foo,
Are you using radosgw with tenants?
If not it could be the problem

Orit

On Sat, Apr 1, 2017 at 7:43 AM, Ben Hines  wrote:

> I'm also trying to use lifecycles (via boto3) but i'm getting permission
> denied trying to create the lifecycle. I'm bucket owner with full_control
> and WRITE_ACP for good measure. Any ideas?
>
> This is debug ms=20 debug radosgw=20
>
>
>
> 2017-03-31 21:28:18.382217 7f50d0010700  2 req 8:0.000693:s3:PUT
> /bentest:put_lifecycle:verifying op permissions
> 2017-03-31 21:28:18.38 7f50d0010700  5 Searching permissions for
> identity=RGWThirdPartyAccountAuthApplier() ->
> RGWLocalAuthApplier(acct_user=foo, acct_name=foo, subuser=, perm_mask=15,
> is_admin=) mask=56
> 2017-03-31 21:28:18.382232 7f50d0010700  5 Searching permissions for
> uid=foo
> 2017-03-31 21:28:18.382235 7f50d0010700  5 Found permission: 15
> 2017-03-31 21:28:18.382237 7f50d0010700  5 Searching permissions for
> group=1 mask=56
> 2017-03-31 21:28:18.382297 7f50d0010700  5 Found permission: 3
> 2017-03-31 21:28:18.382307 7f50d0010700  5 Searching permissions for
> group=2 mask=56
> 2017-03-31 21:28:18.382313 7f50d0010700  5 Permissions for group not found
> 2017-03-31 21:28:18.382318 7f50d0010700  5 Getting permissions
> identity=RGWThirdPartyAccountAuthApplier() ->
> RGWLocalAuthApplier(acct_user=foo, acct_name=foo, subuser=, perm_mask=15,
> is_admin=) owner=foo perm=8
> 2017-03-31 21:28:18.382325 7f50d0010700 10  
> identity=RGWThirdPartyAccountAuthApplier()
> -> RGWLocalAuthApplier(acct_user=foo, acct_name=foo, subuser=,
> perm_mask=15, is_admin=) requested perm (type)=8, policy perm=8,
> user_perm_mask=8, acl perm=8
> 2017-03-31 21:28:18.382330 7f50d0010700  2 req 8:0.000808:s3:PUT
> /bentest:put_lifecycle:verifying op params
> 2017-03-31 21:28:18.382334 7f50d0010700  2 req 8:0.000813:s3:PUT
> /bentest:put_lifecycle:pre-executing
> 2017-03-31 21:28:18.382339 7f50d0010700  2 req 8:0.000817:s3:PUT
> /bentest:put_lifecycle:executing
> 2017-03-31 21:28:18.382361 7f50d0010700 15 read len=183
> data=http://s3.amazonaws.com
> /doc/2006-03-01/">Enabled
> 10
> 2017-03-31 21:28:18.382439 7f50d0010700  2 req 8:0.000917:s3:PUT
> /bentest:put_lifecycle:completing
> 2017-03-31 21:28:18.382594 7f50d0010700  2 req 8:0.001072:s3:PUT
> /bentest:put_lifecycle:op status=-13
> 2017-03-31 21:28:18.382620 7f50d0010700  2 req 8:0.001098:s3:PUT
> /bentest:put_lifecycle:http status=403
> 2017-03-31 21:28:18.382665 7f50d0010700  1 == req done
> req=0x7f50d000a340 op status=-13 http_status=403 ==
>
>
> -Ben
>
> On Tue, Mar 28, 2017 at 6:42 AM, Daniel Gryniewicz 
> wrote:
>
>> On 03/27/2017 04:28 PM, ceph.nov...@habmalnefrage.de wrote:
>>
>>> Hi Cephers.
>>>
>>> Couldn't find any special documentation about the "S3 object expiration"
>>> so I assume it should work "AWS S3 like" (?!?) ...  BUT ...
>>> we have a test cluster based on 11.2.0 - Kraken and I set some object
>>> expiration dates via CyberDuck and DragonDisk, but the objects are still
>>> there, days after the applied date/time. Do I miss something?
>>>
>>> Thanks & regards
>>>
>>>
>> It is intended to work like AWS S3, yes.  Not every feature of AWS
>> lifecycle is supported, (for example no moving between storage tiers), but
>> deletion works, and is tested in teuthology runs.
>>
>> Did you somehow turn it off?  The config option rgw_enable_lc_threads
>> controls it, but it defaults to "on".  Also make sure rgw_lc_debug_interval
>> is not set, and that rgw_lifecycle_work_time isn't set to some interval too
>> small scan your objects...
>>
>> Daniel
>>
>> ___
>> ceph-users mailing list
>> ceph-users@lists.ceph.com
>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>>
>
>
> ___
> ceph-users mailing list
> ceph-users@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>
>
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: [ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."

[Ben Hines]

I'm also trying to use lifecycles (via boto3) but i'm getting permission
denied trying to create the lifecycle. I'm bucket owner with full_control
and WRITE_ACP for good measure. Any ideas?

This is debug ms=20 debug radosgw=20



2017-03-31 21:28:18.382217 7f50d0010700  2 req 8:0.000693:s3:PUT
/bentest:put_lifecycle:verifying op permissions
2017-03-31 21:28:18.38 7f50d0010700  5 Searching permissions for
identity=RGWThirdPartyAccountAuthApplier() ->
RGWLocalAuthApplier(acct_user=foo,
acct_name=foo, subuser=, perm_mask=15, is_admin=) mask=56
2017-03-31 21:28:18.382232 7f50d0010700  5 Searching permissions for uid=foo
2017-03-31 21:28:18.382235 7f50d0010700  5 Found permission: 15
2017-03-31 21:28:18.382237 7f50d0010700  5 Searching permissions for
group=1 mask=56
2017-03-31 21:28:18.382297 7f50d0010700  5 Found permission: 3
2017-03-31 21:28:18.382307 7f50d0010700  5 Searching permissions for
group=2 mask=56
2017-03-31 21:28:18.382313 7f50d0010700  5 Permissions for group not found
2017-03-31 21:28:18.382318 7f50d0010700  5 Getting permissions identity=
RGWThirdPartyAccountAuthApplier() -> RGWLocalAuthApplier(acct_user=foo,
acct_name=foo, subuser=, perm_mask=15, is_admin=) owner=foo perm=8
2017-03-31 21:28:18.382325 7f50d0010700 10  identity=
RGWThirdPartyAccountAuthApplier() -> RGWLocalAuthApplier(acct_user=foo,
acct_name=foo, subuser=, perm_mask=15, is_admin=) requested perm (type)=8,
policy perm=8, user_perm_mask=8, acl perm=8
2017-03-31 21:28:18.382330 7f50d0010700  2 req 8:0.000808:s3:PUT
/bentest:put_lifecycle:verifying op params
2017-03-31 21:28:18.382334 7f50d0010700  2 req 8:0.000813:s3:PUT
/bentest:put_lifecycle:pre-executing
2017-03-31 21:28:18.382339 7f50d0010700  2 req 8:0.000817:s3:PUT
/bentest:put_lifecycle:executing
2017-03-31 21:28:18.382361 7f50d0010700 15 read len=183
data=http://s3.amazonaws.com/doc/2006-03-01/
">Enabled10
2017-03-31 21:28:18.382439 7f50d0010700  2 req 8:0.000917:s3:PUT
/bentest:put_lifecycle:completing
2017-03-31 21:28:18.382594 7f50d0010700  2 req 8:0.001072:s3:PUT
/bentest:put_lifecycle:op status=-13
2017-03-31 21:28:18.382620 7f50d0010700  2 req 8:0.001098:s3:PUT
/bentest:put_lifecycle:http status=403
2017-03-31 21:28:18.382665 7f50d0010700  1 == req done
req=0x7f50d000a340 op status=-13 http_status=403 ==


-Ben

On Tue, Mar 28, 2017 at 6:42 AM, Daniel Gryniewicz  wrote:

> On 03/27/2017 04:28 PM, ceph.nov...@habmalnefrage.de wrote:
>
>> Hi Cephers.
>>
>> Couldn't find any special documentation about the "S3 object expiration"
>> so I assume it should work "AWS S3 like" (?!?) ...  BUT ...
>> we have a test cluster based on 11.2.0 - Kraken and I set some object
>> expiration dates via CyberDuck and DragonDisk, but the objects are still
>> there, days after the applied date/time. Do I miss something?
>>
>> Thanks & regards
>>
>>
> It is intended to work like AWS S3, yes.  Not every feature of AWS
> lifecycle is supported, (for example no moving between storage tiers), but
> deletion works, and is tested in teuthology runs.
>
> Did you somehow turn it off?  The config option rgw_enable_lc_threads
> controls it, but it defaults to "on".  Also make sure rgw_lc_debug_interval
> is not set, and that rgw_lifecycle_work_time isn't set to some interval too
> small scan your objects...
>
> Daniel
>
> ___
> ceph-users mailing list
> ceph-users@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

[ceph-users] Kraken release and RGW --> "S3 bucket lifecycle API has been added. Note that currently it only supports object expiration."

[ceph . novice]

Hi Cephers.

 

Couldn't find any special documentation about the "S3 object expiration" so I assume it should work "AWS S3 like" (?!?) ...  BUT ...

we have a test cluster based on 11.2.0 - Kraken and I set some object expiration dates via CyberDuck and DragonDisk, but the objects are still there, days after the applied date/time. Do I miss something?

 

Thanks & regards
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com