Comment 3 for bug 1784083

When the `neutron-bgp-dragent` service on the `neutron-dynamic-routing` unit gets ready before the `neutron-server` service on the `neutron-api` unit, it will start sending messages it will receive no reply on. These show up as MessageTimeout Tracebacks in the `neutron-bgp-dragent` log.

Some times the `neutron-bgp-dragent` does not get updates even after the `neutron-server` service is available and the MessageTimeout Tracebacks subsides.

Removing the speaker from the agent and adding it back resolves the issue.

I believe this error condition must be in Neutron itself. While we figure out exactly what is going on I propose we add a workaround to the test for the `neutron-dynamic-routing` charm.