-
Notifications
You must be signed in to change notification settings - Fork 65
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
[BUG] - invalid plan when attempting to deploy bare metal-- can only do vpc #377
Comments
@Sophrinix What's the plan you're using? It's possible there's something funky on the platform. |
i have used several plan options. but i want vbm-24c-256gb-amd |
I was able to provision that plan in the region # update region code as relevant
curl "https://api.vultr.com/v2/plans-metal" -X GET --silent | jq '.plans_metal | map(select(.locations[] | contains("ewr"))) | .[] | .id'
"vbm-6c-32gb"
"vbm-24c-256gb-amd"
"vbm-8c-132gb-v2"
""
|
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# vultr_bare_metal_server.bm1 will be created
+ resource "vultr_bare_metal_server" "bm1" {
+ app_id = (known after apply)
+ cpu_count = (known after apply)
+ date_created = (known after apply)
+ default_password = (sensitive value)
+ disk = (known after apply)
+ gateway_v4 = (known after apply)
+ id = (known after apply)
+ image_id = (known after apply)
+ label = "tf-plan-test"
+ mac_address = (known after apply)
+ main_ip = (known after apply)
+ netmask_v4 = (known after apply)
+ os = (known after apply)
+ os_id = 1946
+ plan = "vbm-24c-256gb-amd"
+ ram = (known after apply)
+ region = "ewr"
+ reserved_ipv4 = (known after apply)
+ status = (known after apply)
+ tags = [
+ "tf",
]
+ user_data = (known after apply)
+ v6_main_ip = (known after apply)
+ v6_network = (known after apply)
+ v6_network_size = (known after apply)
}
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
vultr_bare_metal_server.bm1: Creating...
vultr_bare_metal_server.bm1: Still creating... [10s elapsed]
vultr_bare_metal_server.bm1: Still creating... [20s elapsed]
vultr_bare_metal_server.bm1: Still creating... [30s elapsed]
vultr_bare_metal_server.bm1: Still creating... [40s elapsed]
vultr_bare_metal_server.bm1: Still creating... [50s elapsed]
vultr_bare_metal_server.bm1: Still creating... [1m0s elapsed]
...
vultr_bare_metal_server.bm1: Still creating... [9m50s elapsed]
vultr_bare_metal_server.bm1: Still creating... [10m0s elapsed]
vultr_bare_metal_server.bm1: Still creating... [10m10s elapsed]
vultr_bare_metal_server.bm1: Still creating... [10m20s elapsed]
vultr_bare_metal_server.bm1: Still creating... [10m30s elapsed]
vultr_bare_metal_server.bm1: Still creating... [10m40s elapsed]
vultr_bare_metal_server.bm1: Still creating... [10m50s elapsed]
vultr_bare_metal_server.bm1: Still creating... [11m0s elapsed]
vultr_bare_metal_server.bm1: Creation complete after 11m10s [id=daa1264b-7ac2-4d24-8a8c-6154a4f51143]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
|
When I attempt to deploy a bare metal instance I get the following error
I have verified with
that I am in fact selecting a valid plan.
What i think is happening is somewhere in this provider code ,
is being used rather than both
/v2/plans
and/v2/plans-metal
if that is the case, where in the code is it calling
/plans
?The text was updated successfully, but these errors were encountered: