Last Modified: Oct 19, 2025
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-A 1.8.0, F5OS-A 1.8.3
Opened: Jan 15, 2025 Severity: 3-Major
On r2x00/r4x00 related systems, tenant launch fails with an error in ConfD tenant status leaf: "error adding container to network "sriov-net3-bip1": failed to set up pod interface "net7" from the device "x557_4": failed to set netlink MAC address to <mac>: resource temporarily unavailable" or "SRIOV-CNI failed to load netconf: LoadConf(): the VF 0000:ec:01.3 does not have a interface name or a dpdk driver" Linux network manager udev rules and sriov cni try to access the VF and change the interface name of VF. During this process, VFs fail and unable to retrieve. Thus, resource temporarily unavailable error occurs.
Tenant launch is unsuccessful and unable to connect to the tenant console or tenants' management connection.
On r4x00 or r2x00 based systems: 1. In kubectl get pods -A output, the tenant pod goes into Init:0/1 state. default virt-launcher-bip1-1-t6rkh 0/1 Init:0/1 0 36s 2. And in kubectl events, "resource temporarily unavailable" occurs on one of the VFs. 3. In /sys/class/net folder unable to see the below VF interfaces. Instead, some interfaces point to ensp* names which are wrong.
1. Set all tenants to the Configured state. 2. Reboot the appliance. 3. Once the system is up, change one tenant’s state to Deployed at a time, allowing a gap of 3–5 minutes before moving to the next tenant. 4. Repeat this process until all tenants are deployed.
None