-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
AWS - Terraform plan with directory services causes panic / crash with segmentation violation code=0x1 addr=0x18 pc=0x40e2395 #17168
Comments
terraform-provider-aws/aws/data_source_aws_directory_service_directory.go Lines 184 to 190 in ad52710
|
Observation: Please let me know your thoughts. I am getting used to Terraform debugging, so there might be some noob faults in the above. Sorry for that. |
I am having a similar issue while using the data source for the setup was tried with below configurations -
CRASH LOG
|
It looks like these are shared directories which do not yet have full support (not excusing the crash though). |
This functionality has been released in v3.46.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
This issue was originally opened by @screwnet as hashicorp/terraform#27538. It was migrated here as a result of the provider split. The original body of the issue is below.
Terraform Version
Terraform Configuration Files
main.tf
Debug Output
Crash Output
Expected Behavior
The code should have executed without crashing during terraform plan operation
Actual Behavior
When:
is executed, the code causes Terraform to crash with panic.
Steps to Reproduce
Copy the terraform code above to a test file and run following commands in the same directory:
Additional Context
Any invalid values in the resource properties were inserted as a part of cleaning logs.
The AD directory is shared from a different AWS account (via VPC peering and handshake) and was not created in this account. The executed users had admin privileges on DS, EC2 services in the destination account where the code was run.
All routing, security group and peering is working fine as well as aws cli:
References
The text was updated successfully, but these errors were encountered: