Workaround ovs bug that resets hostname with add command

In UCA repo for Antelope OVS version to 3.1.0 is used that is affected
by the bug [1]. Until that is fixed, we're masking ovs-record-hostname
service.

[1] https://bugs.launchpad.net/cloud-archive/+bug/2017757

Change-Id: Iead62b464a68bbfcffb0e79a4db004760287e89b

tasks/providers/ovn_config.yml

@@ -63,6 +63,20 @@
     - ansible_facts['pkg_mgr'] == 'dnf'
     - neutron_services['neutron-ovn-controller']['group'] in group_names
 
+# NOTE(noonedeadpunk): ovs 3.1.0 installed from UCA for Antelope now has a bug where
+#                      `ovs-vsctl add` acts exactly as `set` and resets hostname
+#                      so we mask service that executes that part to prevent failures
+#                      https://bugs.launchpad.net/cloud-archive/+bug/2017757
+- name: Mask setting OVS hostname service
+  service:
+    name: ovs-record-hostname
+    enabled: false
+    state: stopped
+  when:
+    - ansible_facts['pkg_mgr'] == 'apt'
+    - ansible_facts['distribution_version'] == '22.04'
+    - neutron_services['neutron-ovn-controller']['group'] in group_names
+
 - name: Ensure ovn-northd service is started and enabled
   systemd:
     name: "{{ neutron_ovn_northd_service_name }}"