fdio noha: Workaround tap MAC generation issues

systemd 230..241 has issues generating persistent MAC addresses
for bridge/tap/etc network devices, causing trouble for VPP agent
hooking tap devices to the bridges it creates on the fly.

Work around this by disabling the faulty policy, as suggested in [1].

[1] https://github.com/systemd/systemd/issues/3374

Change-Id: I8d568bc0a859256d1493bf9f8261d60943fa60e0
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>

diff --git a/mcp/reclass/classes/cluster/mcp-fdio-noha/openstack/init.yml b/mcp/reclass/classes/cluster/mcp-fdio-noha/openstack/init.yml
index 1e13884..858da65 100644 (file)
--- a/mcp/reclass/classes/cluster/mcp-fdio-noha/openstack/init.yml
+++ b/mcp/reclass/classes/cluster/mcp-fdio-noha/openstack/init.yml
@@ -18,3 +18,13 @@ parameters:
     node_hostname: ${_param:cluster_node01_hostname}
     node_port: 4001
     external_vpp_tap: 'tap0'
+  linux:
+    system:
+      file:
+        /etc/systemd/network/99-default.link:
+          contents: |
+            # Workaround tap/bridge MAC generation issue
+            # https://github.com/systemd/systemd/issues/3374
+            [Link]
+            NamePolicy=kernel database onboard slot path
+            MACAddressPolicy=none