-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
infoblox_ip_allocation fails - doesn't know what to do with vm_name field #48
Comments
Do you have a cloud license installed? if not it will throw this error, to mitigate it add the following EA's in NIOS |
No, I don't have the cloud license installed. |
Nevermind, I added the EAs in NIOS. :) Still crashing though.
|
closing as the issue is solved and the another issue has already been raised for the crash |
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
Terraform will perform the following actions:
infoblox_ip_allocation.demo_allocation will be created
}
Plan: 1 to add, 0 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
infoblox_ip_allocation.demo_allocation: Creating...
Error: Error allocating IP from network block(10.120.0.0/13): WAPI request error: 400('400 Bad Request')
Contents:
{ "Error": "AdmConProtoError: Unknown extensible attribute: VM Name",
"code": "Client.Ibap.Proto",
"text": "Unknown extensible attribute: VM Name"
}
on instances.tf line 112, in resource "infoblox_ip_allocation" "demo_allocation":
112: resource "infoblox_ip_allocation" "demo_allocation"{
The terraform stanza that creates this error is:
resource "infoblox_ip_allocation" "demo_allocation"{
vm_name="test01.domain.com"
ip_addr = aws_instance.test01.private_ip
cidr="10.120.0.0/13"
tenant_id="domain.com"
enable_dns=true
}
The text was updated successfully, but these errors were encountered: