Last Modified: Jul 02, 2025
Affected Product(s):
F5OS F5OS-A
Fixed In:
F5OS-A 1.7.0
Opened: Jun 22, 2023 Severity: 2-Critical
On r2k or r4k systems, the VFs creation process under each PF were intermittently not having relevant sysfs entries under each VF created. 1. Not all the 4VFs are created under a PF(Ex: ip link show <PF>) 2. `driver` soft link is not created for VF in sysfs 3. `net` directory is missing for VF in sysfs 4. `net` directory had no entries when creating a new VF in sysfs
Tenant creation stalls as there are insufficient/Unready/Unhealth VFs to consume for Datapath.
When the r2k or r4k system boots up, VF creation under each PF gets triggered and checks for the VF state and retries the VF creation, if we hit any of the following: 1. Not all the 4VFs are created under a PF(Ex: ip link show <PF>) 2. `driver` soft link is not created for VF in sysfs 3. `net` directory is missing for VF in sysfs 4. `net` directory had no entries when creating a new VF in sysfs
Even on six retrials for about three minutes after booting the system, if the VF creation does not succeed, reboot the host system with a message(s) in /var/log/messages. "Intel NIC PFs/VFs are not ready to deploy tenant(s). Only ${valid_pf_count}/${no_of_active_pfs} PFs had valid VFs. Suggest to reboot host system. " "Intel NIC PFs/VFs are not ready to deploy tenant(s). Suggest to reboot host system."
Fixed validating the VF entries in sysfs. Added finite retrials to recreate VFs, if found unhealthy. If the finite retrials, not helped recovering the VFs, suggests to reboot the host system.