Skip to content
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

remote-exec inline doesn't proceed to next command #5775

Closed
varuns-zetaris opened this issue Mar 22, 2016 · 4 comments
Closed

remote-exec inline doesn't proceed to next command #5775

varuns-zetaris opened this issue Mar 22, 2016 · 4 comments

Comments

@varuns-zetaris
Copy link

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.

@rklyne
Copy link

rklyne commented Mar 22, 2016

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.

Reproducable with this config:
terraform.tf.zip

@jen20
Copy link
Contributor

jen20 commented Mar 22, 2016

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!

@rklyne
Copy link

rklyne commented Mar 22, 2016

@jen20 You're on fire!
Thank you very much

@ghost
Copy link

ghost commented Apr 27, 2020

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 ghost locked and limited conversation to collaborators Apr 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants