Gate tempest dsvm neutron dvr test fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Incomplete
|
Undecided
|
Unassigned | ||
tempest |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
The following tests are failing in the neutron gate:
tempest.
(tempest.
tempest.
tempest.
I spotted this message in logs [1]:
"Connection to the hypervisor is broken on host: ubuntu-
Tracebacks:
2016-12-14 10:34:36.039551 | Captured traceback:
2016-12-14 10:34:36.039562 | ~~~~~~~~~~~~~~~~~~~
2016-12-14 10:34:36.039577 | Traceback (most recent call last):
2016-12-14 10:34:36.039611 | File "tempest/
2016-12-14 10:34:36.039634 | waiters.
2016-12-14 10:34:36.039658 | File "tempest/
2016-12-14 10:34:36.039693 | raise exceptions.
2016-12-14 10:34:36.039728 | tempest.
2016-12-14 10:34:36.043578 | Captured traceback:
2016-12-14 10:34:36.043588 | ~~~~~~~~~~~~~~~~~~~
2016-12-14 10:34:36.043602 | Traceback (most recent call last):
2016-12-14 10:34:36.043619 | File "tempest/test.py", line 100, in wrapper
2016-12-14 10:34:36.043636 | return f(self, *func_args, **func_kwargs)
2016-12-14 10:34:36.043668 | File "tempest/
2016-12-14 10:34:36.043687 | server = self.create_
2016-12-14 10:34:36.043709 | File "tempest/
2016-12-14 10:34:36.043718 | **kwargs)
2016-12-14 10:34:36.043752 | File "tempest/
2016-12-14 10:34:36.043763 | % server['id'])
2016-12-14 10:34:36.043798 | File "/opt/stack/
2016-12-14 10:34:36.043810 | self.force_
2016-12-14 10:34:36.043846 | File "/opt/stack/
2016-12-14 10:34:36.043864 | six.reraise(
2016-12-14 10:34:36.043886 | File "tempest/
2016-12-14 10:34:36.043905 | clients.
2016-12-14 10:34:36.043927 | File "tempest/
2016-12-14 10:34:36.043939 | server_
2016-12-14 10:34:36.044257 | tempest.
2016-12-14 10:34:36.044301 | Details: {u'code': 500, u'created': u'2016-
2016-12-14 10:34:36.039827 | Captured traceback:
2016-12-14 10:34:36.039838 | ~~~~~~~~~~~~~~~~~~~
2016-12-14 10:34:36.039852 | Traceback (most recent call last):
2016-12-14 10:34:36.039870 | File "tempest/test.py", line 241, in setUpClass
2016-12-14 10:34:36.039885 | six.reraise(etype, value, trace)
2016-12-14 10:34:36.039903 | File "tempest/test.py", line 234, in setUpClass
2016-12-14 10:34:36.039915 | cls.resource_
2016-12-14 10:34:36.039944 | File "tempest/
2016-12-14 10:34:36.039972 | cls.server = cls.create_
2016-12-14 10:34:36.039995 | File "tempest/
2016-12-14 10:34:36.040005 | **kwargs)
2016-12-14 10:34:36.040027 | File "tempest/
2016-12-14 10:34:36.040038 | % server['id'])
2016-12-14 10:34:36.040083 | File "/opt/stack/
2016-12-14 10:34:36.040107 | self.force_
2016-12-14 10:34:36.040143 | File "/opt/stack/
2016-12-14 10:34:36.040161 | six.reraise(
2016-12-14 10:34:36.040183 | File "tempest/
2016-12-14 10:34:36.040202 | clients.
2016-12-14 10:34:36.040224 | File "tempest/
2016-12-14 10:34:36.040237 | server_
2016-12-14 10:34:36.040271 | tempest.
2016-12-14 10:34:36.040329 | Details: {u'code': 500, u'created': u'2016-
tags: | added: gate-failure l3-dvr-backlog |
I think this is related to the libvirtd issues we've been seeing on xenial, https:/ /bugs.launchpad .net/nova/ +bug/1643911
I don't see the exact footprint in the syslog for this job, but the "Connection to the hypervisor is broken on host" is telling.
Actually, syslog does have this:
Dec 14 10:05:19 ubuntu- xenial- osic-cloud1- disk-6162583 23.so[7f755ffe5 000+1bf000]
kernel: traps: libvirtd[16302] general protection ip:7f7560066355 sp:7ffea18bcf60 error:0 in libc-2.
libvirtd seems to have restarted right afterwards, but it does make this suspect.