Skip to content
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

Merged
merged 5 commits into from Nov 11, 2016

Conversation

Abhishekvrshny
Copy link

Robin H. Johnson and others added 5 commits November 3, 2016 14:32
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)
@Abhishekvrshny Abhishekvrshny added this to the jewel milestone Nov 3, 2016
@Abhishekvrshny Abhishekvrshny self-assigned this Nov 3, 2016
@ghost ghost changed the base branch from jewel to jewel-next November 9, 2016 09:55
@ghost
Copy link

ghost commented Nov 9, 2016

jenkins test this please (test-erasure-eio failed)

@ghost
Copy link

ghost commented Nov 9, 2016

jenkins test this please (general jenkins failure)

ghost pushed a commit that referenced this pull request Nov 9, 2016
…when no hostnames are configured

Reviewed-by: Loic Dachary <ldachary@redhat.com>
@ghost ghost assigned oritwas Nov 11, 2016
@ghost
Copy link

ghost commented Nov 11, 2016

@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.

@oritwas oritwas merged commit ea83a70 into ceph:jewel-next Nov 11, 2016
@robbat2
Copy link
Contributor

robbat2 commented Dec 16, 2016

This is on ceph:jewel-next, but when it will be merged to ceph:jewel for release in the 10.2.6 release?

@smithfarm
Copy link
Contributor

@robbat2 The commits in this PR are in jewel, too. I just checked.

@robbat2
Copy link
Contributor

robbat2 commented Jan 27, 2017

Yes, I see in 5b402f8 that jewel-next got merged to jewel on Dec 22nd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants