Project

General

Profile

Bug #6314

catch case where mon starts up but has rank -1 accordingly to mon_status.

Added by Alfredo Deza over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
ceph-deploy
Target version:
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Now that `mon_status` is implemented we need some glue-code to check make it a bit more robust and ensure that the rank is not `-1`.

There is already a good chunk of this working in `ceph_deploy/mon.py:mon_status`

History

#1 Updated by Alfredo Deza over 10 years ago

  • Target version changed from v0.69 to v0.70

#2 Updated by Greg Farnum over 10 years ago

But...it should have rank -1 before it gets the chance to join the quorum, shouldn't it?
Or have I forgotten how ranks are assigned?

#3 Updated by Alfredo Deza over 10 years ago

  • Status changed from New to In Progress

Created issue #6324 to prevent this command from hanging.

#4 Updated by Alfredo Deza over 10 years ago

Greg, yes, you are correct. The idea here is that we will implement a command to deploy all monitors defined initially and wait until they form quorum.

We do need to check for this value for that, otherwise we can't continue.

#5 Updated by Alfredo Deza over 10 years ago

  • Status changed from In Progress to Resolved

Merged into ceph-deploy master branch with hash: e66d751

Also available in: Atom PDF