Last Modified: Dec 17, 2020
See more info
Known Affected Versions:
14.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 14.1.2, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 14.1.3, 188.8.131.52, 15.0.0, 15.0.1, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124
Opened: Oct 26, 2018
If BIG-IP images are run on Azure D2_V3 or D4_V3 instance types, mcpd may fail to start correctly and be killed either by the kernel's hung process watchdog, or from a SIGABRT from sod. This prevents the instance from being able to operate normally. Support for these instance types has not been added yet.
The system may run fine, but in some cases it has been observed that mcpd will fail to start properly and be killed. If this occurs, the system will fail to operate normally.
BIG-IP running within Azure cloud environment utilizing D2_V3 or D2_V4 instances.
Run on a V2 instance.