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

Bug 1565228

Summary: [Netvirt] One Instance doesn't get an IP after when a network is added to a router
Product: Red Hat OpenStack Reporter: Itzik Brown <itbrown>
Component: opendaylightAssignee: Aswin Suryanarayanan <asuryana>
Status: CLOSED ERRATA QA Contact: Itzik Brown <itbrown>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: aadam, mkolesni, nyechiel
Target Milestone: betaKeywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: odl_netvirt
Fixed In Version: opendaylight-8.0.0-9.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
N/A
Last Closed: 2018-06-27 13:50: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:
Attachments:
Description Flags
Compute 0 flows dump
none
Compute 0 flows dump
none
Compute 1 flows dump none

Description Itzik Brown 2018-04-09 16:38:27 UTC
Description of problem:
In the following scenario the instance doesn't get an IP.

Create a router
Create a network
Create a subnet 
Add the subnet to the router
Launch an instance

Version-Release number of selected component (if applicable):
opendaylight-8.0.0-5.el7ost.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Itzik Brown 2018-04-10 12:14:50 UTC
Created attachment 1419860 [details]
Compute 0 flows dump

Comment 2 Itzik Brown 2018-04-10 12:15:46 UTC
Created attachment 1419862 [details]
Compute 0 flows dump

Comment 3 Itzik Brown 2018-04-10 12:16:22 UTC
Created attachment 1419863 [details]
Compute 1 flows dump

Comment 9 Itzik Brown 2018-05-03 18:00:29 UTC
Checked with:
opendaylight-8.0.0-9.el7ost

Comment 11 errata-xmlrpc 2018-06-27 13:50: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/RHEA-2018:2086