Bug 1692156 - Instance not receiving IP on DVR enabled tenant network due to missing flows
Summary: Instance not receiving IP on DVR enabled tenant network due to missing flows
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 13.0 (Queens)
Hardware: x86_64
OS: Linux
high
high
Target Milestone: z7
: 13.0 (Queens)
Assignee: Brian Haley
QA Contact: Candido Campos
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-24 19:05 UTC by David Hill
Modified: 2019-07-10 13:02 UTC (History)
8 users (show)

Fixed In Version: openstack-neutron-12.0.5-13.el7ost
Doc Type: Bug Fix
Doc Text:
This update resolves an issue in large-scale neutron deployments with Distributed Virtual Routing (DVR), where instances lost IP addresses after a restart of the Layer 2 openvswitch agent.
Clone Of:
Environment:
Last Closed: 2019-07-10 13:02:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1813703 0 None None None 2019-03-25 13:32:32 UTC
OpenStack gerrit 645406 0 'None' MERGED More accurate agent restart state transfer 2021-02-02 08:26:40 UTC
Red Hat Knowledge Base (Solution) 4004951 0 None None None 2019-03-24 19:12:32 UTC
Red Hat Product Errata RHBA-2019:1744 0 None None None 2019-07-10 13:02:12 UTC

Description David Hill 2019-03-24 19:05:11 UTC 
Description of problem:
Instance not receiving IP on DVR enabled tenant network due to missing flows

Backport commits listend in https://bugs.launchpad.net/neutron/+bug/1813703 to OSP13

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create VMs with DVR networks up until some doesn't receive an IP from the DHCP server
2.
3.

Actual results:
VMs are failing to receive an IP

Expected results:
VMs should receive an IP

Additional info:
Comment 21 errata-xmlrpc 2019-07-10 13:02:00 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:1744
Note You need to log in before you can comment on or make changes to this bug.