Bug 1885575

Summary: [RFE] ML2/OVS to ML2/OVN migration tool should be capable of detecting ongoing stack upadate during reruns
Product: Red Hat OpenStack Reporter: Jaison Raju <jraju>
Component: python-networking-ovnAssignee: OSP Team <rhos-maint>
Status: CLOSED WONTFIX QA Contact: Eran Kuris <ekuris>
Severity: low Docs Contact:
Priority: low    
Version: 16.1 (Train)CC: apevec, gurpsing, jlibosva, jraju, lhh, majopela, scohen
Target Milestone: gaKeywords: FutureFeature, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 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