Comment 6 for bug 1857016

Hi Terry,

Thank you for reporting this bug.

Do you know a way to reproduce this error? If yes, please describe the steps here.

The proposed code change is in a file that seems to be migrated to the neutron repo already:

neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/commands.py

How do we track changes to the ovn codebase during the networking-ovn -> neutron migration? My naive expectation would have been that if the file was migrated to neutron then changes only should be made to it in neutron and no longer in networking-ovn. How do we make sure we don't lose changes like the proposed one?

Unless you are 1000% sure that your proposed fix to master will merge without any change, it usually spares you some work if you only upload backports after the fix merged to master.