Bug 1533153 - New auto egress IPs will fail after restarting node service
Summary: New auto egress IPs will fail after restarting node service
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.9.0
Assignee: Dan Winship
QA Contact: Meng Bo
URL:
Whiteboard:
: 1554923 (view as bug list)
Depends On:
Blocks: 1535658 1535659
TreeView+ depends on / blocked
 
Reported: 2018-01-10 15:35 UTC by Dan Winship
Modified: 2018-07-23 08:07 UTC (History)
4 users (show)

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.
Clone Of:
: 1535658 1535659 (view as bug list)
Environment:
Last Closed: 2018-03-28 14:19:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Origin (Github) 18049 0 None None None 2018-01-17 20:28:11 UTC
Red Hat Product Errata RHBA-2018:0489 0 None None None 2018-03-28 14:19:32 UTC

Description Dan Winship 2018-01-10 15:35:44 UTC 
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 15:36:48 UTC 
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 14:51:37 UTC 
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 20:36:39 UTC 
*** Bug 1554923 has been marked as a duplicate of this bug. ***
Comment 7 errata-xmlrpc 2018-03-28 14:19:05 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-2018:0489
Note You need to log in before you can comment on or make changes to this bug.