Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2108212

Summary: [OSP17] During OVN migration workload VMs became not reacheable via IPv6
Product: Red Hat OpenStack Reporter: Roman Safronov <rsafrono>
Component: openstack-tripleo-heat-templatesAssignee: Miro Tomaska <mtomaska>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: medium Docs Contact: James Smith <jamsmith>
Priority: high    
Version: 17.0 (Wallaby)CC: aruffin, averdagu, bcafarel, chrisw, ekuris, fpalin, jamsmith, joflynn, jpretori, jschluet, lsvaty, mariel, mburns, mtomaska, pgrist, scohen
Target Milestone: z2Keywords: Automation, Triaged
Target Release: 17.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-tripleo-14.2.3-17.1.20231102190827.40278e1.el9ost openstack-tripleo-heat-templates-14.3.1-17.1.20231103010821.e7c7ce3.el9ost Doc Type: Bug Fix
Doc Text:
This update fixes an issue that disrupted connection to instances over IPv6 during migration from the OVS mechanism driver to the OVN mechanism driver. + Now you can migrate from OVS to OVN with IPv6 without experiencing the instance connection disruption.
 Story Points: ---
Clone Of:
: 2254412 (view as bug list) Environment:
Last Closed: 2024-01-16 14:31:53 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:

Description Roman Safronov 2022-07-18 15:29:19 UTC 
Description of problem:
Workload VM stops to respond to IPv6 address during OVN migration

Version-Release number of selected component (if applicable):
RHOS-17.0-RHEL-9-20220714.n.1

How reproducible:
happened on most osp17 ovs2ovn downstream jobs, 4 out of 5, except dvr2dvr 

Steps to Reproduce:
1.Deploy HA environment (3 controllers + 2 compute nodes) with ML2/OVS backend
2.Create a workload, internal network, router, security groups allowing ping/ping6 and ssh. Connect internal network to the external through the router.
3.Run infinite IPv6 ping to VM ipv6 addresses and IPv4 ping to the VM IPv4 address
4. Start ML2/OVS to ML2/OVN migration procedure according to the official documentation
  https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html/migrating_the_networking_service_to_the_ml2ovn_mechanism_driver/migrating-ml2ovs-to-ovn

Actual results:
The VM IPv4 address (FIP) responds to ping from the external network - this is CORRECT
The VM IPv6 address stops responding to ping6 from the external network, very high packet loss reported (see below) - BAD

--- 2001:db8:cafe:1:f816:3eff:fe91:7627 ping statistics ---
2356 packets transmitted, 186 received, 92.1053% packet loss, time 2407621ms



Expected results:
The VM IPv4 address (FIP) responds to ping from the external network
The VM IPv6 address responds to ping6 from the external network


Additional info:
Comment 20 Eran Kuris 2023-06-18 11:41:54 UTC 
Raising the blocker flag as its an automation blocker
Comment 62 Roman Safronov 2023-11-30 10:02:40 UTC 
Verified that the issue does not occur on RHOS-17.1-RHEL-9-20231122.n.1 with openstack-tripleo-heat-templates-14.3.1-17.1.20231103010823.el9ost.noarch, puppet-tripleo-14.2.3-17.1.20231102190827.40278e1.el9ost.noarch
Comment 75 errata-xmlrpc 2024-01-16 14:31:53 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 17.1.2 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-2024:0209
Comment 76 Terry Wilson 2024-03-26 21:16:09 UTC 
*** Bug 2247087 has been marked as a duplicate of this bug. ***
Comment 77 Red Hat Bugzilla 2024-07-25 04:25:06 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days