Bug ID 495523: MCPd goes into a restart loop after changing the AWS Instance Type

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Opened: Dec 09, 2014
Severity: 3-Major

Symptoms

MCPd goes into a restart loop after a change to the AWS Instance Type.

Impact

The instance is not usable. There is no error message to indicate the failure.

Conditions

This occurs in Virtual Edition (VE) after changing the underlying instance hardware in AWS.

Workaround

You can save the configuration on the BIG-IP system, instantiate a instance of the desired type, and apply the saved configuration. Note: In later versions of the software (version 12.1.0 and later), if you have a PAYG or BYOL, you can change the instance as long as you have set up the AWS API keys.

Fix Information

None

Behavior Change