Bug 1523853 - Sometimes TestSimpleInterfaceMonitor.test_get_events functional test fails
Summary: Sometimes TestSimpleInterfaceMonitor.test_get_events functional test fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: zstream
: 9.0 (Mitaka)
Assignee: Ihar Hrachyshka
QA Contact: Arie Bregman
URL:
Whiteboard:
Depends On: 1521107
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-08 20:30 UTC by Ihar Hrachyshka
Modified: 2018-03-15 12:42 UTC (History)
8 users (show)

Fixed In Version: openstack-neutron-8.4.0-13.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1521107
Environment:
Last Closed: 2018-03-15 12:41:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 318898 0 None None None 2017-12-08 20:30:45 UTC
Red Hat Product Errata RHBA-2018:0537 0 None None None 2018-03-15 12:42:44 UTC

Description Ihar Hrachyshka 2017-12-08 20:30:45 UTC
+++ This bug was initially created as a clone of Bug #1521107 +++

https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/DFG-network-neutron-8-dsvm-functional-rhos/65/testReport/junit/neutron.tests.functional.agent.linux.test_ovsdb_monitor/TestSimpleInterfaceMonitor/test_get_events_vsctl_/


Traceback (most recent call last):
  File "neutron/tests/functional/agent/linux/test_ovsdb_monitor.py", line 142, in test_get_events
    'Initial call should always be true')
  File "/usr/lib/python2.7/site-packages/unittest2/case.py", line 678, in assertTrue
    raise self.failureException(msg)
AssertionError: [] is not true : Initial call should always be true

This is probably fixed with https://review.openstack.org/#/c/318898/1 that was merged in Newton+.

--- Additional comment from Ihar Hrachyshka on 2017-12-07 10:05:50 EST ---

Happens all the time.

Comment 7 errata-xmlrpc 2018-03-15 12:41:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0537


Note You need to log in before you can comment on or make changes to this bug.