Bug ID 719241: Using custom DNS servers on the Azure VNet with the missing 168.63.129.16 causes Waagent provisioning failure.

Last Modified: May 14, 2019

Bug Tracker

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

Known Affected Versions:
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

Opened: May 09, 2018
Severity: 4-Minor

Symptoms

During the BIG-IP system boot-up, waagent is unable to get a response from the intended wire server endpoint, which stops it from running custom script extensions. This happens because of the missing route to the Azure virtual public IP address of 168.63.129.16. The var/log/waagent.log contains error messages similar to the following: -- INFO Protocol endpoint not found: WireProtocol, [ProtocolError] [Wireserver Exception] [HttpError] [HTTP Failed] GET http://n.n.n.n,n.n.n.n/?comp=versions -- IOError [Errno -3] Temporary failure in name resolution -- 6 attempts made

Impact

waagent custom script extensions do not complete, failing the BIG-IP provisioning that waagent intends to perform during startup.

Conditions

-- BIG-IP system is deployed in Azure VNet with a custom DNS server. -- The DHCP server has assigned a classless-static-route in its dhclient lease (/var/lib/dhclient/dhclient.leases) which contains a custom route to 168.63.129.16.

Workaround

Add 168.63.129.16 route on mgmt interface during BIG-IP system initialization to facilitate correct waagent custom script extension execution.

Fix Information

None

Behavior Change