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

Bug 1638021

Summary: [Deployment] Need to default inactivity probe to 180s for OVSDB with ODL
Product: Red Hat OpenStack Reporter: Tim Rozet <trozet>
Component: openstack-tripleo-heat-templatesAssignee: Tim Rozet <trozet>
Status: CLOSED ERRATA QA Contact: Noam Manos <nmanos>
Severity: low Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: jchhatba, mariel, mburns, mkolesni, sgaddam
Target Milestone: z4Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: Deployment
Fixed In Version: openstack-tripleo-heat-templates-8.0.7-11.el7ost Doc Type: Bug Fix
Doc Text:
Previously, the inactivity probe timer for Open vSwitch from ODL was insufficient for larger-scale deployments, which caused the ODL L2 agents to appear as offline after the inactivity time lapsed. This bug fix increases the default inactivity probe timer duration and adds the capability to configure the timer in the Director using the `OpenDaylightInactivityProbe` heat parameter. Default value is 180 seconds.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-16 17:55:03 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: 1609037    
Bug Blocks:    

Description Tim Rozet 2018-10-10 13:46:26 UTC
Now that configuration is exposed to modify the inactivity probe timer for OVSDB in ODL via puppet-opendaylight, we now need to default the value for our deployments to be 180s.

Comment 16 errata-xmlrpc 2019-01-16 17:55:03 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-2019:0068