Trunk Tests are failing often in dvr-multinode scenario job

Bug #1766701 reported by Slawek Kaplonski on 2018-04-24
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
High
Slawek Kaplonski
Miguel Lavalle (minsel) on 2018-04-26
Changed in neutron:
assignee: nobody → Miguel Lavalle (minsel)
Bernard Cafarelli (bcafarel) wrote :

These tests are currently marked unstable, so will not appear with failed build_status?
https://github.com/openstack/neutron-tempest-plugin/commit/02a5e2b07680d8c4dd69d681ae9a01d92b4be0ac

A recent failure for neutron_tempest_plugin.scenario.test_trunk.TrunkTest.test_subport_connectivity: http://logs.openstack.org/73/589573/1/check/neutron-tempest-plugin-dvr-multinode-scenario/b69c365/job-output.txt.gz#_2018-08-08_00_50_01_984287

Changed in neutron:
assignee: Miguel Lavalle (minsel) → Slawek Kaplonski (slaweq)
Slawek Kaplonski (slaweq) wrote :

Patch proposed for neutron-tempest-plugin: https://review.openstack.org/#/c/602696

Changed in neutron:
status: Confirmed → In Progress
Miguel Lavalle (minsel) wrote :
Changed in neutron:
status: In Progress → Fix Committed

Do we need to backport his patch?

Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/590422
Reason: It's already done in https://review.openstack.org/#/c/602696/3

Reviewed: https://review.openstack.org/611247
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f9cf83474971dfc0f47c1ee9b6d5d17583e1bf51
Submitter: Zuul
Branch: stable/ocata

commit f9cf83474971dfc0f47c1ee9b6d5d17583e1bf51
Author: Slawek Kaplonski <email address hidden>
Date: Wed Sep 12 02:01:31 2018 +0200

    Fix bash cmd used in scenario trunk tests

    In scenario trunk test test_subport_connectivity there
    is bash command used to check name of base interface on
    spawned vm (e.g. ens3 or eth0), configure vlan interface
    with vlan_id used on trunk port (e.g. ens3.10),
    make this vlan device up and run dhclient on this interface
    if it's not running yet.

    This command was broken and that cause failure of this test.

    Change-Id: I4c0207f79cd6df2594f976b9509697209011edf2
    Closes-Bug: #1766701
    (cherry picked from commit 6bf840f0a73579804375dddd92b3a20acc57b877)
    (cherry picked from commit c78b80becfd6ad5865fb1681a05395940591f431)

tags: added: in-stable-ocata

Reviewed: https://review.openstack.org/611246
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c78b80becfd6ad5865fb1681a05395940591f431
Submitter: Zuul
Branch: stable/pike

commit c78b80becfd6ad5865fb1681a05395940591f431
Author: Slawek Kaplonski <email address hidden>
Date: Wed Sep 12 02:01:31 2018 +0200

    Fix bash cmd used in scenario trunk tests

    In scenario trunk test test_subport_connectivity there
    is bash command used to check name of base interface on
    spawned vm (e.g. ens3 or eth0), configure vlan interface
    with vlan_id used on trunk port (e.g. ens3.10),
    make this vlan device up and run dhclient on this interface
    if it's not running yet.

    This command was broken and that cause failure of this test.

    Change-Id: I4c0207f79cd6df2594f976b9509697209011edf2
    Closes-Bug: #1766701
    (cherry picked from commit 6bf840f0a73579804375dddd92b3a20acc57b877)

tags: added: in-stable-pike

This issue was fixed in the openstack/neutron 11.0.6 release.

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers