Comment 7 for bug 999698

Ok, thanks. I'm still thinking that what's happening is that nova-network is reading the message off the queue before it restarts, even when the order is changed in your loop. The service restarts must be happening asyncrhonously.

Regarding the service stopping part ... this error is happening in service startup code, so I think it's pretty much just an expected failure if nova-compute can't talk to nova-network during startup.

There is a patch on gerrit right now that may fix this scenario.

https://review.openstack.org/#/c/6694/

I haven't reviewed the patch yet, but based on the description, it sounds like it should make it so nova-network can't restart wihle it's in the middle of processing the request from nova-compute. Mind giving that patch a try?