Ceph » rgw

Thanks, Niko.

Neither of those commits would seem able to cause this. Will try your lifecycle policy and update.

Matt

no, but could you try using an alternate lifecycle document?

e.g., try:

<LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/&quot;>
<Rule>
<ID>delete-7-days</ID>
<Filter>
<Prefix></Prefix>
</Filter>
<Status>Enabled</Status>
<Expiration>
<Days>7</Days>
</Expiration>
</Rule>
</LifecycleConfiguration>

We accept a <Prefix> element at the top level, as well as in a filter. I think the problem might be that you didn't send an <ID>.

Matt6

Okay - so I do have an update: while both client and server report errors, the lifecycle policies are still being updated.

i.e. if I specify the ID (or change the expiration days) in the JSON file, the change is stored by Ceph even though the command returns an error.

Matt I tried your example XML but might be doing something wrong:

```
$ aws s3api --endpoint-url=https://REDACTED put-bucket-lifecycle --bucket bucketname --lifecycle-configuration file://lifecycle-upstream.xml

Error parsing parameter '--lifecycle-configuration': Expected: '=', received: '<' for input:
<LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/&quot;>
```

We also updated all three Ceph RADOS gateways to the same latest version:

```
$ radosgw-admin --version
ceph version 15.2.5 (2c93eff00150f0cc5f106a559557a58d3d7b6f1f) octopus (stable)
```

Oddly enough, we now experience the issue with two of the three.

Still uncertain if this is an issue on our side or an issue with Ceph.

I don't believe the issue is related to format of the policy file. While testing I also ran `delete-bucket-lifecycle` multiple times to remove policies from the test bucket and experienced the same error.

Maybe you can improve the log level of rgw to 20, then try again, this will be helpful for positioning problem.

Have you upgraded the osds to match? I would expect these errors to go away when all rgws and osds are running the latest octopus. Sorry for the inconvenience!

Casey Bodley wrote:

Have you upgraded the osds to match? I would expect these errors to go away when all rgws and osds are running the latest octopus. Sorry for the inconvenience!

Sorry for the slow reply - I'm actually blocked by https://github.com/ceph/ceph-ansible/issues/5916 on updating the OSDs.

Right now the OSDs are a mixed bag.

$ sudo ceph tell osd.* version | grep version | awk '{print $2}' | sort | uniq -c
12 "15.2.2",
6 "15.2.5",

After resolving the above issue and updating all OSDs to 15.2.5 I'll try again.

Casey Bodley wrote:

Have you upgraded the osds to match? I would expect these errors to go away when all rgws and osds are running the latest octopus. Sorry for the inconvenience!

Sorry for the slow progress here - we were blocked by https://github.com/ceph/ceph-ansible/issues/5819 for performing updates.

All OSDs are now running v15.2.8 and I can confirm this issue is resolved :) Thanks everyone.

(How does one close an issue, or is that action restricted to admins here?)