Bug 1943605 - Geneve allocation is not update during migration from ml2/ovs to ovn
Summary: Geneve allocation is not update during migration from ml2/ovs to ovn
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z7
: 16.1 (Train on RHEL 8.2)
Assignee: Jakub Libosvar
QA Contact: Roman Safronov
URL:
Whiteboard:
Depends On:
Blocks: 2003708
TreeView+ depends on / blocked
 
Reported: 2021-03-26 15:06 UTC by Jakub Libosvar
Modified: 2023-01-20 10:14 UTC (History)
7 users (show)

Fixed In Version: python-networking-ovn-7.3.1-1.20210713093309.4e24f4c.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2003708 (view as bug list)
Environment:
Last Closed: 2021-12-09 20:18:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 784352 0 None MERGED ovn-migration: Introduce migrate mode to DB sync tool 2021-05-14 10:01:24 UTC
Red Hat Issue Tracker OSP-1428 0 None None None 2021-11-18 11:31:16 UTC
Red Hat Product Errata RHBA-2021:3762 0 None None None 2021-12-09 20:18:54 UTC

Description Jakub Libosvar 2021-03-26 15:06:39 UTC 
Description of problem:
After migration is finished, geneve vni allocations are all empty. It means newly created networks may have same segmentation id as existing migrated networks.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 11 Roman Safronov 2021-08-01 07:00:02 UTC 
Verified on RHOS-16.1-RHEL-8-20210727.n.1 with python3-networking-ovn-7.3.1-1.20210714143305.4e24f4c.el8ost.noarch
Created several vxlan networks before migration to OVN, migrated to OVN, then created several new networks and verified that after migration all geneve networks (old and newly created) have unique segmentation ids.
Comment 22 errata-xmlrpc 2021-12-09 20:18:25 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.