Constant tracebacks with eventlet 0.18.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
Undecided
|
Unassigned | ||
Glance |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Davanum Srinivas (DIMS) | ||
neutron |
Expired
|
Undecided
|
Unassigned |
Bug Description
Kilo builds, with eventlet 0.18.2 have a constant traceback:
2016-02-12 00:47:01.126 3936 DEBUG nova.api.
2016-02-12 00:47:01.129 3936 INFO nova.osapi_
File "/opt/bbc/
write(
File "/opt/bbc/
_writelines
File "/opt/bbc/
writeall(fd, item)
File "/opt/bbc/
fd.write(buf)
File "/usr/lib/
self.flush()
File "/usr/lib/
self.
File "/opt/bbc/
tail = self.send(data, flags)
File "/opt/bbc/
return self._send_
File "/opt/bbc/
return send_method(data, *args)
error: [Errno 104] Connection reset by peer
This is happening across nova, neutron, glance, etc..
Dropping back to eventlet < 0.18.0 works.
Changed in cinder: | |
status: | New → Invalid |
@Jesse Keating:
The periodic check for stable/kilo python27 shows no failure [1]
although it uses eventlet version 0.18.2 [2].
* What's the exact version of Nova you are using?
* What are the steps which lead to that traceback?
Please switch the status back to "new" after you provided the needed
information.
References: logs.openstack. org/periodic- stable/ periodic- nova-python27- kilo/0015699/ testr_results. html.gz logs.openstack. org/periodic- stable/ periodic- nova-python27- kilo/0015699/ console. html#_2016- 02-12_07_ 12_51_249
[1] http://
[2] http://