Bug 1638021 - [Deployment] Need to default inactivity probe to 180s for OVSDB with ODL
Summary: [Deployment] Need to default inactivity probe to 180s for OVSDB with ODL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: z4
: 13.0 (Queens)
Assignee: Tim Rozet
QA Contact: Noam Manos
URL:
Whiteboard: Deployment
Depends On: 1609037
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-10 13:46 UTC by Tim Rozet
Modified: 2019-01-16 17:55 UTC (History)
5 users (show)

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.
Clone Of:
Environment:
Last Closed: 2019-01-16 17:55:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1797128 0 None None None 2018-10-10 15:02:54 UTC
OpenStack gerrit 615377 0 None None None 2018-11-14 14:10:33 UTC
Red Hat Product Errata RHBA-2019:0068 0 None None None 2019-01-16 17:55:17 UTC

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
Note You need to log in before you can comment on or make changes to this bug.