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

luminous: rbd-mirror: forced promotion can result in incorrect status #18337

Merged
merged 2 commits into from Oct 27, 2017

Conversation

Projects
None yet
4 participants
@kmroz

kmroz commented Oct 16, 2017

dillaman added some commits Sep 26, 2017

rbd-mirror: forced-promotion should interrupt replay delay to shut down
Fixes: http://tracker.ceph.com/issues/21559
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
(cherry picked from commit e3b5831)
rbd-mirror: ensure forced-failover cannot result in sync state
If the local image already exists and the local image isn't
registered in the remote journal, it should be assumed that
it's already in the replaying state so it can verify the
ancestry to detect split-brains.

Fixes: http://tracker.ceph.com/issues/21559
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
(cherry picked from commit bc96c53)

@tchaikov tchaikov added this to the luminous milestone Oct 17, 2017

@theanalyst

This comment has been minimized.

Show comment
Hide comment
@theanalyst

theanalyst Oct 27, 2017

Member

Passed a teuthology run at http://tracker.ceph.com/issues/21830#note-7 and will be merged when approved

Member

theanalyst commented Oct 27, 2017

Passed a teuthology run at http://tracker.ceph.com/issues/21830#note-7 and will be merged when approved

@theanalyst theanalyst requested a review from dillaman Oct 27, 2017

@dillaman

👍

@theanalyst theanalyst merged commit 7c03693 into ceph:luminous Oct 27, 2017

3 of 4 checks passed

Docs: build check Docs: failed with errors
Details
Signed-off-by all commits in this PR are signed
Details
Unmodified Submodules submodules for project are unmodified
Details
make check make check succeeded
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment