-
Bug
-
Resolution: Done
-
Undefined
-
4.12
-
Moderate
-
None
-
SDN Sprint 229
-
1
-
False
-
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.
compute:
- name: worker
platform:
openstack:
zones: []
additionalNetworkIDs: ['0eeae16f-bbc7-4e49-90b2-d96419b7c30d']
replicas: 3
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 .
[
{
"interface": "207beb76-5476-4a05-b412-d0cc53ab00a7",
"ifaddr": {
"ipv4": "10.46.44.64/26"
},
"capacity": {
"ip": 8
}
},
{
"interface": "2baf2232-87f7-4ad5-bd80-b6586de08435",
"ifaddr": {
"ipv4": "172.17.5.0/24"
},
"capacity": {
"ip": 10
}
}
]
According to huirwang, egressIP only works for primary interface on the node.
Version-Release number of selected component (if applicable):
4.12.0-0.nightly-2022-11-22-012345 RHOS-16.1-RHEL-8-20220804.n.1
How reproducible:
Always
Steps to Reproduce:
Deploy cluster with additional Network on the workers
Actual results:
It is possible to select an egressIP network for a secondary interface
Expected results:
Only primary subnet can be chosen for egressIP
Additional info:
https://issues.redhat.com/browse/OCPQE-12968
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to