Bug 2073182 - [16.2][OVN migration]Trunk subport connectivity is broken after VM reboot
Summary: [16.2][OVN migration]Trunk subport connectivity is broken after VM reboot
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Arnau Verdaguer
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks: 2052341 2192580
TreeView+ depends on / blocked
 
Reported: 2022-04-07 20:39 UTC by Roman Safronov
Modified: 2023-12-04 17:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2192580 (view as bug list)
Environment:
Last Closed: 2023-12-04 17:29:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-14569 0 None None None 2022-04-07 20:40:10 UTC

Description Roman Safronov 2022-04-07 20:39:35 UTC 
Description of problem:
After rebooting a VM with a trunk port, it's subport connectivity is broken.

Version-Release number of selected component (if applicable):
RHOS-16.2-RHEL-8-20220329.n.2
python3-networking-ovn-7.4.2-2.20220113214853.el8ost.noarch
ovn-2021-21.12.0-11.el8fdp.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Deploy an environment with OVS network backend. 
2. Create 2 VMs, each with a trunk port which has a subport connected to the same network. Make sure that ping between subports is working.
3. Migrate to OVN according to the official documentation. Make sure that ping between subports is still working after the migration.
4. Reboot the VMs, wait until they are up again and try to login into one of the VMs and ping from there a subport of the second VMs.

Actual results:
No response to ping requests

Expected results:
Ping works

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