Errors about multiple networks pollutes functional test output

Bug #1629046 reported by Jay Pipes
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Low
Khushbuparakh

Bug Description

Running the Nova functional tests locally, I consistently get around a dozen or so of these in the output:

Captured stderr:
~~~~~~~~~~~~~~~~
    Traceback (most recent call last):
      File "/home/jaypipes/src/git.openstack.org/openstack/nova/.tox/functional/local/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 457, in fire_timers
        timer()
      File "/home/jaypipes/src/git.openstack.org/openstack/nova/.tox/functional/local/lib/python2.7/site-packages/eventlet/hubs/timer.py", line 58, in __call__
        cb(*args, **kw)
      File "/home/jaypipes/src/git.openstack.org/openstack/nova/.tox/functional/local/lib/python2.7/site-packages/eventlet/greenthread.py", line 214, in main
        result = function(*args, **kwargs)
      File "nova/utils.py", line 1066, in context_wrapper
        return func(*args, **kwargs)
      File "nova/compute/manager.py", line 1414, in _allocate_network_async
        six.reraise(*exc_info)
      File "nova/compute/manager.py", line 1397, in _allocate_network_async
        bind_host_id=bind_host_id)
      File "nova/network/neutronv2/api.py", line 844, in allocate_for_instance
        context, instance, neutron, requested_networks, ordered_networks)
      File "nova/network/neutronv2/api.py", line 730, in _validate_requested_network_ids
        raise exception.NetworkAmbiguous(msg)
    NetworkAmbiguous: Multiple possible networks found, use a Network ID to be more specific.

They don't affect the result of the test, so it's nothing more than an annoyance, but would be nice to fix.

Changed in nova:
assignee: nobody → Nicolas Helgeson (nhelgeson)
Changed in nova:
assignee: Nicolas Helgeson (nhelgeson) → nobody
Jin Li (jl7351)
Changed in nova:
assignee: nobody → Jin Li (jl7351)
Revision history for this message
Jin Li (jl7351) wrote :

Hi Jay, can you please tell me how I can reproduce this issue? I run "sudo tox -e py27" on nova and I can't find any NetworkAmbiguous exception.
my plan is to find all test cases threw this exception and catch the exception in these test cases. what do you think?

Revision history for this message
Jay Pipes (jaypipes) wrote :

Hi Jin Li!

You need to run tox -efunctional to run the functional tests. You'll see the output in there :)

Best,

-jay

Revision history for this message
Jin Li (jl7351) wrote :

Hi Jay,
I use this version of nova : 0a2700e4e69996f1df080e34c11cb7ae448ad938
and run tox -efunctional in home directory of nova, there are some stderr but none of them is NetworkAmbiguous. am I missing any steps? do I need to have devstack running to do functional test?

I will attach me test result below for you convenience.

-Jin

Sean Dague (sdague)
Changed in nova:
assignee: Jin Li (jl7351) → nobody
Changed in nova:
assignee: nobody → Khushbuparakh (khushbuparakh)
Revision history for this message
melanie witt (melwitt) wrote :

This is several years old and this issue no longer exists.

Changed in nova:
status: Confirmed → Invalid
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.