IPs are Unmanaged after Deleting Host Record [ Edited ]

[#1]

My company is using InfoBlox for IPAM and DNS as a part of an automation Proof of Technology using RedHat CloudForms. I've written methods to create host records and then delete them via the API as a part of our VM provisioning/deprovisioning workflows.

When deleting the records, these IPs are then listed as "unmanaged" and are not returned as "avalible" by my REST calls. I'm wondering if there is another API call I can make to "re-manage" these IPs, or maybe an alternative way to delete the host record that opens the IP up as avalible again automatically.

I'm currently deleting the host record using the DELETE request suggested in The definitive list of REST examples.

Thanks -

LM

[#2]

Hi,

How you described that it looks like everything should work as expected by your.

You didn't provided any code/requests you made, so we can guess. Are you using nextavailableip to receive an available IP?

BR,

Vadim

[#3 · Accepted solution]

The 'Unmanaged' status is because the address still has some discovered data.
I've tried the following REST on my grid and it did clear the 'unmanaged' status of the IP :

https://mygrid.com/wapi/v2.5/network_discovery?_function=clear_discovery_data

you will have to put the following data in the POST body :

{
  "scope": "IP_ADDRESS",
  "network": "192.168.0.0/24",
  "ip_address": "192.168.0.2",
  "usage": "UNMANAGED"
}

Hope this helps,

Stefaan

[#4]

I ended up using a POST very similar to this.

I pass all those keys/values as params.

Thank you for your reply.