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

Resource exists in state file, but still wants to be created on apply! #3498

Closed
joelmoss opened this issue Oct 14, 2015 · 3 comments
Closed

Comments

@joelmoss
Copy link
Contributor

So this has only just started hapenning with no terraform changes...

Running plan always shows some resources that will be created on apply. Yet checking the state file I see that all such resources already exist.

When running apply, I get a warning like this...

[WARN] A duplicate Security Group rule was found. This may be
a side effect of a now-fixed Terraform issue causing two security groups with
identical attributes but different source_security_group_ids to overwrite each
other in the state. See https://github.com/hashicorp/terraform/pull/2376 for more
information and instructions for recovery. Error message: the specified rule "peer: sg-0848b96e, TCP, from port: 19100, to port: 19100, ALLOW" already exists

The issue referenced above has no relation at all to this, because the resources already exist. I evene created them with Terraform.

So I'm really stumped. Is this a bug?

@joelmoss
Copy link
Contributor Author

Also, not sure if it is the same issue as #2584. If I remove the real resources from AWS and apply with terraform, I no longer get the warning (as expected). And it says all was successful. But checking the statefile for those new resources, and they still do not exist, but they have been created successfully.

@joelmoss
Copy link
Contributor Author

Duplicate of #2584

@ghost
Copy link

ghost commented Apr 30, 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 Apr 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant