yahoo-eng-team team mailing list archive

[OpenStack Infra <1818859@xxxxxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1818613 ***
    https://bugs.launchpad.net/bugs/1818613

Reviewed:  https://review.openstack.org/641117
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=92f1281b696c79133609d3c04b467ac7ea9f4337
Submitter: Zuul
Branch:    master

commit 92f1281b696c79133609d3c04b467ac7ea9f4337
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Tue Mar 5 18:37:44 2019 +0000

    Add a more robust method to check OVSDB values in BaseOVSTestCase
    
    Sometimes, when the OVSDB is too loaded (that could happen during the
    functional tests), there is a delay between the OVSDB post transaction
    end and when the register (new or updated) can be read. Although this is
    something that should not happen (considering the OVSDB is transactional),
    tests should deal with this inconvenience and provide a robust method to
    retrieve a value and at the same time check the value. This new method
    should provide a retrieving mechanism to read again the value in case of
    discordance.
    
    In order to solve the gate problem ASAP, another bug is fixed in this
    patch: to skip the QoS removal when OVS agent is initialized during
    funtional tests
    
    When executing functional tests, several OVS QoS policies specific for
    minimum bandwidth rules [1]. Because during the functional tests
    execution several threads can create more than one minimum bandwidth
    QoS policy (something in a production environment cannot happen), the
    OVS QoS driver must skip the execution of [2] to avoid removing other
    QoS created in parellel in other tests.
    
    This patch is marking as unstable "test_min_bw_qos_policy_rule_lifecycle"
    and "test_bw_limit_qos_port_removed". Those tests will be investigated
    once the CI gates are stable.
    
    [1] Those QoS policies are created only to hold minimum bandwidth rules.
        Those policies are marked with:
           external_ids: {'_type'='minimum_bandwidth'}
    [2] https://github.com/openstack/neutron/blob/d6fba30781c5f4e63beeda04d065226660fc92b6/neutron/plugins/ml2/drivers/openvswitch/agent/extension_drivers/qos_driver.py#L43
    
    Closes-Bug: #1818613
    Closes-Bug: #1818859
    Related-Bug: #1819125
    
    Change-Id: Ia725cc1b36bc3630d2891f86f76b13c16f6cc37c


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  neutron functional job intermittent failures with
  ovsdbapp.backend.ovs_idl.idlutils.RowNotFound

Status in neutron:
  Fix Released

Bug description:
  It appears the neutron functional job started failing with errors
  related to:

  ovsdbapp.backend.ovs_idl.idlutils.RowNotFound

  For example [1][2].

  Based on logstash [3] it looks like this issue may have cropped up
  around March 5th.

  
  [1] http://logs.openstack.org/34/639034/7/check/neutron-functional/d32644a/job-output.txt.gz
  [2] http://logs.openstack.org/04/637004/2/check/neutron-functional-python27/5dd04c3/job-output.txt.gz#_2019-03-06_13_27_21_193728
  [3] http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22ovsdbapp.backend.ovs_idl.idlutils.RowNotFound%3A%20Cannot%20find%20Port%20with%20name%3D%5C%22

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