ovs quantum agent appears to stop responding after some time
Bug #1044135 reported by
Naveen Joy
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Critical
|
Gary Kotton |
Bug Description
Soon after starting the agent process (say after about 3 - 5 min) , the OVS quantum agent appears to stop responding. The agent was also not logging to the log_file configured in its .ini file. Therefore, I ran the agent from the command line and grabbed its output till the point it appeared to hang and not respond. When the VM ports are created, they are not bound to their vlan at this point. Please find attached data. Let me know if you need anything else.
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
milestone: | folsom-rc1 → 2012.2 |
To post a comment you must log in.
Was noticing something like this while testing last night, but hadn't
gotten around to determining if it was in master or just the branch I
was testing.
Are you seeing this even if rpc = False? I noticed this only when my
settings got reset to make rpc = True, though I haven't investigated
it enough to know if that is the rpc flag is just a coincidence.
Another possible correlation I've noticed is that it occurs when I use
a script to spin up multiple VMs in succession, possibly suggesting
some kind of race/timing issue. Does that match your use case?
p.s. moving this to 'confirmed', as i've seen something like it as well, and so think its worthy of investigation.