Last Modified: Oct 19, 2025
Affected Product(s):
F5OS F5OS, Install/Upgrade
Known Affected Versions:
F5OS-A 1.8.0
Fixed In:
F5OS-A 1.8.3
Opened: Feb 10, 2025 Severity: 1-Blocking
A tenant fails to deploy. The output of the 'show tenant' command: INSTANCE TENANT CREATION READY MGMT NODE POD NAME ID SLOT PHASE TIME TIME STATUS MAC ------------------------------------------------------------------------------------------------------------------------------ 1 tenant-1 1 1 Insufficient memory on node, retrying tenant deployment - Errors in platform.log: 2024-12-21T16:19:02.370251+08:00 TENANT-1 orchestration-agent[7]: priority="Err" version=1.0 msgid=0x506000000000042 msg="Failed to allocate memory for tenant" TENANT="tenant-1" node=1. 2024-12-21T16:19:35.547187+08:00 TENANT-1 orchestration-agent[7]: priority="Err" version=1.0 msgid=0x507000000000004 msg="Unable to fetch VFs pci address from filesystem". 2024-12-21T16:19:40.757952+08:00 TENANT-1 orchestration-agent[7]: priority="Info" version=1.0 msgid=0x507000000000006 msg="SR-IOV DP pod is at running/ready state, able to access VFs". 2024-12-21T16:20:12.814467+08:00 TENANT-1 orchestration-agent[7]: priority="Err" version=1.0 msgid=0x506000000000040 msg="Timeout waiting for response from NodeAgent" TENANT="tenant-1" NODE=1. 2024-12-21T16:20:12.814506+08:00 TENANT-1 orchestration-agent[7]: priority="Err" version=1.0 msgid=0x506000000000042 msg="Failed to allocate memory for tenant" TENANT="tenant-1" node=1.
Tenants will not start. The GUI reports "Insufficient memory on node, retrying tenant deployment".
Exact conditions are unknown. It has been observed after upgrading from F5OS 1.5.2 to 1.8.0.
None
None