-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.17
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The nmstatectl config described under the section Example: Bonds and SR-IOV dual-nic node network configuration its not working properly.
Version-Release number of selected component (if applicable):
4.17.14
How reproducible:
Steps to Reproduce:
1. use the nmstatectl config from here:
networkConfig:
interfaces:
- name: eno1
type: ethernet
state: up
mac-address: 0c:42:a1:55:f3:06
ipv4:
enabled: true
dhcp: false
ethernet:
sr-iov:
total-vfs: 2
ipv6:
enabled: false
- name: sriov:eno1:0
type: ethernet
state: up
ipv4:
enabled: false
ipv6:
enabled: false
dhcp: false
- name: sriov:eno1:1
type: ethernet
state: down
- name: eno2
type: ethernet
state: up
mac-address: 0c:42:a1:55:f3:07
ipv4:
enabled: true
ethernet:
sr-iov:
total-vfs: 2
ipv6:
enabled: false
- name: sriov:eno2:0
type: ethernet
state: up
ipv4:
enabled: false
ipv6:
enabled: false
- name: sriov:eno2:1
type: ethernet
state: down
- name: bond0
type: bond
state: up
min-tx-rate: 100
max-tx-rate: 200
link-aggregation:
mode: active-backup
options:
primary: sriov:eno1:0
port:
- sriov:eno1:0
- sriov:eno2:0
ipv4:
address:
- ip: 10.19.16.57
prefix-length: 23
dhcp: false
enabled: true
ipv6:
enabled: false
dns-resolver:
config:
server:
- 10.11.5.160
- 10.2.70.215
routes:
config:
- destination: 0.0.0.0/0
next-hop-address: 10.19.17.254
next-hop-interface: bond0
table-id: 254
2. the following changes are required to make the logic of nmstatectl work in the context of OCP:
config:
dns-resolver:
config:
server:
- 172.16.30.1
routes:
config:
- destination: 0.0.0.0/0
next-hop-address: 172.16.30.1
next-hop-interface: bond0
table-id: 254
interfaces:
- name: enp1s0
type: ethernet
state: up
mac-address: "AA:AA:AA:AA:02:01"
mtu: 1500
ipv4:
enabled: false
dhcp: false
ethernet:
sr-iov:
total-vfs: 2
ipv6:
enabled: false
dhcp: false
- name: enp1s0v0
type: ethernet
state: up
ipv4:
enabled: false
dhcp: false
ipv6:
enabled: false
dhcp: false
- name: enp1s0v1
type: ethernet
state: down
- name: enp2s0
type: ethernet
state: up
mac-address: "AA:AA:AA:AA:02:02"
mtu: 1500
ipv4:
enabled: false
dhcp: false
ethernet:
sr-iov:
total-vfs: 2
ipv6:
enabled: false
dhcp: false
- name: enp2s0v0
type: ethernet
state: up
ipv4:
enabled: false
dhcp: false
ipv6:
enabled: false
dhcp: false
- name: enp2s0v1
type: ethernet
state: up
ipv4:
enabled: false
dhcp: false
ipv6:
enabled: false
dhcp: false
- name: bond0
type: bond
state: up
#min-tx-rate: 100
#max-tx-rate: 200
link-aggregation:
mode: active-backup
options:
primary: enp1s0v0
# miimon: "150"
port:
- enp1s0v0
- enp2s0v0
ipv4:
address:
- ip: 172.16.30.30
prefix-length: 24
dhcp: false
enabled: true
ipv6:
enabled: false
dhcp: false 3.
Actual results:
NetworkManager it snot able to create the bond0 and inbound and outbound traffic reach the cluster. the NetworkManager its generating the configuration files using the sriov:<interface_name>:0.ini which is causing the service to fail.
Expected results:
NetworkManager be able to create the bond0 and inbound and outbound traffic reach the cluster
Additional info: