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

crush: fix v4 bucket feature detection (straw2) #4322

Merged
2 commits merged into from Apr 10, 2015
Merged

crush: fix v4 bucket feature detection (straw2) #4322

2 commits merged into from Apr 10, 2015

Conversation

liewegas
Copy link
Member

This needs to get backported to hammer too!

Backport: hammer
Signed-off-by: Sage Weil <sage@redhat.com>
@gregsfortytwo
Copy link
Member

Looks good to me, but the gitbuilders are slow so not merging.

@gregsfortytwo
Copy link
Member

Also I'm sure @dachary et al will be grateful if you can push the "fix has_v4_buckets()" commit with a backport tag.

@ghost
Copy link

ghost commented Apr 10, 2015

@liewegas @gregsfortytwo is right, I would be happy ;-). Although Backport: in the commit message is not convenient to track actual backporting, it is probably an appropriate place to say : "I think it would make sense to backport this patch to X,Y,Z".

alg, not type!

This bug made us incorrectly think we were using v4 features when user type
5 was being used.  That's currently 'rack' with recent crush maps, but
was other types for clusters that were created with older versions.  This
is clearly problematic as it will lock out non-hammer clients incorrectly,
breaking deployments on upgrade.

Fixes: #11364
Backport: hammer
Signed-off-by: Sage Weil <sage@redhat.com>
ghost pushed a commit that referenced this pull request Apr 10, 2015
crush: fix v4 bucket feature detection (straw2)

Reviewed-by: Greg Farnum <gfarnum@redhat.com>
Reviewed-by: Loic Dachary <ldachary@redhat.com>
@ghost ghost merged commit 33bdae7 into next Apr 10, 2015
@liewegas liewegas deleted the wip-crush-v4 branch April 10, 2015 15:50
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants