You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may not be an issue per se, it may be just with our understanding of how Infoblox/Terraform provider works. Please forgive my ignorance on this topic; I have reached out to our internal Infoblox support but that team is not sure how this works either.
In Infoblox Web UI, we can see a lot of unused IP addresses, but when the Terraform Infoblox provider makes a request for an IP allocation, we are getting this error back.
Any thoughts for what we may be doing wrong?
I believe the ip allocation block calls the next_available_ip function call but from Infoblox perspective, there's none left/available for it to give out, which makes me think next_available_ip API function does not look at the IP range in DHCP scope; can you please explain how this function works if possible?
The text was updated successfully, but these errors were encountered:
Not sure if this is considered a workaround, but we decided to create new subnets dedicated for terraform provisioning (off limits to human/engineers) and without DHCP scope.
This may not be an issue per se, it may be just with our understanding of how Infoblox/Terraform provider works. Please forgive my ignorance on this topic; I have reached out to our internal Infoblox support but that team is not sure how this works either.
In Infoblox Web UI, we can see a lot of unused IP addresses, but when the Terraform Infoblox provider makes a request for an IP allocation, we are getting this error back.
Any thoughts for what we may be doing wrong?
I believe the ip allocation block calls the next_available_ip function call but from Infoblox perspective, there's none left/available for it to give out, which makes me think next_available_ip API function does not look at the IP range in DHCP scope; can you please explain how this function works if possible?
The text was updated successfully, but these errors were encountered: