Bug 1535659 - [3.8] New auto egress IPs will fail after restarting node service
Summary: [3.8] New auto egress IPs will fail after restarting node service
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.8.0
Assignee: Casey Callendrello
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On: 1533153
Blocks: 1535658
TreeView+ depends on / blocked
 
Reported: 2018-01-17 20:31 UTC by Ben Bennett
Modified: 2019-12-05 21:59 UTC (History)
7 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: 1533153
Environment:
Last Closed: 2019-12-05 21:59:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ose pull 1041 0 None None None 2019-12-05 21:44:20 UTC
Origin (Github) 18049 0 None None None 2018-01-17 20:31:01 UTC

Description Ben Bennett 2018-01-17 20:31:02 UTC 
+++ This bug was initially created as a clone of Bug #1533153 +++

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

--- Additional comment from Dan Winship on 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 1 Dan Winship 2018-01-31 14:39:23 UTC 
https://github.com/openshift/ose/pull/1041
Comment 3 Meng Bo 2018-03-07 10:44:29 UTC 
The bug has been fixed on v3.9.3
Note You need to log in before you can comment on or make changes to this bug.