Bug #43172
openRadosgw(rgw_build_bucket_policies) fails on old buckets
0%
Description
Hi,
We have an old cluster with pre-jewel buckets with indices in the data pool. The nautilus radosgw-admin commands do well with all these buckets, but radosgw fails on access. Buckets that have their indices in rgw.data.index are fine.
I tracked it down to the function rgw_build_bucket_policies in rgw/rgw_op.cc where at the end the placement rules are checked:
/* init dest placement -- only if bucket exists, otherwise request is either not relevant, or
* it's a create_bucket request, in which case the op will deal with the placement later */
if (s->bucket_exists) {
s->dest_placement.storage_class = s->info.storage_class;
s->dest_placement.inherit_from(s->bucket_info.placement_rule);
if (!store->svc.zone->get_zone_params().valid_placement(s->dest_placement)) {
ldpp_dout(s, 0) << "NOTICE: invalid dest placement: " << s->dest_placement.to_str() << dendl;
return -EINVAL;
}
}
In the Logs of radosgw I find the lines "req 5 0.000s NOTICE: invalid dest placement:", s->dest_placement.to_str() is empty.
I tried to add a new placement rule "pre-jewel", that reflects our old buckets and even added that as default for one user. He may create and work with new buckets. His old buckets still are inaccessible.
As we have lots of buckets that are in use, a solution would be nice, so we can finish our nautilus upgrade.
There once was a issue with luminous, that has been discussed and solved here (https://tracker.ceph.com/issues/22928) by Yehuda
kind regards,
Ingo