Bug ID 1707921: Tenant upgrade fails with disk full error on BIG-IP 17.x created with T2 image

Last Modified: Jun 19, 2025

Affected Product(s):
BIG-IP Install/Upgrade(all modules)

Known Affected Versions:
17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2

Opened: Oct 23, 2024

Severity: 2-Critical

Symptoms

Upgrade failed with "disk full" error in 17.1.x version. ----------------------------------------------------------------------------------------------------------- Sys::Software Status Volume Product Version Build Active Status Allowed Version ----------------------------------------------------------------------------------------------------------- HD1.1 BIG-IP 17.1.1.4 0.0.9 yes complete yes HD1.2 BIG-IP 17.1.1.3 0.0.5 no failed (Disk full (volume group). See SOL#10636)

Impact

Creation of additional boot location fails with "disk full" error.

Conditions

- Deployed BIG-IP tenant with v17.x.x T2 image - Trying to create an additional boot location

Workaround

Expand the tenant's virtual disk (storage-size) from F5OS to accommodate an additional boot location in the tenant. Values of 46G/47G have worked well in lab testing.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips