0.6.16 BUG with IAM Role Attribute Mismatch

[eedwardsdisco]

Terraform Version

0.6.16

Affected Resource(s)

Please list the resources as a list, for example:

• aws_iam_role
• aws_iam_instance_profile

Terraform Configuration Files

https://gist.github.com/eedwardsdisco/5706ca2000a9adb4caf739b371e7b8b9

Debug Output

https://gist.github.com/eedwardsdisco/4e84559902baf96d31dbc2a19cbca904

Panic Output

https://gist.github.com/eedwardsdisco/419cb65ae7e497130f17c59d79d177e4

Expected Behavior

terraform apply succeeds

Actual Behavior

terraform apply fails and exits on a bug

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply

Important Factoids

succeeds if I run apply again after the fact

References

[eedwardsdisco]

possibly related to #6788 ?

[eedwardsdisco]

possibly related to #6806 ?

[eedwardsdisco]

Here's a breakdown of the diff.

Seems to be an issue with the roles.X field, where the plan phase has a different role id than the apply phase?

https://gist.github.com/eedwardsdisco/0163b5de916cdf4307d9084c28a55a73

[eedwardsdisco]

I managed to get past it by changing from using a rendered template output for the name of the policy

name = "${template_file.cluster_name.rendered}-opsworks-service"

I changed the above (and all other references to this template) to instead be the value that was getting calculated in the template itself.

name = "${lower(var.cluster_name_prefix)}-${lower(var.cluster_environment_name)}-opsworks-service"

I suspect there is a problem with the plan phase and rendering template output.

e.g. sounds related to #5462 in that I've also seen the 'ERROR PARSING JSON' problem on PLAN but not on APPLY (when the JSON comes from a template output).

[mitchellh]

This should be fixed in higher versions of 0.7.x. I can't get this to reproduce and it looks like the same as your other issue!

[ghost]

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.