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

Experimental feature failure #9934

Closed
levinse opened this issue Nov 7, 2016 · 8 comments
Closed

Experimental feature failure #9934

levinse opened this issue Nov 7, 2016 · 8 comments

Comments

@levinse
Copy link

levinse commented Nov 7, 2016

Experimental feature failure! Please report a bug.

This is not an error. Your Terraform operation completed successfully.
Your real infrastructure is unaffected by this message.

While running, Terraform sometimes tests experimental features in the
background. These features cannot affect real state and never touch
real infrastructure. If the features work properly, you see nothing.
If the features fail, this message appears.

The following failures happened while running experimental features.
Please report a Terraform bug so that future Terraform versions that
enable these features can be improved!

You can report an issue at: https://github.com/hashicorp/terraform/issues

1 error(s) occurred:

  • apply operation: Real and shadow states do not match! Real state:

(I can provide the full / sensitive output if needed but this keeps happening)

@jdblack
Copy link

jdblack commented Nov 7, 2016

I got this in 0.7.9 as well:

  • apply operation: Real and shadow states do not match! Real state:

data.template_file.logging-host:
ID = 9a3171e19560fc375ae46c76ff67ccc0307cd61339fc7ad71a32200007d76a1b
rendered = s-s1
template = ${env_s}-${shard_s}
vars.% = 2
vars.env_s = s
vars.shard_s = s1
vault_secret.docker_auth:
ID = path:secret/core/docker/auth
data.% = 1
data.value = [SECRET_VALUE_HERE]
path = /secret/core/docker/auth

.....
Shadow state:

%!s(PANIC=runtime error: invalid memory address or nil pointer dereference)

@mitchellh
Copy link
Contributor

Hey @jdblack or @levinse, thanks for reporting an issue! I'm fairly confident that this will be the same as #9905, but can't be 100% sure w/o a full output. Let me know.

@jdblack
Copy link

jdblack commented Nov 9, 2016

I also think its a duplicate.

Unfortunately our output is over 7,000 lines long and contains sensitive
data.

I did include the full shadow output, which I believe just listed a NPE

We unfortunately have sensitive data in our hashicorp output. I did

On Nov 8, 2016 12:59 PM, "Mitchell Hashimoto" [email protected]
wrote:

Hey @jdblack https://github.com/jdblack or @levinse
https://github.com/levinse, thanks for reporting an issue! I'm fairly
confident that this will be the same as #9905
#9905, but can't be 100%
sure w/o a full output. Let me know.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#9934 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDuLbIOcXPPbhAoJK8XgbLUTuCjlN_Pks5q8OLJgaJpZM4Krwc5
.

@mitchellh
Copy link
Contributor

@jdblack I'll have 0.7.10 released tomorrow morning, check with that and you may be good to go. Contains a good number of fixes in this category.

@sriney-boc
Copy link

sriney-boc commented Nov 14, 2016

I get the same error with 0.7.10.

You can report an issue at: https://github.com/hashicorp/terraform/issues

1 error(s) occurred:

  • plan operation: Real and shadow states do not match! Real state:

and then all of our infrastructure info.

@mitchellh
Copy link
Contributor

Unfortunately I cannot diagnose the error without knowing what doesn't match. If that error showed up then the states do not match.

@sriney-boc
Copy link

It's only showing when I run with a target

plan -target=module....

@ghost
Copy link

ghost commented Apr 20, 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 20, 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

5 participants