Aria Automation Infoblox IPAM: IP addresses are not de-allocated on VM deletion: "No Infoblox records found for IP #.#.#.#"

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• This may occur when onboarding new VMs that already have an IP associated in Infoblox.
• The IP reservation in Infoblox for the VM is of type "IPv4 Reservation", not "host". 
• The following result is seen in the IPAM deallocation workflow:
  • [INFO] - No Infoblox records found for IP #.#.#.#

Environment

• VMware Aria Automation 8.x

Cause

• The Infoblox IPAM plug-in for Automation supports the Infoblox host record.

Resolution

Workaround:

It is possible to add the following custom property to the VM which has an "IPv4 Reservation" record in Infoblox:

• Infoblox.IPAM.createFixedAddress: true

This overrides the default behavior which sees only Infoblox "host" records as corresponding to VMs.

 

More information can be seen on this docs page:

• Using Infoblox-specific properties and extensible attributes for IPAM integrations in VMware Aria Automation cloud templates