Bug 1780381

Summary:	Loadbalancer missing logical switch association
Product:	Red Hat OpenStack	Reporter:	ffernand <ffernand>
Component:	python-networking-ovn	Assignee:	ffernand <ffernand>
Status:	CLOSED ERRATA	QA Contact:	Roman Safronov <rsafrono>
Severity:	medium	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	apevec, jschluet, lhh, majopela, njohnston, scohen
Target Milestone:	z11	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-networking-ovn-4.0.3-17.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1780383 (view as bug list)		Environment:
Last Closed:	2020-03-10 11:26:15 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:
Bug Blocks:	1780383

Description ffernand 2019-12-05 20:14:05 UTC

Description of problem:

Network id info missing in Logical Router Port

For applications like Octavia, it is necessary to know the network associated to a
given logical router port. Such information can be easily provided via the LRP's
external_ids column.

Note that this is already done in Stein and newer releases; so this issue is only applicable to Rocky and [stopping at] Queens.


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


How reproducible:


Use Octavia with OVN


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Roman Safronov 2020-02-16 14:34:27 UTC

Verified on puddle 13.0-RHEL-7/2020-02-14.1 with python-networking-ovn-4.0.4-2.el7ost.noarch.rpm   

Created a router connected to external and internal networks and verified that each logical_router_port contains associated network name in form "neutron:network_name"="neutron-<NEUTRON NET ID>" in external_ids column

Comment 6 errata-xmlrpc 2020-03-10 11:26:15 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-2020:0770

Comment 7 Red Hat Bugzilla 2023-09-14 05:48:15 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days