Bug ID 591039: DHCP lease is saved on the Custom AMI used for auto-scaling VE

Last Modified: Oct 01, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP 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

Fixed In:
12.1.0 HF1

Opened: May 03, 2016
Severity: 2-Critical

Symptoms

When configuring the instance for auto-scaling purpose and subsequently generating the Custom/Model AMI that is used for autoscaling VEs, the new instances generated from this image, might have the old DHCP lease acquired by the custom instance before an AMI was generated from it. This can collide with the new lease that the new instances get in their boot-up.

Impact

Multiple valid DHClient leases exist, which could result dhclient in BIG-IP choosing wrong IP address for the management interface.

Conditions

This occurs when Auto-scaling VEs.

Workaround

Delete the /var/lib/dhclient/dhclient.leases before shutting down the custom instance and generating a Custom/Model AMI out of it.

Fix Information

Auto-scaling AMI will no longer contain a DHCP lease when they are saved.

Behavior Change