Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1731913

Summary:	[4.1] arping is missing in sdn image
Product:	OpenShift Container Platform	Reporter:	Casey Callendrello <cdc>
Component:	Networking	Assignee:	Phil Cameron <pcameron>
Status:	CLOSED ERRATA	QA Contact:	zhaozhanqi <zzhao>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, sponnaga, vlaad
Target Milestone:	---
Target Release:	4.1.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	4.1.9
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The arping binary was missing from the SDN image build. Consequence: Egress IPs, especially High-Availability egress IPs may not have functioned reliably.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-07 15:06:02 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-07-22 11:23:20 UTC

Description of problem:

Egress IPs relies on arping, but it's missing in the image. We've fixed this in 4.2, but we need to fix it in 4.1

Parent card: SDN-488.

Comment 1 Casey Callendrello 2019-07-22 11:28:07 UTC

4.2 bug: SDN-488, has been verified by QE.

Comment 3 zhaozhanqi 2019-07-31 03:32:54 UTC

Verified this bug on 4.1.0-0.nightly-2019-07-29-171515

# oc get co network
NAME      VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
network   4.1.0-0.nightly-2019-07-29-171515   True        False         False      18h

# oc rsh -n openshift-sdn sdn-ltklk
sh-4.2# which arping
/usr/sbin/arping
sh-4.2# exit
exit

Comment 5 errata-xmlrpc 2019-08-07 15:06:02 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:2010