Bug #14208
closed
rgw: 500 returned on Put Bucket ACL (ECANCELLED/-125)
Added by Robin Johnson over 8 years ago.
Updated about 4 years ago.
Description
Put Bucket ACL is failing, returning ECANCELLED (-125)
<Error><Code>UnknownError</Code></Error>
The new ACL is just adding publicly readable to a given bucket, cannot reproduce on other buckets/users.
2015-12-30 22:56:07.042754 7fc718ce9700 1 -- [2607:f298:4:d006::5781]:0/1008664 --> [2607:f298:4:d007::8853]:6863/1453551 -- osd_op(client.170008394.0:4652663043 .bucket.meta.USER-BUCKET-NAME:default.170008394.70001 [call version.check_conds,call version.set,setxattr user.rgw.acl (197)] 13.101bba61 ondisk+write+known_if_redirected e838310) v5 -- ?+0 0x7fc92883d5b0 con 0x7fc94f4630f0
2015-12-30 22:56:07.043773 7fc718ce9700 0 WARNING: set_req_state_err err_no=125 resorting to 500
RGW logs at 20/20 attached (redacted private info).
The object .bucket.meta.USER-BUCKET-NAME:default.170008394.70001 seems fine.
Files
Could be related to metadata cache disagreement between different rgws (as we've seen in your environment).
- Target version deleted (
v0.94.6)
Yehuda Sadeh wrote:
Could be related to metadata cache disagreement between different rgws (as we've seen in your environment).
FWIW, we just saw this occur on a dev build of Jewel. Resolved by restarting all RGWs. Unable to reproduce after a restart.
- Status changed from New to Need More Info
- Assignee set to Matt Benjamin
Assigning myself. I think we need more context to guide in reproducing (or a reproducer?).
Matt,
We ran into this on Jewel 10.2.2 clusters, while creating a container (bizarrely reproducible only with a specified named container). Am attaching RGW logs captured with debug_ms set to 1/5 and debug_rgw set to 20/20, please let me know if you need any further info, the cluster is in a reproducible state.
Thanks,
-Pavan.
- Status changed from Need More Info to Closed
Also available in: Atom
PDF