Neutron Linuxbridge jobs failing with 'operation failed: failed to read XML'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Critical
|
Daniel Berrange | ||
neutron |
Invalid
|
Critical
|
Unassigned | ||
os-vif |
Invalid
|
Undecided
|
Unassigned |
Bug Description
2016-08-11 12:57:42.191740 | Traceback (most recent call last):
2016-08-11 12:57:42.191760 | File "tempest/test.py", line 106, in wrapper
2016-08-11 12:57:42.191779 | return f(self, *func_args, **func_kwargs)
2016-08-11 12:57:42.191814 | File "tempest/
2016-08-11 12:57:42.191825 | 'ACTIVE')
2016-08-11 12:57:42.191851 | File "tempest/
2016-08-11 12:57:42.191865 | server_
2016-08-11 12:57:42.191905 | tempest.
2016-08-11 12:57:42.191942 | Details: {u'message': u'operation failed: failed to read XML', u'created': u'2016-
In nova-cpu logs, we see the same error: http://
Note that the log contains other suspicious errors, like:
- privsep unexpected errors: http://
- libvirt failing to locate brq: http://
Agent logs seems more or less clean.
Changed in nova: | |
assignee: | nobody → Daniel Berrange (berrange) |
As per grafana, the failures started at around Aug 11, 3am. Patches that were merged around that time and are related to linuxbridge are: https:/ /review. openstack. org/298443 and https:/ /review. openstack. org/353264