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

init-ceph: keep trying other OSDs if we fail to set CRUSH position on one OSD #1846

Merged
2 commits merged into from May 24, 2014

Conversation

liewegas
Copy link
Member

No description provided.

Sage Weil added 2 commits May 20, 2014 16:28
If we fail to start the daemon, skip the post_start and other steps.

Signed-off-by: Sage Weil <sage@inktank.com>
If we fail to set the CRUSH position for one OSD, continue on to try
starting others, just as we do when we fail to start the daemon.

Fixes: #8342
Signed-off-by: Sage Weil <sage@inktank.com>
@ghost
Copy link

ghost commented May 22, 2014

👍 The $pre_mount and $pre_start commands may also fail and break the loop. If they break the loop because they are bugous, it is probably a good thing. If they would succeed on some OSDs and not others, it's probably a bad thing. Since they are neither documented nor used in upstart scripts there does not seem to be a need to change anything.

@onlyjob
Copy link
Contributor

onlyjob commented May 24, 2014

Works as expected and fixes the problem. Thanks very much. Please commit.

ghost pushed a commit that referenced this pull request May 24, 2014
init-ceph: keep trying other OSDs if we fail to set CRUSH position on one OSD

Reviewed-by: Loic Dachary <loic@dachary.org>
Reviewed-by: Dmitry Smirnov <onlyjob@debian.org>
@ghost ghost merged commit 82e40bc into master May 24, 2014
@liewegas liewegas deleted the wip-8342 branch June 9, 2014 03:16
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants