Skip to content
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

MissingParameter: The request must contain the parameter InstanceId #1905

Closed
jedi4ever opened this issue May 11, 2015 · 4 comments · Fixed by #1959
Closed

MissingParameter: The request must contain the parameter InstanceId #1905

jedi4ever opened this issue May 11, 2015 · 4 comments · Fixed by #1959
Assignees

Comments

@jedi4ever
Copy link

This occurred when I created a NAT instance of the wrong type.
fi. hvm image was not supported on t1.micro

In tfstate there was an instance with instanceId "" , so it could not continue.

@timothykimball
Copy link

I am having this problem if I Ctrl-C out of a terraform script at a certain point and then attempt to destroy:

terraform destroy
aws_instance.app: Refreshing state... (ID: )
cloudflare_record.dns: Refreshing state... (ID: 287002525)
Error refreshing state: 1 error(s) occurred:

  • 1 error(s) occurred:
  • MissingParameter: The request must contain the parameter InstanceId

If I log into AWS, I can see the instance that was created by terraform is there. Just no way to destroy it?

@mitchellh
Copy link
Contributor

Fixed in above PR.

@timothykimball That sounds really bad, but I tried a few times and couldn't get this to reproduce (unless I ctrl-C twice, which explicitly warns me data loss will occur). You can do it with a single ctrl-C?

@mitchellh mitchellh self-assigned this May 14, 2015
@timothykimball
Copy link

@mitchellh - Pleased to meet you! Great product btw. What is the best way for me to contribute?

I have attempted to reproduce and you are correct - I was hitting Ctrl-C twice (slap my hand). Apologies.

mitchellh added a commit that referenced this issue May 14, 2015
helper/schema: blank ID refresh doesn't exist [GH-1905]
@ghost
Copy link

ghost commented May 2, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators May 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants