Ideally config-schema container restart should not trigger any configuration changes on Fabric devices. However, because of a bug in old contrail versions, active schema restart triggers invalid bgp_neighbor config update on some fabric devices. We will see the bgp neighbor being sent as leaf loopback IP when there should not be any bgp neighbor send for leaf. This bug is fixed in Contrail version 21.4L4 version.
Note: As per design, config containers like config-schema, svc-monitor etc may get restarted whenever it loses connectivity to zookeeper.
Invalid bgp_neighbor config update on fabric devices triggered by active config-schema restart. On some fabric devices we will see the bgp neighbor being sent as leaf loopback IP when there should not be any bgp neighbor send for leaf.
This bug is fixed in Contrail version 21.4L4 version. This bug will not cause much issues since the "Invalid BGP configuration" which got pushed will get automatically removed immediately by next netconf push from contrail.