AWS Opsworks Stack - Unable to create Linux Chef 12 stacks

[smckim]

Similar issue to #5905
Opsworks stacks are initially created with a lot of default values, and then updated afterwards with values specified in the configuration file. Stacks are initially created with the default configuration_manager_version of Chef 11.4, which cannot be upgraded in Opsworks to Chef 12, causing terraform apply to fail.

[sharmaansh21]

https://github.com/hashicorp/terraform/blob/master/builtin/providers/aws/resource_aws_opsworks_stack.go#L65

@smckim i think here we are passing 11.4 that is causing this bug

[apparentlymart]

This is also related to #5569

[tommyorndorff]

Is there any way to work around this? I need to port over chef 12 opsworks stacks from cloudformation to terraform using amazon linux 2013.03.

[smckim]

My work around was to create the stack in the console first and then manually edit the tfstate file with the values from the stack I created (which matched the values I had in my aws_opsworks_stack resource configuration). Further updates on the stack work fine (layer creation, etc), it's just the initial creation of the stack with terraform that currently doesn't work.

[vinyar]

As a work around:
Since instances already come with chef 11.x you can add omnibus updated cookbook to your runlist and upgrade chef-client as part of the chef run
https://github.com/hw-cookbooks/omnibus_updater

[stack72]

Closed with #6244

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