To Reproduce Steps to reproduce the behavior:

1. 
   computes nodes are correctly added to neutron aggregates, that's why I believe there is an issue on how edpm is configuring/bootstrapping ovn during fresh install.

Bug impact

• Please provide information on the impact of this bug to the end user.

Known workaround

• 
  As soon as I removed and readded bridge mapping, compute were correctly added to all neutron provider aggregates

Additional context

Follow up from https://issues.redhat.com/browse/OSPRH-8988

There were two fixes https://review.opendev.org/c/openstack/neutron/+/935990 and https://review.opendev.org/c/openstack/neutron/+/942156

[10:30:08 ]$ oc rsh neutron-965c8fc8f-288tk rpm -qa | grep openstack-neutron
Defaulted container "neutron-api" out of: neutron-api, neutron-httpd
openstack-neutron-common-22.2.2-18.0.20250327134804.51e19bb.el9ost.noarch
openstack-neutron-22.2.2-18.0.20250327134804.51e19bb.el9ost.noarch
openstack-neutron-ml2-22.2.2-18.0.20250327134804.51e19bb.el9ost.noarch
openstack-neutron-rpc-server-22.2.2-18.0.20250327134804.51e19bb.el9ost.noarch

[10:30:25 ]$ oc rsh neutron-965c8fc8f-288tk grep -IErin 'service_plugins .*segments' /etc/neutron/neutron.conf.d/
Defaulted container "neutron-api" out of: neutron-api, neutron-httpd
/etc/neutron/neutron.conf.d/01-neutron.conf:7:service_plugins = qos,ovn-router,trunk,segments,port_forwarding,log
/etc/neutron/neutron.conf.d/02-neutron-custom.conf:3:service_plugins = qos,ovn-router,trunk,segments,port_forwarding,log,placement