Bug 1807062

Summary: route-override CNI and whereabouts IPAM CNI should be installed in OpenShift
Product: OpenShift Container Platform Reporter: Douglas Smith <dosmith>
Component: NetworkingAssignee: Douglas Smith <dosmith>
Networking sub component: multus QA Contact: Weibin Liang <weliang>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: eparis
Version: 4.3.z   
Target Milestone: ---   
Target Release: 4.3.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1807067 (view as bug list) Environment:
Last Closed: 2020-03-24 14:33:46 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:
Bug Depends On: 1807067    
Bug Blocks:    

Description Douglas Smith 2020-02-25 14:44:07 UTC
Description of problem: route-override and whereabouts IPAM binaries are not copied to the host systems, and their configurations are not integrated in

How reproducible: Always.

Steps to Reproduce:
1. Install OpenShift

Actual results: Note that no binaries named "route-override" or "whereabouts" appear in the CNI BIN directory on the hosts

Expected results: "route-override" or "whereabouts" appear in the CNI BIN directory on the hosts

Comment 5 Weibin Liang 2020-03-12 17:31:39 UTC
Tested and verified in 4.3.0-0.nightly-2020-03-12-085147

[root@dhcp-41-193 FILE]# oc get clusterversions
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.3.0-0.nightly-2020-03-12-085147   True        False         128m    Cluster version is 4.3.0-0.nightly-2020-03-12-085147

[root@dhcp-41-193 FILE]# oc debug node/compute-0
Starting pod/compute-0-debug ...
To use host binaries, run `chroot /host`
Pod IP:
If you don't see a command prompt, try pressing enter.
sh-4.2# chroot /host
sh-4.4#  ls /var/lib/cni/bin -lathr
total 157M
drwxr-xr-x. 2 root root 4.0K Mar 12 15:02 .
drwxr-xr-x. 6 root root   62 Mar 12 15:06 ..
-rwxr-xr-x. 1 root root  40M Mar 12 15:08 multus
-rwxr-xr-x. 1 root root 4.1M Mar 12 15:08 bandwidth
-rwxr-xr-x. 1 root root 4.5M Mar 12 15:08 bridge
-rwxr-xr-x. 1 root root  12M Mar 12 15:08 dhcp
-rwxr-xr-x. 1 root root 5.8M Mar 12 15:08 firewall
-rwxr-xr-x. 1 root root 3.0M Mar 12 15:08 flannel
-rwxr-xr-x. 1 root root 4.0M Mar 12 15:08 host-device
-rwxr-xr-x. 1 root root 3.5M Mar 12 15:08 host-local
-rwxr-xr-x. 1 root root 4.2M Mar 12 15:08 ipvlan
-rwxr-xr-x. 1 root root 3.1M Mar 12 15:08 loopback
-rwxr-xr-x. 1 root root 4.2M Mar 12 15:08 macvlan
-rwxr-xr-x. 1 root root 4.0M Mar 12 15:08 portmap
-rwxr-xr-x. 1 root root 4.4M Mar 12 15:08 ptp
-rwxr-xr-x. 1 root root 3.3M Mar 12 15:08 sbr
-rwxr-xr-x. 1 root root 2.8M Mar 12 15:08 static
-rwxr-xr-x. 1 root root 3.2M Mar 12 15:08 tuning
-rwxr-xr-x. 1 root root 4.2M Mar 12 15:08 vlan
-rwxr-xr-x. 1 root root 3.2M Mar 12 15:08 route-override
-rwxr-xr-x. 1 root root  40M Mar 12 15:08 whereabouts
-rwxr-xr-x. 1 root root 5.8M Mar 12 15:10 openshift-sdn

Comment 7 errata-xmlrpc 2020-03-24 14:33:46 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.