Bug 1513767 – [3.7] Allow egress router to run on non-default interface

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1513767 - [3.7] Allow egress router to run on non-default interface

Summary:	[3.7] Allow egress router to run on non-default interface

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Networking (Show other bugs)
Sub Component:
Version:	3.7.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	3.7.z
Assigned To:	Dan Winship
QA Contact:	Meng Bo
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1513764
Blocks:
	Show dependency tree / graph

Reported:	2017-11-15 17:42 EST by Dan Winship
Modified:	2017-12-18 08:23 EST (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:	Feature: The "assign-macvlan" pod annotation can now take the name of a network interface rather than just "true" or "false". Reason: Result: egress-routers can now be run on a non-default network interface
Story Points:	---
Clone Of:	1513764
Environment:
Last Closed:	2017-12-18 08:23:56 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:3464	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.7 bug fix and enhancement update	2017-12-18 13:22:05 EST

Groups: None (edit)

Description Dan Winship 2017-11-15 17:42:18 EST

+++ This bug was initially created as a clone of Bug #1513764 +++

Currently egress-routers always attach themselves to the network interface containing the default route. We need to make it possible to attach one to an alternate interface.

To get this out to a customer quickly, we're doing the simplest possible fix, which is to let the user manually specify a network interface (rather than, say, having OpenShift try to figure out the correct interface automatically based on EGRESS_SOURCE).

Comment 1 Dan Winship 2017-11-27 07:41:55 EST

https://github.com/openshift/origin/pull/17383

Comment 3 hongli 2017-12-06 01:24:08 EST

verified in atomic-openshift-3.7.13-1.git.0.a81ae64.el7.x86_64 and passed

Comment 6 errata-xmlrpc 2017-12-18 08:23:56 EST

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-2017:3464

Note You need to log in before you can comment on or make changes to this bug.