Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1760211

Summary: Bump up default pacemaker monitor timeout value for OVN DBs
Product: Red Hat OpenStack Reporter: Maciej Józefczyk <mjozefcz>
Component: puppet-tripleoAssignee: Kamil Sambor <ksambor>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: dalvarez, jjoyce, jschluet, ksambor, nusiddiq, pveiga, slinaber, tvignaud
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: ---Flags: ksambor: needinfo+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-tripleo-8.5.1-8.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1767005 1802949 (view as bug list) Environment:
Last Closed: 2020-03-10 11:22:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1767005, 1767008, 1797685, 1802949    

Comment 2 Daniel Alvarez Sanchez 2019-10-10 07:57:30 UTC 
Under pressure, the default monitor timeout value of 20 seconds is not enough to prevent unnecessary failovers of the ovn-dbs pacemaker resource.

While spawning a few VMs in the same time this could lead to unnecessary movements of master DB, then re-connections of ovn-controllers (slaves are read-only), further peaks of load on DBs, and at the end it could lead to snowball effect.

We should bump the default value in puppet to 60 seconds and provide an option to change it in the future from THT.
Comment 7 errata-xmlrpc 2020-03-10 11:22:02 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:0760