Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1651265 - OVN migration tool- we need to add cleanup of pre-migration resource if the migration failed
Summary: OVN migration tool- we need to add cleanup of pre-migration resource if the m...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
Target Milestone: z5
: 16.1 (Train on RHEL 8.2)
Assignee: Jakub Libosvar
QA Contact: Roman Safronov
Depends On:
TreeView+ depends on / blocked
Reported: 2018-11-19 14:58 UTC by Eran Kuris
Modified: 2021-04-07 14:37 UTC (History)
6 users (show)

Fixed In Version: python-networking-ovn-7.2.1-0.20200611111150.18fabca.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-04-07 14:37:06 UTC
Target Upstream Version:

Attachments (Terms of Use)
ovn migration (202.74 KB, text/plain)
2018-11-19 14:58 UTC, Eran Kuris
no flags Details

System ID Private Priority Status Summary Last Updated
Launchpad 1804477 0 None None None 2021-03-25 15:04:24 UTC
OpenStack gerrit 626577 0 None MERGED Pre-cleanup migration resources and fix validation 2021-03-25 15:04:51 UTC

Description Eran Kuris 2018-11-19 14:58:48 UTC
Created attachment 1507272 [details]
ovn migration

Description of problem:
If we are running OVN migration after that pre-migration resources were created in previous  it will create conflicts between the current run and the previous 
 9) (Request-ID: req-7aed8979-4091-42e2-aeec-1a901b2f5e2c)\n+ openstack router create ovn-migration-router-pre\n+ openstack router set --external-gateway public ovn-migration-router-pre\nMore than one Router exists with the name 'ovn-migration-router-pre'.\n+ openstack router add subnet ovn-migration-router-pre ovn-migration-subnet-pre\nMore than one Router exists with the name 'ovn-migration-router-pre'.\n++ openstack floating ip create --port
 ovn-migration-server-port-pre public -c floating_ip_address\n++ grep floating_ip_address\n++ awk '{print $4}'\nError while executing command: ConflictException: 409, {\"NeutronError\": {\"message\": \"Cannot associate floating IP (3717e29a-e9e1-4b53-9da5-a07e4be4ef9c) with port 7a44095a-6153-4fb8-9de7-93077e8104f7 using fixed IP, as that fixed IP already has a floating IP on external network f6855347-fe63-4ff8-9c61-0d09
559d6b0a.\", \"type\": \"FloatingIPPortAlreadyAssociated\", \"detail\": \"\"}}\n+ server_ip=\n+ echo\n+ chmod 0600 /home/stack/ovn_migration/pre_migration_resources/ovn_migration_ssh_key\nchmod: cannot access '/home/stack/ovn_migration/pre_migratio

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.run ovn_migration.sh start-migration  when export VALIDATE_MIGRATION=True
make sure it will be failed
2. after it failed run it again 

Actual results:

Expected results:

Additional info:

Comment 3 Mike Burns 2020-08-26 21:25:21 UTC
This Release is retired.  If this bug is still relevant, please reopen and retarget to an open release.

Comment 5 Jakub Libosvar 2021-03-25 15:07:49 UTC
This has been fixed 3 years ago upstream, any OSP 16.1 version should have the fix available.

Comment 6 Roman Safronov 2021-04-01 13:24:20 UTC
Was verified on RHOS-16.1-RHEL-8-20210323.n.0 with python3-networking-ovn-7.3.1-1.20201114024053.el8ost.noarch and python3-networking-ovn-migration-tool-7.3.1-1.20201114024053.el8ost.noarch.

Verified that in case we rerun ovn migration script while migration workload already exist, the workload objects are removed and then re-created successfully.

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