integrations
[BUG]: Cancelling terraform apply hangs indefinitely
Expected Behavior
Terraform should stop when asked.
Actual Behavior
Cancelled terraform apply hung forever until forcibly killed (SIGKILL).
Terraform Version
Terraform 1.7.4 on linux AMD64
Affected Resource(s)
All resources, I think
Terraform Configuration Files
No response
Steps to Reproduce
Just a regular terraform apply (that perhaps is taking too long) and then cancelling
Debug Output
module.clojure_service_image.github_repository_collaborators.all: Refreshing state... [id=clojure-service-image]
module.cci_synthetics.github_repository_collaborators.all: Refreshing state... [id=cci-synthetics]
module.jira_tickets_for_new_vulns.github_branch_protection.default: Refreshing state... [id=BPR_kwDOII76r84B_P4l]
Too long with no output (exceeded 10m0s): context deadline exceeded
Panic Output
No response
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Fix
An attempt at a fix is here: #2298
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCi/MYn6O2q82X++/uTezGMf+Y5ufrE5qRHd9tpW75n5QtQOSXSGlu5o3apAg/Ixct2rIgCo1a5fHLMDEquAAsZFKhEj/WSOritiPkah4nAEEeorlqZV3FXTJuWpMvanJzle5dTdeGmXigiB+8W6VZjpLXAmUvCwj6L0ULKgz63suKldCiClGDQeqpvWuuheFGrH/W/XJbD6+KIEEKVJ0zoeVBFn7uZTyCskRGoX5vts9zjEMXHIiK6TB6GYzkgtQKRn9jFiov5L6Xtl2mbI9No/eQ7lAoErSD1CYn8csPg7A5hnFLvpzIBTJd3FqHpNAr+gJ/ORdMkqTnvLrvjdzOdj+T89MlAtbuL+k6Rjt4tuepEbjJb5qiBW1c8qrYP+DPLuCuM6YoJL7Eeufeapbc3N2lCDzb7yGI+6wbD0Hzl2ATwJ24B3c4wG1r78WdfMYR8gDU7cDwBnmmLeHiLbP4XDzXAazS1FD1zr/Dnu936CxHsyaesuZOU2mTslWKD1bcn1mboUjgDAOG/y+2L9IrRMudIfqMkZsIwqtu24UKe9b7Cz2IYikEuPmzqHD83e5flB1mQG/M+ueoPvbaqKA67T/baP7eHmrL2WCIdHFYSPkVhy+dyHqUeI/P9Z1RPV3RwzEJpUs+2ZCwgmsILYRygFDKX/6oWuaFQqo/OUjH9Hw==
@kyc-theresawchavez789 do you mind sharing with us where that is supposed to be used? That might just be exactly what we need to know to fix terraform from hanging indefinitely. 🤔
@C-Collamar i made a PR I think might address this (fixes a leaked lock)
@pete-woods that's interesting. I wrote my comment as a cheeky remark just to spark activity to this dreadful issue. It's good to know you have a PR that hopefully resolves this. I just hope this gets resolved soon, thanks man.
@kfcampbell sorry for the direct @ - I just had a look for owners who were active sometimes.
This issue (and acompanying PR) have been open for a quite a while, and it would be amazing to get this bug fixed.
Are there any updates on it? Experience the same with high parallelism values
