Description of problem: OVNMetadataEnabled value isn't applied during an overcloud deployment Version-Release number of selected component (if applicable): (undercloud) [stack@undercloud-0 ~]$ rpm -qa | grep heat-templates openstack-tripleo-heat-templates-11.3.2-0.20200405044623.ec9970c.el8ost.noarch Steps to Reproduce: network-environment.yaml parameter_defaults: ... OVNMetadataEnabled: true Actual results: [ovn] ovn_nb_connection=tcp:172.17.1.129:6641 ovn_sb_connection=tcp:172.17.1.129:6642 Expected results: [ovn] ovn_nb_connection=tcp:172.17.1.129:6641 ovn_sb_connection=tcp:172.17.1.129:6642 ovn_metadata_enabled: true
What appears to be happening is that ML2 ansible tripleo config is pulling in basic neutron ml2 plugin configuration and missing the OVN templates. Only the values set in the OVN controller templates are being set because it is separate from the core plugin/API container. I think the networking-ansible integration needs to be revisited either that it is truly additive or its "parent" configuration can be parameterized.
Verified on 16.1-RHEL-8/RHOS-16.1-RHEL-8-20200625.n.0 with openstack-tripleo-heat-templates-11.3.2-0.20200616081529.396affd.el8ost.noarch.rpm Verified that ovn_metadata_enabled=True is set in ml2_conf.ini
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:3148