Tempest tests fail with "Multiple possible networks found" error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
New
|
Undecided
|
Unassigned | ||
tempest |
New
|
Undecided
|
Unassigned |
Bug Description
Couldn't find an already-filed bug for this one (seen on milestone-proposed backport):
Tempest test runs sometimes fail with "NetworkAmbiguous" errors (Multiple possible networks found...)
2013-10-08 21:28:27.943 | tempest.
2013-10-08 21:28:27.981 | Error in atexit.
2013-10-08 21:28:27.982 | Traceback (most recent call last):
2013-10-08 21:28:27.984 | File "/usr/lib/
2013-10-08 21:28:27.985 | func(*targs, **kargs)
2013-10-08 21:28:27.986 | File "tempest/test.py", line 167, in validate_
2013-10-08 21:28:27.987 | + str(at_exit_set))
2013-10-08 21:28:27.988 | RuntimeError: tearDownClass does not calls the super's tearDownClass in these classes: set([<class 'tempest.
2013-10-08 21:28:27.989 | Error in sys.exitfunc:
2013-10-08 21:28:28.099 |
2013-10-08 21:28:28.100 | process-returncode
2013-10-08 21:28:28.100 | process-returncode ... FAIL
2013-10-08 21:28:28.537 |
2013-10-08 21:28:28.537 | =======
2013-10-08 21:28:28.538 | FAIL: tearDownClass (tempest.
2013-10-08 21:28:28.538 | tearDownClass (tempest.
2013-10-08 21:28:28.538 | -------
2013-10-08 21:28:28.539 | _StringException: Traceback (most recent call last):
2013-10-08 21:28:28.539 | File "tempest/
2013-10-08 21:28:28.539 | thing.delete()
2013-10-08 21:28:28.540 | File "tempest/
2013-10-08 21:28:28.540 | self.client.
2013-10-08 21:28:28.540 | File "/opt/stack/
2013-10-08 21:28:28.540 | ret = self.function(
2013-10-08 21:28:28.541 | File "/opt/stack/
2013-10-08 21:28:28.541 | return self.delete(
2013-10-08 21:28:28.541 | File "/opt/stack/
2013-10-08 21:28:28.542 | headers=headers, params=params)
2013-10-08 21:28:28.542 | File "/opt/stack/
2013-10-08 21:28:28.543 | headers=headers, params=params)
2013-10-08 21:28:28.543 | File "/opt/stack/
2013-10-08 21:28:28.543 | self._handle_
2013-10-08 21:28:28.543 | File "/opt/stack/
2013-10-08 21:28:28.544 | exception_
2013-10-08 21:28:28.544 | File "/opt/stack/
2013-10-08 21:28:28.544 | message=error_dict)
2013-10-08 21:28:28.545 | NeutronClientEx
2013-10-08 21:28:28.545 |
2013-10-08 21:28:28.545 |
2013-10-08 21:28:28.546 | =======
2013-10-08 21:28:28.546 | FAIL: tempest.
2013-10-08 21:28:28.546 | tempest.
2013-10-08 21:28:28.546 | -------
2013-10-08 21:28:28.547 | _StringException: Empty attachments:
2013-10-08 21:28:28.547 | stderr
2013-10-08 21:28:28.547 | stdout
2013-10-08 21:28:28.548 |
2013-10-08 21:28:28.548 | pythonlogging:'': {{{
2013-10-08 21:28:28.548 | 2013-10-08 21:27:45,619 400 Bad Request
2013-10-08 21:28:28.549 | 2013-10-08 21:27:45,619 <?xml version="1.0"?>
2013-10-08 21:28:28.549 | <Response>
2013-10-08 21:28:28.549 | }}}
2013-10-08 21:28:28.549 |
2013-10-08 21:28:28.550 | Traceback (most recent call last):
2013-10-08 21:28:28.550 | File "tempest/
2013-10-08 21:28:28.550 | reservation_1, rcuk_1 = _run_instance(
2013-10-08 21:28:28.551 | File "tempest/
2013-10-08 21:28:28.551 | client_
2013-10-08 21:28:28.551 | File "tempest/
2013-10-08 21:28:28.552 | return getattr(conn, name)(*args, **kwargs)
2013-10-08 21:28:28.552 | File "/usr/local/
2013-10-08 21:28:28.552 | verb='POST')
2013-10-08 21:28:28.553 | File "/usr/local/
2013-10-08 21:28:28.553 | raise self.ResponseEr
2013-10-08 21:28:28.553 | EC2ResponseError: EC2ResponseError: 400 Bad Request
2013-10-08 21:28:28.553 | <?xml version="1.0"?>
2013-10-08 21:28:28.554 | <Response>
I assume it is because create_test_server that is defined in BaseComputeTest (tempest/ api/compute/ base.py) is not configured to get the default network ID from config. /bugs.launchpad .net/tempest/ +bug/1250866 have the same problem.
Guys in issue https:/
In setUpClass for BaseComputeTest tests should set the option of getting the ID of default network to be attached.
But this may break some other network related tests.