Only one of multiple, simultaneous RunInstances calls succeeds if issued immediately after starting nova-network

Bug #733216 reported by Soren Hansen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Soren Hansen

Bug Description

When I reinstall my test environment and start running instances on it, usually only one of the first batch succeeds, the rest are stuck in "networking" state. After that everything is fine and I can run many concurrent RunInstances calls.

I'm not completely sure, but my working hypothesis is each thread finds that dnsmasq isn't running, and then tries to start it, all at roughly the same time. Only one succeeds, though, because only one process can listen on the socket at any given time.

Related branches

Thierry Carrez (ttx)
Changed in nova:
importance: Undecided → Medium
status: New → Confirmed
Soren Hansen (soren)
Changed in nova:
status: Confirmed → In Progress
assignee: nobody → Soren Hansen (soren)
Changed in nova:
status: In Progress → Fix Committed
Revision history for this message
Nachi Ueno (nati-ueno) wrote :

Same thing will happen for update_ra which is for IPv6).
So, we would like to send our code.
https://code.launchpad.net/~ntt-pf-lab/nova/only-start-one-radvd

Thierry Carrez (ttx)
Changed in nova:
milestone: none → 2011.2
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.