-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.14, 4.16
-
None
-
None
-
False
-
Description of problem:
nncp route-rules applied on the OCP cluster breaks br-ex connectivity by configuring the route-rules on br-ex device (ovs-if-br-ex) below the nncp route-rules apiVersion: nmstate.io/v1 kind: NodeNetworkConfigurationPolicy metadata: name: egress-policy spec: desiredState: route-rules: config: - ip-to: 100.77.77.0/26 priority: 5550 route-table: 254 nodeSelector: node-role.kubernetes.io/gateway: ""
Version-Release number of selected component (if applicable):
kubernetes-nmstate-operator.4.16.0-202407181806
How reproducible:
always
Steps to Reproduce:
1. Apply nncp above with specified priority in table 254 2. Check ip rules is applied : ip rule list 3. Check in which interface the route-rule is applied: for c in $(nmcli -f UUID c show|grep -); do nmcli c show $c |grep routing; done
Actual results:
nncp is applied on br-ex device (ovs-if-br-ex) for some reason
Expected results:
nncp add route-rules without applying it on br-ex device
Additional info: