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

Plan Counting Possible Error #2590

Closed
stack72 opened this issue Jul 1, 2015 · 9 comments
Closed

Plan Counting Possible Error #2590

stack72 opened this issue Jul 1, 2015 · 9 comments
Assignees

Comments

@stack72
Copy link
Contributor

stack72 commented Jul 1, 2015

I just upgraded to terraform 0.6.0

When running:

terraform plan -refresh=true -input=false

I got the following output

Note: You didn't specify an "-out" parameter to save this plan, so when
"apply" is called, Terraform can't guarantee this is what will execute.

~ aws_autoscaling_group.kibana_autoscale_group
    health_check_type: "EC2" => "ELB"

~ aws_instance.dash_instance
    source_dest_check: "" => "1"

~ aws_instance.docker_registry
    source_dest_check: "" => "1"

~ aws_instance.jenkins_master_instance
    source_dest_check: "" => "1"

~ aws_instance.jenkins_slave_instance
    source_dest_check: "" => "1"

~ aws_instance.mumui_instance
    source_dest_check: "" => "1"


Plan: 0 to add, 131 to change, 0 to destroy.

131 doesn't seem right since the list only has 6 changes in it

@phinze
Copy link
Contributor

phinze commented Jul 1, 2015

cc @radeksimko sounds like we need to revisit the plan counting

@mitchellh
Copy link
Contributor

Ah, I noticed this too actually and forgot to open a bug prior to release. For my anecdote: it also seemed to be the "to change" line for me as well.

@radeksimko
Copy link
Member

I have spotted the same problem - I can confirm it's happening, although not in all cases. I remember seeing this in non-trivial stacks w/ terraform_remote_state.

@pikeas
Copy link
Contributor

pikeas commented Jul 1, 2015

Sorry about the dupe! See the linked issue for a simpler repro - adding a tag to an aws_instance results in terraform plan counting all my resources under to change.

@radeksimko
Copy link
Member

@pikeas It would help if you could share a relevant part of your TF code & tfstate (minus any secrets), but if you can't, that's 👌 , I think we can find a way how to reproduce it.

@jedineeper
Copy link
Contributor

Have seen this on my Atlas account as well :(

@radeksimko
Copy link
Member

Fix in #2620

@radeksimko
Copy link
Member

Fixed via #2620

@ghost
Copy link

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

No branches or pull requests

6 participants