You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I added "aws_ssm_document" and "aws_ssm_association" after existing instance ressource: My hope is to be able to launch commands to update/install additional features some linux instances after their creation
2017-12-26T09:43:38.674+0100 [DEBUG] plugin.terraform.exe: local-exec-provisione
r (internal) 2017/12/26 09:43:38 [DEBUG] plugin: waiting for all plugin processe
s to complete...
Error: Error applying plan:
1 error(s) occurred:
* aws_ssm_association.gw0: 1 error(s) occurred:
* aws_ssm_associati2017-12-26T09:43:38.701+0100 [DEBUG] plugin: plugin process e
xited: path=C:\tools\terraform\infa-hub\.terraform\plugins\windows_amd64\terrafo
rm-provider-aws_v0.1.4_x4.exe
on.gw0: [ERROR] Error c2017/12/26 09:43:38 [ERR] yamux: Failed to read stream da
ta: read tcp 127.0.0.1:54622->127.0.0.1:10000: wsarecv: Une connexion existante
a dû être fermée par l'hôte distant.
reat2017/12/26 09:43:38 [ERR] yamux: Failed to write header: write tcp 127.0.0.1
:54622->127.0.0.1:10000: use of closed network connection
2017-12-26T09:43:38.704+0100 [WARN ] plugin: error closing client during Kill: e
rr="unexpected EOF"
ing2017-12-26T09:43:38.705+0100 [DEBUG] plugin: plugin process exited: path=C:\t
ools\terraform\terraform.exe
SSM association: InvalidDocument: Document schema version, 2.0, is not supporte
d by association that is created with instance id
status code: 400, request id: ddef467a-ea18-11e7-988e-75f688c18213
Expected Behavior
expect that Association is done and 'hostname' command executed on existing ec2 linux instance
Actual Behavior
Don't execute, see crash output, ssm association don't work
Steps to Reproduce
Please list the full steps required to reproduce the issue, for example:
terraform init
terraform plan
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered:
This issue has been automatically migrated to hashicorp/terraform-provider-aws#2840 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know.
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
locked and limited conversation to collaborators
Apr 5, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
v0.11.1
Terraform Configuration Files
I added "aws_ssm_document" and "aws_ssm_association" after existing instance ressource:
My hope is to be able to launch commands to update/install additional features some linux instances after their creation
Debug Output
Expected Behavior
expect that Association is done and 'hostname' command executed on existing ec2 linux instance
Actual Behavior
Don't execute, see crash output, ssm association don't work
Steps to Reproduce
Please list the full steps required to reproduce the issue, for example:
terraform init
terraform plan
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: