Bug ID 557642: Manually created backend nodes should not be added to a pool that is managed by AWS Auto Scaling Group.

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1

Opened: Nov 11, 2015
Severity: 4-Minor

Symptoms

Autoscale pool manager reports at every iteration in /var/log/ltm that it wants to delete a pool member but fails to do so.

Impact

/var/log/ltm is full of error messages. No actual impact on the traffic.

Conditions

Applies only to pool member autoscale in AWS. Happens only if you manually add a backend node to a pool that is managed by AWS Auto Scaling Group.

Workaround

Manually delete the pool member that has been manually added to the pool. Note: Manually created backend nodes should not be manually added to a pool that is managed by AWS Auto Scaling Group. Autoscale pool manager will detect that the offending pool member was not created by the AWS Auto Scaling Group. It will try to delete the pool member from the pool, an operation that will likely fail. This will be repeated at every iteration of the autoscale pool manager, which fills /var/log/ltm with error messages.

Fix Information

None

Behavior Change