Bug 1752010

Summary: multus cni-plugins: build without cgo
Product: OpenShift Container Platform Reporter: Casey Callendrello <cdc>
Component: NetworkingAssignee: Casey Callendrello <cdc>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED NOTABUG Docs Contact:
Severity: unspecified    
Priority: unspecified CC: nagrawal, pcameron
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-09-16 14:14:29 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 12:47:21 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 Phil Cameron 2019-09-13 18:39:29 UTC 
@Neelesh
I haven't worked with multus. Where is the repo and the Dockerfile. 
The fix is to just add CGO_ENABLED=0 before the make in the Dockerfile.
Comment 3 Casey Callendrello 2019-09-16 14:14:29 UTC 
Looks like Multus already has cgo disabled.