-
Bug
-
Resolution: Not a Bug
-
Blocker
-
None
-
CentOS Stream 9, rhel-9.2.0.z, rhel-9.4.z
-
None
-
No
-
Important
-
rhel-sst-network-management
-
ssg_networking
-
None
-
Customer/Partner Case ID Jira ID Status Details OpenStack 17.1 N/A RHEL-59977This issue starts when configuring DPDK ports on SR-IOV VFs, leading to a system hang and verification failure after the initial successful setup. The problem might be related to either a kernel bug or hardware firmware, and an investigation spike has been created to determine the root cause. The team is currently analyzing logs and reproducing the issue to identify potential solutions. Next steps include reviewing findings and proposing a resolution or escalation to kernel/hardware teams if necessary.
[2024-10-07] The investigation is still ongoing using NMT-1198 as top priority within the current sprint.
[2024-10-21] This ticket is now closed because the issues were identified as unrelated to NetworkManager or Nmstate, with one being caused by dpdk-devbind.py binding VFs incorrectly and the other being an SELinux labeling issue preventing communication between NetworkManager and the OVS daemon.Customer/Partner Case ID Jira ID Status Details OpenStack 17.1 N/A RHEL-59977 This issue starts when configuring DPDK ports on SR-IOV VFs, leading to a system hang and verification failure after the initial successful setup. The problem might be related to either a kernel bug or hardware firmware, and an investigation spike has been created to determine the root cause. The team is currently analyzing logs and reproducing the issue to identify potential solutions. Next steps include reviewing findings and proposing a resolution or escalation to kernel/hardware teams if necessary. [2024-10-07] The investigation is still ongoing using NMT-1198 as top priority within the current sprint. [2024-10-21] This ticket is now closed because the issues were identified as unrelated to NetworkManager or Nmstate, with one being caused by dpdk-devbind.py binding VFs incorrectly and the other being an SELinux labeling issue preventing communication between NetworkManager and the OVS daemon. -
False
-
-
None
-
Red Hat OpenStack Services on OpenShift (formerly Red Hat OpenStack Platform)
-
None
-
None
-
None
-
None
What were you trying to do that didn't work?
Os-net-config performed a sequence of steps to setup DPDK on VF.
What is the impact of this issue to you?
nmstate is able to create the dpdk ports over a VF. but when the same templates are repeated, we get verification error. At this point accessing the sysfs path for numvfs stalls the system (cat /sys/class/net/enp5s0f0/device/sriov_numvfs )
Please provide the package NVR for which the bug is seen:
How reproducible is this bug?:
100%
Steps to reproduce
- run template1.yaml
- run template2.yaml
- Bind the drivers with VFs
- run template3.yaml to create the DPDK ports - The dpdk ports were successfully created
- run template4.yaml
- run template5.yaml
Expected results
The Vfs shall be configured as it was , The ovs bridges shall be setup with the DPDK ports attached.
Actual results
Verification failure: enp5s0f0.interface.ethernet.sr-iov.total-vfs desire '5', current '0'
And accessing the sysfs for numvfs stalls the system
cat /sys/class/net/enp5s0f0/device/sriov_numvfs => System hangs
