iterative / terraform-provider-iterative

☁️ Terraform plugin for machine learning workloads: spot instance recovery & auto-termination | AWS, GCP, Azure, Kubernetes
https://registry.terraform.io/providers/iterative/iterative/latest/docs
Apache License 2.0
288 stars 27 forks source link

`task` machine = "m+k80" does not work as expected? #593

Closed dacbd closed 2 years ago

dacbd commented 2 years ago

referencing: https://github.com/iterative/terraform-provider-iterative/blob/master/docs/guides/generic-machine-types.md

with:

terraform {
  required_providers { iterative = { source = "iterative/iterative" } }
}
provider "iterative" {}

resource "iterative_task" "test" {
  timeout   = 24*60*60
  disk_size = 100
  machine   = "m+k80"
  image     = "ubuntu"

  # cloud-specific config
  cloud     = "aws"

  storage {
    workdir = ""
    output  = ""
  }
  script = <<-END
    stuff
  END
}

received:

╷
│ Error: operation error Auto Scaling: CreateAutoScalingGroup, https response error StatusCode: 400, RequestID: 59df852b-a7f9-458c-b783-d2a832f69027, api error ValidationError: You must use a valid fully-formed launch template. The requested configuration is currently not supported. Please check the documentation for supported configurations.
│ 
│   with iterative_task.test,
│   on main.tf line 6, in resource "iterative_task" "test":
│    6: resource "iterative_task" "test" {
│ 
╵
╷
│ Error: failed to create
│ 
│   with iterative_task.test,
│   on main.tf line 6, in resource "iterative_task" "test":
│    6: resource "iterative_task" "test" {
│ 
╵
dacbd commented 2 years ago

🤔 image

dacbd commented 2 years ago

specific to that region, also this look familiar 😓

 Error: operation error Auto Scaling: CreateAutoScalingGroup, https response error StatusCode: 400, RequestID: e1ae26b0-a9d7-423e-a156-4839a0f7578d, api error ValidationError: You must use a valid fully-formed launch template. Your requested instance type (p2.xlarge) is not supported in your requested Availability Zone (us-west-2d). Please retry your request by not specifying an Availability Zone or choosing us-west-2a, us-west-2b, us-west-2c.