fdio noha: Workaround tap MAC generation issues 47/69547/1
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Tue, 14 Jan 2020 13:11:17 +0000 (14:11 +0100)
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Tue, 14 Jan 2020 13:11:17 +0000 (14:11 +0100)
commitfdf80205c24041fdf143269b128bf479401d832c
treec78bcc6fca94500f1bf3a1a270795fc037edec47
parentf03bfd30206c1d21de7e5c9ef2f6ed79f6ee13f4
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>
mcp/reclass/classes/cluster/mcp-fdio-noha/openstack/init.yml