"error: [Errno 32] Broken pipe" when plugging OVS VIF into an instance
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned |
Bug Description
2017-07-28 08:35:03.006 1542 ERROR os_vif [req-398df22e-
2017-07-28 08:35:03.006 1542 ERROR os_vif Traceback (most recent call last):
2017-07-28 08:35:03.006 1542 ERROR os_vif File "/usr/local/
2017-07-28 08:35:03.006 1542 ERROR os_vif plugin.plug(vif, instance_info)
2017-07-28 08:35:03.006 1542 ERROR os_vif File "/usr/local/
2017-07-28 08:35:03.006 1542 ERROR os_vif self._plug_
2017-07-28 08:35:03.006 1542 ERROR os_vif File "/usr/local/
2017-07-28 08:35:03.006 1542 ERROR os_vif linux_net.
2017-07-28 08:35:03.006 1542 ERROR os_vif File "/usr/local/
2017-07-28 08:35:03.006 1542 ERROR os_vif return self.channel.
2017-07-28 08:35:03.006 1542 ERROR os_vif File "/usr/local/
2017-07-28 08:35:03.006 1542 ERROR os_vif result = self.send_
2017-07-28 08:35:03.006 1542 ERROR os_vif File "/usr/local/
2017-07-28 08:35:03.006 1542 ERROR os_vif self.writer.
2017-07-28 08:35:03.006 1542 ERROR os_vif File "/usr/local/
2017-07-28 08:35:03.006 1542 ERROR os_vif self.writesock.
2017-07-28 08:35:03.006 1542 ERROR os_vif File "/usr/local/
2017-07-28 08:35:03.006 1542 ERROR os_vif tail = self.send(data, flags)
2017-07-28 08:35:03.006 1542 ERROR os_vif File "/usr/local/
2017-07-28 08:35:03.006 1542 ERROR os_vif return self._send_
2017-07-28 08:35:03.006 1542 ERROR os_vif File "/usr/local/
2017-07-28 08:35:03.006 1542 ERROR os_vif return send_method(data, *args)
2017-07-28 08:35:03.006 1542 ERROR os_vif error: [Errno 32] Broken pipe
2017-07-28 08:35:03.006 1542 ERROR os_vif
2017-07-28 08:35:03.007 1542 ERROR nova.virt.
Looking at libvirtd log, there is nothing that would immediately suggest what happened, but for the reference, that's what I see there:
2017-07-28 08:35:03.689+0000: 11804: debug : virThreadJobSet:96 : Thread 11804 (virNetServerHa
2017-07-28 08:35:03.689+0000: 11804: debug : virThreadJobCle
2017-07-28 08:35:03.689+0000: 11807: debug : virThreadJobSet:96 : Thread 11807 (virNetServerHa
2017-07-28 08:35:03.689+0000: 11807: debug : qemuDomainLooku
2017-07-28 08:35:03.689+0000: 11807: debug : virThreadJobCle
2017-07-28 08:35:03.697+0000: 11802: debug : virThreadJobSet:96 : Thread 11802 (virNetServerHa
2017-07-28 08:35:03.697+0000: 11802: debug : virThreadJobCle
2017-07-28 08:35:03.698+0000: 11806: debug : virThreadJobSet:96 : Thread 11806 (virNetServerHa
2017-07-28 08:35:03.698+0000: 11806: debug : qemuDomainLooku
2017-07-28 08:35:03.698+0000: 11806: debug : virThreadJobCle
2017-07-28 08:35:03.698+0000: 11810: debug : virThreadJobSet:96 : Thread 11810 (virNetServerHa
2017-07-28 08:35:03.698+0000: 11810: debug : virThreadJobCle
2017-07-28 08:35:03.699+0000: 11804: debug : virThreadJobSet:96 : Thread 11804 (virNetServerHa
2017-07-28 08:35:03.699+0000: 11804: debug : qemuDomainLooku
2017-07-28 08:35:03.699+0000: 11804: debug : virThreadJobCle
2017-07-28 08:35:03.857+0000: 11801: debug : virThreadJobSet:96 : Thread 11801 (virNetServerHa
2017-07-28 08:35:03.857+0000: 11801: debug : virThreadJobCle
2017-07-28 08:35:03.858+0000: 11808: debug : virThreadJobSet:96 : Thread 11808 (virNetServerHa
2017-07-28 08:35:03.858+0000: 11808: debug : qemuDomainLooku
2017-07-28 08:35:03.858+0000: 11808: debug : virThreadJobCle
This is Ocata.
tags: | added: gate-failure |
That looks like a privsep issue? Any idea if the privsep daemon is still running in those cases?