-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
rhel-9.2.0
-
None
-
Low
-
rhel-net-mgmt
-
ssg_networking
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
x86_64
-
None
-
0
Description of problem:
When applying a desire state of nmstate setting SR-IOV `min-rx-rate` on some i40e card, user get failure like:
```
NmstateError: VerificationError: Verification failure: ens1f0.interface.ethernet.sr-iov.total-vfs desire '5', current '0'
```
This give user a wrong impression that nmstate/NetworkManager failure to activate the SR-IOV.
But the actual failure is:
```
kernel: i40e 0000:3b:00.0: Invalid min tx rate (100) (greater than 0) specified for VF 2.
```
When NetworkManager failed to set SR-IOV parameters, NM will disable SRIOV setting which lead to nmstate found SR-IOV been disabled during verification stage.
Version-Release number of selected component (if applicable):
nmstate-2.2.10-3.el9
How reproducible:
100%
Steps to Reproduce:
1. Apply this desire state on i40e card which does not support setting `min-tx-rate`:
```
interfaces:
- name: ens1f0
type: ethernet
description: Change QOS on VF0
state: up
ethernet:
sr-iov:
total-vfs: 5
vfs: - id: 2
min-tx-rate: 100
max-tx-rate: 200
```
Actual results:
VerificationError: Verification failure: ens1f0.interface.ethernet.sr-iov.total-vfs desire '5', current '0'
Expected results:
InvalidArgument: Invalid SR-IOV parameter for interface ens1f0: kernel: i40e 0000:3b:00.0: Invalid min tx rate (100) (greater than 0) specified for VF 2.
Additional info:
- external trackers