Bug 1960629 - Allowed address pairs aren't populated to the new host with DVR router
Summary: Allowed address pairs aren't populated to the new host with DVR router
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Slawek Kaplonski
QA Contact: Candido Campos
URL:
Whiteboard:
Depends On:
Blocks: 1952464 1963869 1972472
TreeView+ depends on / blocked
 
Reported: 2021-05-14 12:47 UTC by Slawek Kaplonski
Modified: 2021-12-09 20:19 UTC (History)
4 users (show)

Fixed In Version: openstack-neutron-15.2.1-1.20210602143304.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1963869 1972472 (view as bug list)
Environment:
Last Closed: 2021-12-09 20:19:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 791492 0 None None None 2021-05-14 14:12:16 UTC
Launchpad 1928466 0 None None None 2021-05-14 12:47:27 UTC
OpenStack gerrit 791492 0 None NEW [DVR] Send allowed address pairs info to the L3 agents 2021-05-18 14:56:58 UTC
Red Hat Issue Tracker OSP-3901 0 None None None 2021-11-18 11:32:20 UTC
Red Hat Product Errata RHBA-2021:3762 0 None None None 2021-12-09 20:19:55 UTC

Description Slawek Kaplonski 2021-05-14 12:47:28 UTC
In the DVR routers, neutron-server needs to populate ARP entries also for IPs added to the ports as allowed address pairs. When e.g. new IP is added to the allowed address pairs of the port, it works fine and neutron server sends notification about such new arp entry to the all L3 agents where dvr router is placed.

But in case when new vm plugged to the same router is spawned on completly new compute, or existing vm is migrated to the new compute where dvr router wasn't created before, arp entries for allowed address pairs aren't populated at all.

Comment 24 errata-xmlrpc 2021-12-09 20:19:32 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 (Red Hat OpenStack Platform 16.1.7 (Train) bug fix and enhancement 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-2021:3762


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