-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
0
-
False
-
-
False
-
?
-
os-net-config-18.0.1-18.0.20250926134653.22b9a65.el9osttrunk.src.rpm
-
rhos-connectivity-nfv
-
None
-
-
-
-
Bugs Pending Verification
-
1
-
Low
To Reproduce Steps to reproduce the behavior:
- Deploy a NIC partitioning template. The template shall have DPDK ports on VFs.
network_config: - type: sriov_pf name: nic3 mtu: 9000 numvfs: 5 use_dhcp: false defroute: false nm_controlled: true hotplug: true drivers_autoprobe: false - type: sriov_pf name: nic4 mtu: 9000 numvfs: 5 use_dhcp: false defroute: false nm_controlled: true hotplug: true drivers_autoprobe: false - type: ovs_user_bridge name: br-link0 nm_controlled: true use_dhcp: false mtu: 9000 ovs_extra: "set port br-link0 tag=74" addresses: - ip_netmask: 172.19.0.100/24 members: - type: ovs_dpdk_bond nm_controlled: true name: dpdkbond0 mtu: 9000 rx_queue: 1 members: - type: ovs_dpdk_port name: dpdk0 members: - type: sriov_vf device: nic3 vfid: 3 - type: ovs_dpdk_port name: dpdk1 members: - type: sriov_vf device: nic4 vfid: 3
- After successful network configuration, manually remove the DPDK port, and unbind the vfio-pci driver
- Re-run os-net-config to apply the network-config
Expected behavior
- The DPDK ports shall be created and the VF driver shall be correctly configured
Actual behavior
- The DPDK ports are created but the VF driver is not bound with vfio-pci, leaving the dpdk port in a chaotic state
Bug impact
- The bug is reproducible only with manual intervention or remove-config usage.
Known workaround
No
