Last Modified: Jan 19, 2023
Opened: Sep 27, 2022
If the BIG-IP tenant disk space is fully used by creating multiple software volumes within the tenant, it will generate disk errors.
Software installs within the tenant may fail.
- A tenant originally deployed from an “ALL-F5OS” tenant image (i.e., BIGIP-188.8.131.52-0.0.10.ALL-F5OS.qcow2.zip.bundle) originally created from one of the following: -- 14.1.5 or above in the 14.1.x branch of code -- 184.108.40.206 or above in the 15.1.x branch of code - The tenant is configured to use 76G of disk space (the default)
Beginning in F5OS-A 1.3.0, the system detects the minimum size of a disk created from a tenant image file, and enforces that minimum on newly-created tenants. If a customer has a tenant affected by this issue and upgrades their system to F5OS-A 1.3.0 or later, set the tenant to "configured", and then deploy the tenant again. If the disk size is not right, the system will show the minimum size, then adjust the tenant disk size to what is advised by the system or larger. From 1.4.0, user does not need to adjust the size unless the user needs a bigger size. The right/minimum size will be auto-allocated when the state is changed.
The tenant disk size will be detected and auto-allocated.
There are two behaviors. 1.3.x: If the disk size is smaller than it has to be, it warns the user and doesn't start the tenant until the user specifies the right/minimum size. 1.4.0: It auto increases the size to the right/minimum size if the user didn't specify the disk size.