Bug 1761397 - external gateway connectivity lost when adding external subnets
Summary: external gateway connectivity lost when adding external subnets
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: ffernand
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On: 1761389 1761400 1761419
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-14 10:40 UTC by ffernand
Modified: 2019-10-14 11:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1761389
Environment:
Last Closed: 2019-10-14 11:34:41 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1843485 0 None None None 2019-10-14 10:40:48 UTC
OpenStack gerrit 688002 0 None MERGED Do not lose router logical port upon subnet add on the external net 2020-02-13 16:56:52 UTC

Description ffernand 2019-10-14 10:40:48 UTC
+++ This bug was initially created as a clone of Bug #1761389 +++

Description of problem:

If we attach a subnet to that external network afterwards, the northbound
database loses that logical port, together with the row in the gateway_chassis table.

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

How reproducible:
Always

Steps to Reproduce:

openstack network create public --external --default --provider-network-type vlan --provider-physical-network tenant --provider-segment 1099

openstack router create myrouter

EXT_NET_ID=$(openstack network show public -f value -c id)
openstack router set --external-gateway $EXT_NET_ID myrouter

Actual results:

We lose connectivity on all external subnets, because the router logical port is lost

Expected results:

User should be able to set subnets after creating and attaching external networks to router


Additional info:

See launchpad for more details on what the sequence of events cause this.

Comment 1 ffernand 2019-10-14 11:34:41 UTC
Not worth fixing in OSP 14, since that is EOL


Note You need to log in before you can comment on or make changes to this bug.