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 have a terraform deployment which fires up a cluster in ec2 run a job using remote-exec . However the hadoop job get executed but after the 2nd command , terraform doesn't go further. It doesn't proceed to the 3rd command . And terraform create doesn't complete. Am i missing anything. If the time taken by job is less it works . But if its long running jobs like 1-2 hrs it fails.
The text was updated successfully, but these errors were encountered:
I'm seeing this too when provisioning postgres on a CentOS DigitalOcean droplet.
It turns out that a 'sleep 1' command is enough to make it break.
New on v0.6.13 for me. I'm rolling back to v0.6.12 temporarily.
Hi @varuns-zetaris and @rklyne! We release 0.6.14 yesterday afternoon (US time) which should address this - the PR was #5751. I'll close this issue for now, but if you see a recurrence of it with 0.6.14 please feel free to reopen. Thanks for reporting!
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 27, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
provisioner "remote-exec" {
inline = [
"aws s3 cp ${var.jar_path} ./",
"hadoop jar ",
"aws s3 cp job_* ${var.log_path}"
]
}
I have a terraform deployment which fires up a cluster in ec2 run a job using remote-exec . However the hadoop job get executed but after the 2nd command , terraform doesn't go further. It doesn't proceed to the 3rd command . And terraform create doesn't complete. Am i missing anything. If the time taken by job is less it works . But if its long running jobs like 1-2 hrs it fails.
The text was updated successfully, but these errors were encountered: