Bug ID 638997: Reboot required after disk size modification in a running BIG-IP VE instance.

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP MA-VE(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0, 12.1.3

Opened: Jan 12, 2017
Severity: 2-Critical

Symptoms

- BIG-IP VE supports disk size modification during the lifetime of a running instance to expand or reduce the disk size that was allocated at the time of deployment. - A reboot is required after any such modification in the disk size for the changes to take effect. In previous versions, the reboot happened automatically but an affected BIG-IP VE will not have the reboot happening automatically. - Due to the lack of reboot, changes in disk size do not take effect on the BIG-IP system.

Impact

Changes in the disk size do not take effect till BIG-IP system is rebooted.

Conditions

Modifying disk size in a running BIG-IP VE instance.

Workaround

Manually reboot the running BIG-IP VE instance after making changes in disk size.

Fix Information

Reboot required after disk size modification in a BIG-IP VE instance.

Behavior Change