7.26beta [development] is released!

Thank you for the detailed logs, they show exactly what is happening, and it is working as designed rather than a fault.

cmr-bridge is a CMR-managed object (the Y flag). CMR creates it, owns it, and rebuilds it (removes and re-creates it under the same name but a new internal ID) whenever it reprovisions the client. A reprovision is triggered by controller-side changes enabling/disabling the CMR server, or disabling/enabling a VLAN rule. In your log that is the /cmr vlan set *9 disabled=yes → disabled=no at 09:56 (and the new rule *A): that reprovisions every managed client.

The loop comes from your own management configuration sitting on top of that managed bridge:

  • cmr_vlan_10 (a VLAN interface) + its DHCP client are attached to cmr-bridge, and this is also the path the client uses to reach the controller.
  • When CMR rebuilds cmr-bridge, your cmr_vlan_10 is left pointing at the old, removed bridge and goes invalid, so the client loses its connection to the controller.
  • Your netwatch script re-attaches cmr_vlan_10 to the new cmr-bridge, the client reconnects, and anything that triggers another reprovision starts the cycle again. That is the remove *9 → add *A → disconnect → re-attach → connect → remove *A → add *B … you see.

Configuration you add on top of cmr-bridge (VLAN interfaces, DHCP clients, IP addresses) is not supported: CMR does not track objects it did not create, so they break whenever it rebuilds the bridge.

To fix it:

  1. Put the client's management interface on a port that CMR does not manage not on cmr-bridge. Give it its own VLAN/IP there, and the netwatch re-attach workaround is no longer needed.
  2. Keep the VLAN configuration of CMR-managed ports in the controller's /cmr vlan rules, not in manual interfaces on the client.

To confirm the mechanism: a plain link flap or reconnect, with no controller-side change, does not rebuild cmr-bridge the bridge is only rebuilt on a reprovision. So once your management path is off cmr-bridge, the rebuilds will no longer disturb it.

Either way probably we might add some improvements in the future, that could work on such setups even more smoothly.