Bug 1628949

Summary:	ovs 2.10 dies: assertion !ovs_list_is_empty(list) failed in ovs_list_back() when configured with OpenDaylight as manager/controller
Product:	Red Hat Enterprise Linux 7	Reporter:	Flavio Leitner <fleitner>
Component:	openvswitch2.10	Assignee:	Flavio Leitner <fleitner>
Status:	CLOSED ERRATA	QA Contact:	haidong li <haili>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.5	CC:	amuller, apevec, atelang, atragler, chrisw, ctrautma, dalvarez, echaudro, fleitner, haili, kfida, qding, rhos-maint, rkhan, sgaddam, srevivo, wznoinsk
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openvswitch2.10-2.10.0-4.el7fdp	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1626488	Environment:
Last Closed:	2018-09-20 20:13:35 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:	1626488

Comment 3 qding 2018-09-17 02:23:09 UTC

Hello Waldemar Znoinski,

I'm ovs-qe and doing the bug verification. Could you please give an instruction or script to reproduce the issue?

Thanks
Qijun

Comment 4 Waldemar Znoinski 2018-09-17 09:04:51 UTC

hi Qijun,

I'm getting this problem in a TripleO environment. If you want to use the same method of installation of OVS + ODL as mine you'd have a quite beefy machine, i.e.: 64GB RAM server and I can give you the commands to test. Other option is to install OVS + ODL on its own (not sure whether the issue exists there - probably yes but never checked it) or using a machine I dpeloy with OSP14 + OVS + ODL that shows the problem. You can then install patched version of OVS and verify fix.

Which way you want to go?

Comment 5 qding 2018-09-17 09:18:35 UTC

(In reply to Waldemar Znoinski from comment #4)
> hi Qijun,
> 
> I'm getting this problem in a TripleO environment. If you want to use the
> same method of installation of OVS + ODL as mine you'd have a quite beefy
> machine, i.e.: 64GB RAM server and I can give you the commands to test.
> Other option is to install OVS + ODL on its own (not sure whether the issue
> exists there - probably yes but never checked it) or using a machine I
> dpeloy with OSP14 + OVS + ODL that shows the problem. You can then install
> patched version of OVS and verify fix.
> 
> Which way you want to go?

We have no problem to get a server with 64G RAM, so prefer the option OVS+ODL, the same one as yours because with the chance we want to extend it to a test case so that we can have a basic verification for this combination in our regular test. As we don't know much on ODL, it would be appreciated if you can give us a much detail instruction. Thank you very much.

Qijun

Comment 9 errata-xmlrpc 2018-09-20 20:13:35 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/RHEA-2018:2735