Bug 1752023

Summary:	build ovn-kubernetes with cgo disabled.
Product:	OpenShift Container Platform	Reporter:	Casey Callendrello <cdc>
Component:	Networking	Assignee:	Phil Cameron <pcameron>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	danw, zzhao
Version:	4.2.0
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-16 06:41:11 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:

Description Casey Callendrello 2019-09-13 13:16:43 UTC

Description of problem:
CNI binaries are special - we build them as part of the container build pipeline, then "leak" them out to the host.  Unfortunately, we *also* have special build tooling that injects openssl in to our release binaries.

We're seeing occasional situations where our binaries coredump repeatedly - this is tracked in 1725832.

In the mean time, any CNI binaries must be built with cgo disabled in the dockerfile.

Comment 2 Dan Winship 2019-09-13 14:53:33 UTC

https://github.com/openshift/sdn/pull/34 is the corresponding PR for openshift-sdn. This bug is just about ovn-kubernetes's CNI plugin. I think Casey already did everything else.

Comment 3 Phil Cameron 2019-09-13 15:37:17 UTC

https://github.com/openshift/ovn-kubernetes/pull/24

Comment 5 zhaozhanqi 2019-09-19 08:40:42 UTC

from build http://download.eng.bos.redhat.com/brewroot/packages/ose-ovn-kubernetes-container/v4.2.0/201909172311/data/logs/x86_64-build.log

Verified this bug

Comment 6 errata-xmlrpc 2019-10-16 06:41:11 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-2019:2922