Functional test fails

Bug #1813540 reported by Slawek Kaplonski on 2019-01-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Slawek Kaplonski

Bug Description

Unit test is failing from time to time since few days.

Example of failure

Logstash query:

summary: - Unit test
+ Functional test
tags: added: functional-tests
removed: unittest
Changed in neutron:
assignee: nobody → Slawek Kaplonski (slaweq)

Fix proposed to branch: master

Changed in neutron:
status: Confirmed → In Progress

Submitter: Zuul
Branch: master

commit 414bdd4c5997886c97d0e3a0b19c684dafeabb7a
Author: Slawek Kaplonski <email address hidden>
Date: Fri Feb 1 14:42:23 2019 +0100

    Don't specify exactly IP in portforwarding functional test

    In Port Forwarding functional tests, port is created in setUp()
    method. This port had specified exactly IP address and subnet to use.
    This was proposed in [1] to fix issue when new port created in same
    subnet got sometimes IP address outside of subnet range.
    Unfortunatelly that fix was not enough and caused other issues
    as sometimes this "fixed" IP address used for port might be
    used e.g. by router_interface port and that caused sometimes
    "409 conflict" response from Neutron sometimes.

    This patch adds additional method in
    neutron.tests.unit.db.test_db_base_plugin_v2 module to find first
    free IP address from given subnet.
    This method is now used in port forwarding tests module to choose
    IP address for second created port in the subnet so there should be
    no conflicts with IP addresses anymore.


    Change-Id: Iee2f72acf6814a0f8f76d240862429a8b63c3b09
    Closes-bug: #1813540

Changed in neutron:
status: In Progress → Fix Released

This issue was fixed in the openstack/neutron development milestone.

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

Other bug subscribers