Bug 1433255 - Restarting dhcp-agent in large environment causes the agent to report down for extended time while namespaces are being re-manageed
Summary: Restarting dhcp-agent in large environment causes the agent to report down fo...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 9.0 (Mitaka)
Assignee: Daniel Alvarez Sanchez
QA Contact: Alexander Stafeyev
URL:
Whiteboard:
Depends On: 1339364 1433256
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-17 08:20 UTC by Daniel Alvarez Sanchez
Modified: 2020-04-15 15:30 UTC (History)
12 users (show)

Fixed In Version: openstack-neutron-8.3.0-5.el7ost
Doc Type: Bug Fix
Doc Text:
Previously, because of the way the initial sync was done after starting the DHCP agent, periodic reports were not sent until the sync completed. In large environments this can be a lengthy process, and the lack of status reports during this process caused the agent to be marked as DOWN. This fix allows periodic reports to be sent during the DHCP agent initial sync, so it won't be marked as DOWN. It also addresses a bug which caused the initial sync to be performed twice, so the setup time has been halved.
Clone Of: 1339364
Environment:
Last Closed: 2017-03-30 19:35:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0856 0 normal SHIPPED_LIVE openstack-neutron bug fix advisory 2017-03-30 23:34:33 UTC

Comment 7 errata-xmlrpc 2017-03-30 19:35:52 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-2017:0856
Note You need to log in before you can comment on or make changes to this bug.