The activator for netshell-controller depends on the activator for netshell-odl-mdsal already having been run. In some cases there is a race condition on the two activators, with the result that netshell-controller is unable to install a callback handler to process PACKET_IN events, and the multi-point VPN can't learn about new hosts via their broadcast packets.
A workaround was the delay the startup of netshell-controller, but this doesn't seem to work all of the time, probably due to timing on different platforms. A real fix is to actually have the netshell-controller activator check the state of the operation requiring netshell-odl-mdsal to be sure that it actually completed correctly.
The activator for netshell-controller depends on the activator for netshell-odl-mdsal already having been run. In some cases there is a race condition on the two activators, with the result that netshell-controller is unable to install a callback handler to process PACKET_IN events, and the multi-point VPN can't learn about new hosts via their broadcast packets.
A workaround was the delay the startup of netshell-controller, but this doesn't seem to work all of the time, probably due to timing on different platforms. A real fix is to actually have the netshell-controller activator check the state of the operation requiring netshell-odl-mdsal to be sure that it actually completed correctly.
Tested fix in hand as I'm filing this issue.