jewel: Error EINVAL: removing mon.a at 172.21.15.16:6789/0, there will be 1 monitors #11999
Conversation
Fixes: http://tracker.ceph.com/issues/17725 Signed-off-by: Joao Eduardo Luis <joao@suse.de> (cherry picked from commit c9d46cf)
Signed-off-by: Joao Eduardo Luis <joao@suse.de> (cherry picked from commit 20dcb59)
|
lgtm, although the commit dropping the 'goto' statements is a lot more about aesthetics than bug fixing - i don't think it causes any harm by being backported anyway. |
….21.15.16:6789/0, there will be 1 monitors Reviewed-by: Loic Dachary <ldachary@redhat.com>
|
@theanalyst , @athanatos , should this go in before v10.2.4? |
|
I think this still needs to be tested. @Abhishekvrshny @dachary ? |
|
@athanatos @ktdreyer this is @theanalyst decision. |
|
@dachary @athanatos did this pass through an integration run already (looks harmless to include IMO) |
|
It was included in http://tracker.ceph.com/issues/17851#note-9 which had a flawless rados suite run at http://tracker.ceph.com/issues/17851#note-12 . Note however that this is the usual X/2000 designed for pre-merge verification and not the X/50 designed to validate a release. |
|
@athanatos by merging in jewel-next you targeted 10.2.5. Please speak up if you wanted this pull request in 10.2.4 instead. |
|
@dachary Sorry, didn't notice. Can you move it over? |
|
@athanatos I'll do it |
ghost
mentioned this pull request
http://tracker.ceph.com/issues/17904