test_networks is failing

Bug #1007076 reported by David Kranz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Fix Released
High
Jay Pipes

Bug Description

Consistently failing jenkins:

======================================================================
ERROR: test suite for <class 'tempest.tests.network.test_networks.NetworksTest'>
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/nose-1.1.2-py2.6.egg/nose/suite.py", line 208, in run
    self.setUp()
  File "/usr/lib/python2.6/site-packages/nose-1.1.2-py2.6.egg/nose/suite.py", line 291, in setUp
    self.setupContext(ancestor)
  File "/usr/lib/python2.6/site-packages/nose-1.1.2-py2.6.egg/nose/suite.py", line 314, in setupContext
    try_run(context, names)
  File "/usr/lib/python2.6/site-packages/nose-1.1.2-py2.6.egg/nose/util.py", line 478, in try_run
    return func()
  File "/cygdrive/c/source/tempest/tempest/tests/network/test_networks.py", line 15, in setUpClass
    resp, body = cls.client.create_network(cls.name)
  File "/cygdrive/c/source/tempest/tempest/services/network/json/network_client.py", line 27, in create_network
    body=body)
  File "/cygdrive/c/source/tempest/tempest/common/rest_client.py", line 152, in post
    return self.request('POST', url, headers, body)
  File "/cygdrive/c/source/tempest/tempest/common/rest_client.py", line 173, in request
    self._set_auth()
  File "/cygdrive/c/source/tempest/tempest/common/rest_client.py", line 61, in _set_auth
    self.tenant_name)
  File "/cygdrive/c/source/tempest/tempest/common/rest_client.py", line 137, in keystone_auth
    raise exceptions.EndpointNotFound(service)
EndpointNotFound: Endpoint not found
Details: network

Revision history for this message
Daryl Walleck (dwalleck) wrote :

The solution is the bug I filed yesterday: https://bugs.launchpad.net/tempest/+bug/1006198

Revision history for this message
David Kranz (david-kranz) wrote :

I guess this test is assuming that keystone knows about quantum, which is not the case for my configuration or for jenkins. This test should only run if quantum is being used. Not sure of the best way to do that.

Revision history for this message
Daryl Walleck (dwalleck) wrote :

In that case there would have to be an explicit run_quantum_tests in the config. Nothing else immediately comes to mind.

Revision history for this message
David Kranz (david-kranz) wrote :

I was thinking that we could use the presence/absense of the [network] section to control this. The tempest config file is already a statement about the configuration.

Revision history for this message
Daryl Walleck (dwalleck) wrote :

That would be a very fragile and non-intuitive solution, unless we make it very explicit than ANY missing section will cause it's tests not to run.

Revision history for this message
David Kranz (david-kranz) wrote :

Jay, hopefully you can deal with this as part of your work to get quantum tests through.

Changed in tempest:
status: New → Confirmed
assignee: nobody → Jay Pipes (jaypipes)
Changed in tempest:
importance: Undecided → High
Revision history for this message
Jay Pipes (jaypipes) wrote :

This is now fixed. Tests are skipped if no network endpoint was found.

Changed in tempest:
status: Confirmed → Fix Released
Sean Dague (sdague)
Changed in tempest:
milestone: none → havana-3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.