Description of problem:
OVN migration script returns non-zero exit code due to deprecated options causing CI job to fail

Ansible failed only on one node - controller-0 in my case

PLAY RECAP *********************************************************************
compute-0                  : ok=26   changed=18   unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   
compute-1                  : ok=26   changed=18   unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   
controller-0               : ok=20   changed=13   unreachable=0    failed=1    skipped=0    rescued=0    ignored=0   
controller-1               : ok=26   changed=18   unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   
controller-2               : ok=26   changed=18   unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   
localhost                  : ok=52   changed=40   unreachable=0    failed=0    skipped=8    rescued=0    ignored=0   
networker-0                : ok=28   changed=20   unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   
networker-1                : ok=28   changed=20   unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   
networker-2                : ok=28   changed=20   unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   



(undercloud) [stack@undercloud-0 ovn_migration]$ cat  ~/ansible-errors.json
{"controller-0": [["Sync neutron db with OVN db (container) - Run 1", {"msg": "non-zero return code", "cmd": ["podman", "exec", "9e464d5df533", "neutron-ovn-db-sync-util", "--config-file", "/etc/neutron/neutron.conf", "--config-file", "/etc/neutron/plugins/ml2/ml2_conf.ini", "--ovn-neutron_sync_mode", "migrate"], "stdout": "", "stderr": "Deprecated: Option \"vif_type\" from group \"ovn\" is deprecated for removal (The port VIF type is now determined based on the OVN chassis information when the port is bound to a host.).  Its value may be silently ignored in the future.\nDeprecated: Option \"ovn_l3_mode\" from group \"ovn\" is deprecated for removal (This option is no longer used. Native L3 support in OVN is always used.).  Its value may be silently ignored in the future.\nError: non zero exit code: 1: OCI runtime error", "rc": 1, "start": "2021-08-09 11:48:13.440754", "end": "2021-08-09 11:48:37.412970", "delta": "0:00:23.972216", "changed": true, "invocation": {"module_args": {"_raw_params": "podman exec \"9e464d5df533\" neutron-ovn-db-sync-util --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --ovn-neutron_sync_mode migrate", "warn": true, "_uses_shell": false, "stdin_add_newline": true, "strip_empty_ends": true, "argv": null, "chdir": null, "executable": null, "creates": null, "removes": null, "stdin": null}}, "stdout_lines": [], "stderr_lines": ["Deprecated: Option \"vif_type\" from group \"ovn\" is deprecated for removal (The port VIF type is now determined based on the OVN chassis information when the port is bound to a host.).  Its value may be silently ignored in the future.", "Deprecated: Option \"ovn_l3_mode\" from group \"ovn\" is deprecated for removal (This option is no longer used. Native L3 support in OVN is always used.).  Its value may be silently ignored in the future.", "Error: non zero exit code: 1: OCI runtime error"], "_ansible_no_log": false}]]}





Version-Release number of selected component (if applicable):
RHOS-16.1-RHEL-8-20210804.n.0
python3-networking-ovn-7.3.1-1.20210714143305.4e24f4c.el8ost.noarch
python3-networking-ovn-migration-tool-7.3.1-1.20210714143305.4e24f4c.el8ost.noarch

How reproducible:
Tried OVN migration on OSP16.1 puddle RHOS-16.1-RHEL-8-20210804.n.0 and the issue happened. No more attempts done with this puddle.

Steps to Reproduce:
1. Deploy ML2OVS environment
2. Run ML2OVS to ML2OVN migration using the official documentation. Alternative option is to run corresponding downstream CI job.


Actual results:
ovn migration script returns a non-zero code

Expected results:
ovn migration script completes without errors

Additional info: