This is a clone of issue
OCPBUGS-3993. The following is the description of the original issue:
Description of problem:
On Openshift on Openstack CI, we are deploying an OCP cluster with an additional network on the workers in install-config.yaml for integration with Openstack Manila.
- name: worker
As a result, the egressIP annotation includes two interfaces definition:
$ oc get node ostest-hp9ld-worker-0-gdp5k -o json | jq -r '.metadata.annotations["cloud.network.openshift.io/egress-ipconfig"]' | jq .
According to huirwang, egressIP only works for primary interface on the node.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Deploy cluster with additional Network on the workers
It is possible to select an egressIP network for a secondary interface
Only primary subnet can be chosen for egressIP