OSA repo is willing to pin to specific ovs/ovn version in stable releases:

https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/917192

While we do intermediate updates in ovs/ovn during stable RDO releases lifecycle (as they are usually longer that ovs/ovn and they should be backwards compatible), I think it's legit that deployment tools want to pin to specific versions.

we use rdo-openvswitch wrapper to manage the upgrade case, we should also ensure that the downgrade case work. I've tested that it works in the ovs case, but not in the ovn one.