Bug ID 1785621: Tenant deployed with Max Memory available on system results in Resource allocation failed - Node is up but Platform services not responding

Last Modified: Oct 19, 2025

Affected Product(s):
F5OS Velos(all modules)

Fixed In:
F5OS-C 1.8.1

Opened: Jan 10, 2025

Severity: 3-Major

Symptoms

Tenant fails to come to running state when deployed with max memory on system.

Impact

Tenant fails to come to running state.

Conditions

Tenant is deployed with max-available memory on the blade in prior releases of F5OS-C 1.8.1 version.

Workaround

Since the max memory available for tenants on blade is corrected in F5OS-C-1.8.1, the tenant memory should be configured accordingly. Step 1. Move failed tenant to configured state and adjust the memory to the new max-available memory of the tenant. Step 2. Move the tenant back to the deployed state.

Fix Information

Max memory available on system for tenant deployment has been corrected with right value.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips