-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
2
-
False
-
-
False
-
?
-
os-net-config-18.0.1-18.0.20250220204730.22b9a65.el9ost
-
rhos-connectivity-nfv
-
None
-
-
-
NFV 003, NFV 004, NFV 005, NFV 006
-
4
-
2025Q1
-
Critical
To Reproduce Steps to reproduce the behavior:
Applying a configuration like this:
- type: ovs_user_bridge name: br-link0 use_dhcp: false mtu: 9000 ovs_extra: "set port br-link0 tag=121" addresses: - ip_netmask: 10.10.121.155/24 use_dhcpv6: false members: - type: ovs_dpdk_bond name: dpdkbond0 mtu: 9000 rx_queue: 1 members: - type: ovs_dpdk_port name: dpdk0 members: - type: sriov_vf device: nic7 vfid: 0 - type: ovs_dpdk_port name: dpdk1 members: - type: sriov_vf device: nic8 vfid: 0
This error is raised:
2025-01-23 11:43:56.895 ERROR os_net_config.impl_nmstate.nmstate_apply **** Verification Error ***** 2025-01-23 11:43:56.896 ERROR os_net_config.impl_nmstate.nmstate_apply Error seen while applying the nmstate templates Verification failure: dpdk1.interface.mtu desire '9000', current 'null' 2025-01-23 11:43:58.240 ERROR os_net_config.impl_nmstate.apply Failure(s) occurred when applying configuration 2025-01-23 11:43:58.240 ERROR os_net_config.impl_nmstate.apply Verification failure: dpdk1.interface.mtu desire '9000', current 'null'
Adding or removing the mtu field everywhere there doesn't solve the problem (same error raised)
os-net-config version (RHOSP 17.1): os-net-config-18.0.1-18.0.20241215105304.22b9a65
Expected behavior
VF configuration is configured without errors
- links to
-
RHBA-2025:146621
Release of components for RHOSO 18.0
