This bug was initially created as a copy of Bug #2094265 I am copying this bug because: The code provided in 2094265 fixes *deployment* but not update. Creating this bugzilla to track the fix for update. Description of problem: Customer has upgraded one of our rhosp from 16.2.1 to 16.2.2 and during the procedure we saw some impact to the VMs running in there. It seems that it happened during the ovn-controller container refresh where at least some of the VMs experienced connection timeouts. It seems that exactly while following the below step was the one that caused the issue and as mentioned, everything auto-recovered after 60-90 seconds. https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html-single/keeping_red_hat_openstack_platform_updated/index#proc_updating-ovn-controller-container_updating-overcloud Version-Release number of selected component (if applicable): RHOSP 16.2.1 How reproducible: Upgrade from RHOSP 16.2.1 to 16.2.2 Steps to Reproduce: 1. Upgrade 16.2.1 to 16.2.2 Actual results: Upgraded successfully but there VM connectivity drop for 60 - 90 seconds while data plan upgrade. Expected results: successful upgrade without any downtime. Additional info:
Hi, added KCS link. For the doc side of this, @kgilliga we would need a new entry in "Known issues that might block an update" in https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html-single/keeping_red_hat_openstack_platform_updated/index#assembly_updating-the-overcloud_keeping-updated . Something along those lines: "Data plane cut might be experienced when using OVN" To prevent such a cut from happening please run the code associated with the KCS 6990594 before running the ovn controller update.
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.2.5 (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-2023:1763