Bug 1718981 - Add higher retry/delay defaults to check the quorum status.
Summary: Add higher retry/delay defaults to check the quorum status.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 4.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 4.0
Assignee: Guillaume Abrioux
QA Contact: Vasishta
URL:
Whiteboard:
Depends On:
Blocks: 1722066
TreeView+ depends on / blocked
 
Reported: 2019-06-10 16:48 UTC by Francesco Pantano
Modified: 2020-01-31 12:46 UTC (History)
9 users (show)

Fixed In Version: ceph-ansible-4.0.0-0.1.rc10.el8cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-31 12:46:18 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 4131 0 'None' closed Add higher retry/delay defaults to check the quorum status. 2020-03-01 19:55:00 UTC
Github ceph ceph-ansible pull 4138 0 'None' closed Add higher retry/delay defaults to check the quorum status. (bp #4131) 2020-03-01 19:55:00 UTC
Red Hat Product Errata RHBA-2020:0312 0 None None None 2020-01-31 12:46:41 UTC

Description Francesco Pantano 2019-06-10 16:48:34 UTC
Description of problem:

As described in bz#1707020 sometimes ceph-ansible fails during a scale up with the 'controller-X out of quorum' message.
After some investigations we've found it could be related to the checks made by the handlers when mons containers are restarted.
Speaking from a pure c-a side, as the [1] suggests, the handler that restarts the monitors can be tuned and we're able to override these parameters via CephAnsibleExtraConfig, but having better (tuned) defaults could help to avoid override these parameters on different scenarios.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 John Fulton 2019-06-19 17:23:44 UTC
Bugs 1719013, 1707020, and 1722066 all seem to be caused by this issue. The defaults no longer seem right for Nautilus to restart its Monitors so we should have this fix.

Comment 4 Giridhar Ramaraju 2019-08-05 13:06:30 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 5 Giridhar Ramaraju 2019-08-05 13:09:08 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 12 errata-xmlrpc 2020-01-31 12:46:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0312


Note You need to log in before you can comment on or make changes to this bug.