libvirt tests fail due to too many connections
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Vish Ishaya |
Bug Description
Our libvirt unit tests can open too many connections to libvirt and cause a failure:
ft533.70: nova.tests.
stderr
stdout
pythonlogging:
Loading network driver 'nova.network.
Loading network driver 'nova.network.
Loading network driver 'nova.network.
URI qemu:///system does not support events
Loading network driver 'nova.network.
Connection to libvirt failed: Cannot recv data: Connection reset by peer
Traceback (most recent call last):
File "/home/
return libvirt.
File "/usr/lib/
if ret is None:raise libvirtError(
libvirtError: Cannot recv data: Connection reset by peer
URI qemu:///system does not support events
Connection to libvirt failed: Cannot write data: Broken pipe
Traceback (most recent call last):
File "/home/
return libvirt.
File "/usr/lib/
if ret is None:raise libvirtError(
libvirtError: Cannot write data: Broken pipe
URI qemu:///system does not support events
}}}
Traceback (most recent call last):
File "/home/
expect_
File "/home/
rescue=rescue)
File "/home/
disk_info, rescue, block_device_info)
File "/home/
guest.cpu = self.get_
File "/home/
cpu = self.get_
File "/home/
caps = self.get_
File "/home/
xmlstr = self._conn.
AttributeError: 'NoneType' object has no attribute 'getCapabilities'
Changed in nova: | |
importance: | Undecided → High |
assignee: | nobody → Vish Ishaya (vishvananda) |
tags: | added: libvirt |
Changed in nova: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-1 → 2013.2 |
Was just looking at this.
Looks like _connect really shouldn't return None since so much of the rest of the code depends on it being present (and we probably don't want to add guards everywhere).