UDP port forwarding test is failing often

Bug #1850800 reported by Slawek Kaplonski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
High
Slawek Kaplonski

Bug Description

Example of failure: https://5ff584e2dd4971153a4c-657b7e35529908ead783d281edf8093c.ssl.cf5.rackcdn.com/691640/1/check/neutron-tempest-plugin-scenario-openvswitch/7532e66/testr_results.html.gz

Traceback (most recent call last):
  File "/opt/stack/tempest/.tox/tempest/lib/python3.6/site-packages/neutron_tempest_plugin/scenario/test_port_forwardings.py", line 116, in test_port_forwarding_to_2_servers
    self._test_udp_port_forwarding(servers)
  File "/opt/stack/tempest/.tox/tempest/lib/python3.6/site-packages/neutron_tempest_plugin/scenario/test_port_forwardings.py", line 101, in _test_udp_port_forwarding
    constants.PROTO_NAME_UDP))
  File "/opt/stack/tempest/.tox/tempest/lib/python3.6/site-packages/testtools/testcase.py", line 417, in assertIn
    self.assertThat(haystack, Contains(needle), message)
  File "/opt/stack/tempest/.tox/tempest/lib/python3.6/site-packages/testtools/testcase.py", line 498, in assertThat
    raise mismatch_error
testtools.matchers._impl.MismatchError: 'tempest-server-2-326024201-UDP-test' not in ''

Logstash query: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22line%20101%2C%20in%20_test_udp_port_forwarding%5C%22

Tags: gate-failure
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to neutron-tempest-plugin (master)

Related fix proposed to branch: master
Review: https://review.opendev.org/692381

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to neutron-tempest-plugin (master)

Reviewed: https://review.opendev.org/692381
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=526f53722fc51eb1f9bdac957495518cbeae5e10
Submitter: Zuul
Branch: master

commit 526f53722fc51eb1f9bdac957495518cbeae5e10
Author: Slawek Kaplonski <email address hidden>
Date: Thu Oct 31 15:29:48 2019 +0100

    Mark port_forwarding scenario test as unstable temporary

    Change-Id: I9db5a329ce02b3ca1f5acb19eb0ad4ceb0c8aadc
    Related-Bug: #1850800

Changed in neutron:
assignee: nobody → Slawek Kaplonski (slaweq)
status: Confirmed → In Progress
Revision history for this message
Slawek Kaplonski (slaweq) wrote :
Changed in neutron:
assignee: Slawek Kaplonski (slaweq) → Nate Johnston (nate-johnston)
Changed in neutron:
assignee: Nate Johnston (nate-johnston) → Slawek Kaplonski (slaweq)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron-tempest-plugin (master)

Reviewed: https://review.opendev.org/699213
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=bd0f3712e25413e6c5b1ed5c35ef6e1361d922a6
Submitter: Zuul
Branch: master

commit bd0f3712e25413e6c5b1ed5c35ef6e1361d922a6
Author: Slawek Kaplonski <email address hidden>
Date: Mon Dec 16 14:13:41 2019 +0000

    Fix intermittent port_forwarding test failures

    This test was failing from time to time on checking UDP port
    forwarding.
    The reason for that was that sometimes (for unknown for me reason)
    nc server spawned on guest vm wasn't run properly. Due to that there was
    no response from this nc server and test was failing.

    This patch changes that to use wait_until_true() helper and wait
    60 seconds to received msg. Every time it tries to receive message,
    first it tries also to spawn nc server on guest vm.

    This patch also reverts commit
    526f53722fc51eb1f9bdac957495518cbeae5e10.
    as port_forwarding test don't need to be marked as unstable anymore.

    Closes-Bug: #1850800

    Change-Id: I95d5ba02b2851a07e6e1a8a2bedfdce7d20f32fc

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron-tempest-plugin 0.9.0

This issue was fixed in the openstack/neutron-tempest-plugin 0.9.0 release.

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.