Bug 1521107

Summary:	Sometimes TestSimpleInterfaceMonitor.test_get_events functional test fails
Product:	Red Hat OpenStack	Reporter:	Ihar Hrachyshka <ihrachys>
Component:	openstack-neutron	Assignee:	Ihar Hrachyshka <ihrachys>
Status:	CLOSED ERRATA	QA Contact:	Arie Bregman <abregman>
Severity:	high	Docs Contact:
Priority:	high
Version:	8.0 (Liberty)	CC:	amuller, ccollett, chrisw, ihrachys, jlibosva, nyechiel, srevivo
Target Milestone:	zstream	Keywords:	AutomationBlocker, Triaged, ZStream
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-7.2.0-30.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1523853 (view as bug list)		Environment:
Last Closed:	2018-03-15 12:38:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1523853

Description Ihar Hrachyshka 2017-12-05 20:02:48 UTC

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+.

Comment 1 Ihar Hrachyshka 2017-12-07 15:05:50 UTC

Happens all the time.

Comment 7 errata-xmlrpc 2018-03-15 12:38:27 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:0534