Bug ID 744730: After increasing the disk size on a VE or VCMP guest a manual reboot is required for the increase to go into effect.

Last Modified: Sep 14, 2023

Affected Product(s):
BIG-IP MA-VE(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6

Fixed In:
15.0.0

Opened: Sep 20, 2018

Severity: 3-Major

Symptoms

When the disk on a BIG-IP Virtual Edition (VE) or VCMP guest is increased the larger disk will be allocated, but VE or VCMP guest will not be able to use the extra space initially. A Manual reboot will allow the system to use the extra space. The Desired behavior for BIG-IP is to reboot by itself.

Impact

BIG-IP cannot use the extra space.

Conditions

This occurs when you launch BIG-IP Virtual Edition or VCMP guest with a larger system disk than was provisioned initially.

Workaround

Manually reboot the affected system.

Fix Information

If a larger system disk size is specified during BIG-IP Virtual Edition launch, it will be allocated. But it will not be able to use the extra space initially. Manual reboot will allow BIG-IP Virtual Edition to use the extra space.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips