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

Bug 1433255

Summary: Restarting dhcp-agent in large environment causes the agent to report down for extended time while namespaces are being re-manageed
Product: Red Hat OpenStack Reporter: Daniel Alvarez Sanchez <dalvarez>
Component: openstack-neutronAssignee: Daniel Alvarez Sanchez <dalvarez>
Status: CLOSED ERRATA QA Contact: Alexander Stafeyev <astafeye>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.0 (Mitaka)CC: amuller, ccollett, chrisw, dalvarez, ekuris, jmelvin, majopela, nyechiel, oblaut, ragiman, srevivo, yfried
Target Milestone: ---Keywords: RFE, Triaged, Unconfirmed, ZStream
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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.
Story Points: ---
Clone Of: 1339364 Environment:
Last Closed: 2017-03-30 19:35:52 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: 1339364, 1433256    
Bug Blocks:    

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