New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jewel: disable virtual hosting of buckets when no hostnames are configured #11760
Conversation
The logic (added in 46aae19) for falling back to just using the hostname as the possible bucket name contained an accidental inversion, because RGWHandler_REST::validate_bucket_name returns success as zero. Backport: jewel Fixes: http://tracker.ceph.com/issues/17136 Re-Fixes: http://tracker.ceph.com/issues/15975 Signed-off-by: Robin H. Johnson <robin.johnson@dreamhost.com> (cherry picked from commit 70e0289)
if no hostnames are configured, all requests were treated as virtual hosted buckets. require at least one hostname in hostnames_set to consider setting in_hosted_domain Fixes: http://tracker.ceph.com/issues/17440 Signed-off-by: Casey Bodley <cbodley@redhat.com> (cherry picked from commit 7c7ad3c)
Signed-off-by: Casey Bodley <cbodley@redhat.com> (cherry picked from commit 36203c2)
Signed-off-by: Casey Bodley <cbodley@redhat.com> (cherry picked from commit aa34b98)
std::accumulate() was appending hostnames without commas or spaces Signed-off-by: Casey Bodley <cbodley@redhat.com> (cherry picked from commit 2d6efe8)
jenkins test this please (test-erasure-eio failed) |
jenkins test this please (general jenkins failure) |
…when no hostnames are configured Reviewed-by: Loic Dachary <ldachary@redhat.com>
@oritwas does this backport look good to merge ? It passed the rgw suite http://tracker.ceph.com/issues/17851#note-3 . Note that it will not be in 10.2.4, reason why it targets jewel-next. |
This is on |
@robbat2 The commits in this PR are in |
Yes, I see in 5b402f8 that |
http://tracker.ceph.com/issues/17769