provider/aws crash when authenticating via instance profile on 0.6.2

[bosmanx]

Hi,

• I created resources on 0.6.1 (5 tf files + template)
• upgraded to 0.6.2 to use aws_s3_bucket_object
• crashed on "plan/apply" - http://pastebin.com/Wj62NHhr
• removing aws_s3_bucket_object doesn't help - http://pastebin.com/azdyRP41
• removing all resources (only provider settings left) doesn't help neither - http://pastebin.com/DFzP4J05

Looks like problem is with my tfstate - http://pastebin.com/BTaXQMxC

[phinze]

Sorry for the trouble! Let's see if we can't get this figured out.

Are you authenticating to AWS via access_key / secret_key or via another method?

[bosmanx]

I'm authenticating via instance profile. So I'm screwed anyway, as both #1595 and #2730 break instance profiles as both use iamconn.GetUser(nil):

* ValidationError: Must specify userName when calling with non-User credentials
        status code: 400, request id: [dabf17c6-3c8d-11e5-b79c-a50fb504c59a]

[phinze]

The reason I ask is it looks like a GetUser api call to test the provider config is where it failed:

2015/08/06 21:00:15 [ERROR] root: eval: *terraform.EvalConfigProvider, err: 1 error(s) occurred:

* ValidationError: Must specify userName when calling with non-User credentials
        status code: 400, request id: [22bdfc24-3c7e-11e5-a422-e51fd6279686]

[phinze]

@bosmanx sorry about this! we'll get it fixed up and cut another release as soon as we can.

[phinze]

Related: #2828

[catsby]

Hey @bosmanx , terribly sorry for the trouble here. I sent a patch in #2959 to address this, and right now I'm trying to duplicate the setup you described to confirm things work as expected. If you have the chance and ability to build Terraform from that branch, it would be awesome to help me confirm this is fixed. If not, I should know with some confidence soon.

Again, I sincerely apologize for this. We're working on patching and then cutting a new release today.

[jszwedko]

@catsby verified that this works for me, thanks for putting together this PR so quickly. Do you think it would be possible to release a patched version after this is merged? I'd really like to take advantage of some of the changes in 0.6.2, but this is blocking our ability to upgrade.

[catsby]

@jszwedko we're waiting on one more hot fix but yes, a new release should go out ASAP with this

[jszwedko]

Awesome, thank you @catsby !

[jszwedko]

Also, apologies for not responding to #2828 before 0.6.2 was cut.

[catsby]

#2959 and #2963 have been merged and will go out in the next release (targeting this coming Monday, August 10th ), so I'm going to close this now. Thanks for writing in! Sorry for the trouble

[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.