← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2079831] Re: [tempest] VM ports have status=DOWN when calling ``TestNetworkBasicOps._setup_network_and_servers``

 

Will mark the neutron bug as Invalid since it is a bug in tempest.

** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2079831

Title:
  [tempest] VM ports have status=DOWN when calling
  ``TestNetworkBasicOps._setup_network_and_servers``

Status in neutron:
  Invalid
Status in tempest:
  In Progress

Bug description:
  The method ``TestNetworkBasicOps._setup_network_and_servers`` is used
  in several tempest tests. It creates a set of resources (network,
  servers, FIPs, etc). This method has a race condition when the config
  option "project_networks_reachable" if False (by default).

  The server is created [1] but there is no connectivity test [2] (due
  to project_networks_reachable=False). The next step is to create a FIP
  [3]. Because we are not passing the port_id, we first retrieve all the
  VM ports [4]. The issue happens at [5]: the ports are created but are
  still down.

  An example of this can be seen in [5][6]:
  1) The tempest test list the VM ports (only one in this case) but the port is down: https://paste.opendev.org/show/bSLi4joS6blqipbwa7Pq/

  2) The Neutron API finishes processing the port activation at the same
  time the port list call was made:
  https://paste.opendev.org/show/brRqntkQYdDoVeEqCeXF/

  
  It is needed to add an active wait in the method ``get_server_port_id_and_ip4`` in order to wait all ports to be active.

  
  [1]https://github.com/openstack/tempest/blob/0a0e1070e573674332cb5126064b95f17099307e/tempest/scenario/test_network_basic_ops.py#L120
  [2]https://github.com/openstack/tempest/blob/0a0e1070e573674332cb5126064b95f17099307e/tempest/scenario/test_network_basic_ops.py#L124
  [3]https://github.com/openstack/tempest/blob/0a0e1070e573674332cb5126064b95f17099307e/tempest/scenario/test_network_basic_ops.py#L128
  [4]https://github.com/openstack/tempest/blob/0a0e1070e573674332cb5126064b95f17099307e/tempest/scenario/manager.py#L1143
  [5]https://3fdd3adccbbbca8893fe-55e7a9d33a731efe4f7611907a31a4a1.ssl.cf1.rackcdn.com/924317/10/experimental/neutron-ovn-tempest-ovs-master/038956b/controller/logs/screen-neutron-api.txt
  [6]https://3fdd3adccbbbca8893fe-55e7a9d33a731efe4f7611907a31a4a1.ssl.cf1.rackcdn.com/924317/10/experimental/neutron-ovn-tempest-ovs-master/038956b/controller/logs/tempest_log.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2079831/+subscriptions



References