Comment 7 for bug 1353953
Revision history for this message
| Ben Nemec (bnemec) wrote Re: guest instance ping timeout on overcloud (Upstream CI failure) | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
Okay, so the sequence of events from what I can see goes like this:
Successful run
* os-collect-config runs
* l3-agent starts, sends rpc, dies because neutron-server isn't available to respond
* neutron-server starts
* os-collect-config runs again
* l3-agent starts, sends rpc, gets response from neutron-server that is still running from previous o-c-c run
* neutron-server restarts with no ill effects
* happiness
Unsuccessful run
* os-collect-config runs
* l3-agent starts, sends rpc, dies same as above
* neutron-server starts
* For whatever reason os-collect-config doesn't run a second time, so l3-agent is never restarted with neutron-server running and thus overcloud networking is hosed