Bug ID 1020277: Mcpd may run out of memory when build image is missing

Last Modified: Jun 10, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP Install/Upgrade, LTM(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, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1

Opened: May 20, 2021
Severity: 3-Major

Symptoms

After installing a new blade, if the BIG-IP does not have the appropriate images to install all volumes onto the new blade, it can get stuck waiting to install. This may cause mcpd to eventually run out of memory. Running "tmsh show sys software" shows a message similar to this for a prolonged period of time: HD1.2 3 BIG-IP 12.1.3.5 0.0.10 no waiting for product image (BIG-IP 12.1.3)

Impact

Mcpd eventually runs out of memory and cores.

Conditions

-- Installing a new blade into a chassis-based system. -- Missing BIG-IP image(s) necessary to update all volumes on the new blade.

Workaround

Either delete the affected volume if it is no longer necessary, or copy the appropriate BIG-IP image to /shared/images.

Fix Information

None

Behavior Change