Bug 1885575 - [RFE] ML2/OVS to ML2/OVN migration tool should be capable of detecting ongoing stack upadate during reruns
Summary: [RFE] ML2/OVS to ML2/OVN migration tool should be capable of detecting ongoin...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 16.1 (Train)
Hardware: All
OS: Linux
low
low
Target Milestone: ga
: ---
Assignee: OSP Team
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-06 12:35 UTC by Jaison Raju
Modified: 2023-07-26 12:05 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-502 0 None None None 2021-11-18 15:14:44 UTC

Description Jaison Raju 2020-10-06 12:35:43 UTC
Description of problem:
It is often noticed in scale environments that ovn migration script in TASK “Updating the overcloud stack with OVN services” takes too long and fail with timeout.

An example of the timeout looks like below:
http://perf1.perf.lab.eng.bos.redhat.com/pub/jaison/upgrades-osp13-16.1.1/osp16/backup/stack/tmux/ml2-ovs_ovn-migration-tmux.log

 sed -n '5876,5878p' ml2-ovs_ovn-migration-tmux.log | less

A rerun of the script fails with error from  TASK “Updating the overcloud stack with OVN services” fails if there is an ongoing config download in progress. “"Config download already in progress with execution id 617bb1ac-e013-4c36-b399-a2deecfa24dd for stack overcloud" .

We need the migration script/playbook to be smart enough to understand if an update is running from past attempt and wait to continue after the stack update is complete.

Comment 4 Gurpreet Singh 2022-09-02 15:11:00 UTC
workaround available. not a blocker for OVN migration


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