Bug 1533153 – New auto egress IPs will fail after restarting node service

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

Bug 1533153 - New auto egress IPs will fail after restarting node service

Summary:	New auto egress IPs will fail after restarting node service

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	medium Severity medium
Target Milestone:	---
Target Release:	3.9.0
Assigned To:	Dan Winship
QA Contact:	Meng Bo
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	1554923 (view as bug list)
Depends On:
Blocks:	1535659 1535658
	Show dependency tree / graph

Reported:	2018-01-10 10:35 EST by Dan Winship
Modified:	2018-07-23 04:07 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Cause: Certain initialization code was only run when doing a full SDN setup, and not when OpenShift was restarted and found the SDN was already up and running. Consequence: If the atomic-openshift-node service was restarted, that node would be unable to create new per-project static egress IPs (HostSubnet.EgressIPs). Fix: The egress IP initialization code is now run in all circumstances. Result: Per-project static egress IPs work correctly, even after a node restart.
Story Points:	---
Clone Of:
Clones:	1535658 1535659 (view as bug list)
Environment:
Last Closed:	2018-03-28 10:19:05 EDT
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
Origin (Github)	18049	None	None	None	2018-01-17 15:28 EST
Red Hat Product Errata	RHBA-2018:0489	None	None	None	2018-03-28 10:19 EDT

Groups: None (edit)

Description Dan Winship 2018-01-10 10:35:44 EST

Description of problem:
After a "simple" restart of a node (such that it doesn't need to re-setup the SDN), newly-created egress IPs won't work correctly

Steps to Reproduce:
1. Start a cluster
2. On one of the nodes, "systemctl restart atomic-openshift-node"
3. Add an auto-egress-IP to that node

Actual results:
Newly-added egress IP doesn't work, and there's an ovs-related error in the journal for that node

Expected results:
Works

Comment 1 Dan Winship 2018-01-10 10:36:48 EST

https://github.com/openshift/origin/pull/18049 fixes this for master. I'll update when there's a backport to 3.7.

Comment 3 Meng Bo 2018-01-30 09:51:37 EST

Tested on build 3.9.0-0.31.0 
Issue has been fixed, egress IP works well after node restart

Comment 4 Dan Winship 2018-03-17 16:36:39 EDT

*** Bug 1554923 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2018-03-28 10:19:05 EDT

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-2018:0489

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