Last Modified: Jul 28, 2026
Affected Product(s):
BIG-IP Install/Upgrade, TMOS
Known Affected Versions:
17.5.1.6, 17.5.1.8
Opened: May 21, 2026 Severity: 2-Critical
- After installing a BIG-IP v17.5.1.6 Engineering Hotfix or the BIG-IP v17.5.1.6 release itself, the /usr volume continues to show 100% used, with 0 free space available. This occurs even if the Engineering Hotfix includes the fix for ID2296269. - This may cause other operations to fail, such as updating any components that would require available space in the /usr volume. The lack of available /usr volume space may also cause internal process failures, which would block the release of BIG-IP v17.5.1.6 Engineering Hotfixes.
Operations such as updating any components that would require available space in the /usr volume may fail in unexpected ways
This may occur after installing a BIG-IP v17.5.1.6 Engineering Hotfix, including one that contains a fix for ID2296269, or the BIG-IP v17.5.1.6 release itself. Note that this issue only occurs on BIG-IP 17.5.1.6, due to incorrect volume sizing metadata applied when creating the /usr volume during installation of the BIG-IP 17.5.1.6 release image. This condition is specific to the BIG-IP 17.5.1.6 release only. This issue is addressed by BIG-IP 17.5.1.6 Engineering Hotfixes which contain code to expand the size of the /usr volume during Engineering Hotfix installation, prior to installing the Engineering Hotfix. This solution was first implemented under ID2291757, then refined by the fix for ID2296269, then further refined by the fix for ID2298081. This incorrect volume sizing metadata issue is resolved under ID2301585 for BIG-IP 17.5.1.8 and later.
-- See KB article K000161170: https://my.f5.com/manage/s/article/K000161170 Follow option B. -- Obtain a BIG-IP 17.5.1.6 Engineering Hotfix with the fix for ID2298081. The generally recommended solution is to upgrade to BIG-IP 17.5.1.8 or later.
None