Cannot set max-tx-rate parameter on N3000 FPGA SR-IOV interface
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Steven Webster |
Bug Description
Brief Description
-----------------
After setting the max-tx-rate on an SR-IOV interface belonging to an N3000 FPGA device, the system may fail to go enabled after unlock.
Severity
--------
Major: System/Feature is usable but degraded
Steps to Reproduce
------------------
Must be performed on an N3000 FPGA network interface (vendor 8086 device 0d58)
- system host-lock
- system host-if-modify <host> <interface_name> -c pci-sriov -N <number of vfs> --max-tx-rate <max_tx_rate>
- system host-unlock
After unlock, the system may fail to go enabled if puppet configures the max-tx-rate on the VFs after the device is reset but before it is brought down/up.
Expected Behavior
------------------
After unlock, the system should be enabled and the SR-IOV VFs should have the appropriate max-tx-rate.
Actual Behavior
----------------
In some cases, the system fails to come up after unlock.
Reproducibility
---------------
intermittent
System Configuration
-------
N3000 FPGA required on AIO/Standard
Branch/Pull Time/Commit
-------
master
Test Activity
-------------
Testing
Workaround
----------
A reboot/lock/unlock may resolve the problem.
Changed in starlingx: | |
importance: | Undecided → High |
status: | New → In Progress |
screening: stx.7.0 / medium - specific failure w/ a particular config; workaround exists. Sufficient to fix in the active branch.