egressIP access issue after running 'pod-network join-project' between namespaces in openshift 3.11

Solution Verified - Updated -

Issue

Using EgressIP on joined Namespaces is not supported, see:
https://access.redhat.com/solutions/4395291

However, it may be the case that after accidentally joining two namespaces that were reliant on EgressIP, separating these namespaces does not have the desired effect of returning the projects to functionality with a bound egressIP.

Steps taken:
$ oc adm pod-network join-projects --to=<project1> <project2>
$ oc adm pod-network isolate-projects <project1> <project2>

  • Observe that egress IP fails to rebind to one or both projects after isolation.

  • Observe that sdn pods now throw alert regarding multiple namespaces binding the same EgressIP, and one of the netID's listed does not exist:

E1117 20:27:45.851079   15851 egressip.go:371] Multiple namespaces (7050864, 4742567) claiming EgressIP 10.xxx.xxx.101

Environment

OpenShift Container Platform (OCP) 3.11
Using ovs-multitenant sdn plugin

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content