Error launching source instance: The parameter groupName cannot be used with the parameter subnet (InvalidParameterCombination)

[mumbley]

I have been running through you get started guide (and on the 5th time of trying I have been cutting/pasting the examples) and have consistently received the same message on changing the ami - as follows

 steve@BasementCat:terraform->  terraform apply
aws_instance.example: Refreshing state... (ID: i-a084358a)
aws_instance.example: Destroying...
aws_instance.example: Destruction complete
aws_instance.example: Modifying...
  ami: "ami-408c7f28" => "ami-aa7ab6c2"
aws_instance.example: Error: Error launching source instance: The parameter groupName cannot be used with the parameter subnet (InvalidParameterCombination)
Error applying plan:

1 error(s) occurred:

* Error launching source instance: The parameter groupName cannot be used with the parameter subnet (InvalidParameterCombination)

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

The "example.tf" file, currently, looks like this: -

provider "aws" {
    access_key = "XXXXXXXXXXXXXXXXXXXXXXXX"
    secret_key = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
    region = "us-east-1"
}

resource "aws_instance" "example" {
    ami = "ami-aa7ab6c2"
    instance_type = "t1.micro"
}

I have seen this raised previously and closed but there obviously seems to be a problem somewhere.

Thanks

[mumbley]

...it is also worth mentioning that, if having received the error, I re-run "terraform apply" the change is applied. It looks as if it got as far as terminating the old instance but not creating the new one (as the error above occurred). so, running the apply again just seems to treat it as a new build.

[mitchellh]

This doesn't crash anymore but, it also doesn't work. I've reproduced it. Working on a fix now.

[mitchellh]

Fixed. It was a set of commits that fixes this:

faa4e75
c9a541d
9d239ee

[mumbley]

Great thanks. Love this project BTW.

On Wed, Aug 27, 2014 at 11:47 PM, Mitchell Hashimoto <
[email protected]> wrote:

Closed #196 #196.

—
Reply to this email directly or view it on GitHub
#196 (comment).