Following these steps: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15/html-single/networking_with_open_virtual_network/index#migrating-ml2ovs-to-ovn We were unable to switch from OVS to the OVN mechanism driver due to the issue described below: https://opendev.org/openstack/tripleo-common/src/branch/master/tripleo_common/update.py --- if current_driver and new_driver and current_driver != new_driver: msg = ("Unable to switch from {} to {} neutron " "mechanism drivers on upgrade. Please consult the " "documentation.").format(current_driver, new_driver) return msg ---- As a result, removed `return msg` and was able to progress past this point. For more information, see https://opendev.org/openstack/tripleo-common/commit/379f886119727fe440e384234db53f48730e27ad
Martin, can you describe which step/command is failing for you? Is it "ovn_migration.sh start-migration" ?
Hi Harald, for comment 1: would you remember if this occurred under `ovn_migration.sh start-migration`?
(In reply to Martin Lopes from comment #2) > Hi Harald, for comment 1: would you remember if this occurred under > `ovn_migration.sh start-migration`? Yes, this happend at the `ovn_migration.sh start-migration` step. That step does: "Updates the overcloud stack to deploy OVN alongside reference implementation services using the temporary bridge br-migration instead of br-int.", which fails due to the check added in https://opendev.org/openstack/tripleo-common/commit/379f886119727fe440e384234db53f48730e27ad. I think that check could look for 'br-migration' in case 'current_driver and new_driver and current_driver != new_driver' and let the update continue if 'br-migration' is there. -- Harald
Verified on 16.0-RHEL-8/RHOS_TRUNK-16.0-RHEL-8-20200213.n.1 with python3-networking-ovn-7.1.0-0.20200204065607.57ac389.el8ost.noarch Verified that migration process is not blocked on this stage and proceeds till the end (in case workaround for https://bugzilla.redhat.com/show_bug.cgi?id=1804376 is applied)
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, 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-2020:0654