Only one of multiple, simultaneous RunInstances calls succeeds if issued immediately after starting nova-network
Bug #733216 reported by
Soren Hansen
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
lp://staging/~soren/nova/only-start-one-dnsmasq
- Vish Ishaya (community): Approve
- Matt Dietz (community): Approve
-
Diff: 10 lines (+1/-0)1 file modifiednova/network/linux_net.py (+1/-0)
lp://staging/~ntt-pf-lab/nova/only-start-one-radvd
- Vish Ishaya (community): Approve
- Soren Hansen (community): Approve
- Matt Dietz: Pending requested
-
Diff: 10 lines (+1/-0)1 file modifiednova/network/linux_net.py (+1/-0)
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in nova: | |
status: | Confirmed → In Progress |
assignee: | nobody → Soren Hansen (soren) |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → 2011.2 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Same thing will happen for update_ra which is for IPv6). /code.launchpad .net/~ntt- pf-lab/ nova/only- start-one- radvd
So, we would like to send our code.
https:/