[JIRA] [ec2-plugin] (JENKINS-33443) Init script fails to create ~/.hudson-run-init on completion and runs multiple times

[mihelich@google.com (JIRA)]

Patrick Mihelich created an issue

Jenkins / JENKINS-33443 Init script fails to create ~/.hudson-run-init on completion and runs multiple times Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 10/Mar/16 1:01 AM Environment: Jenkins 1.625.3 Amazon EC2 plugin 1.31 Master and slaves running Ubuntu 14.04 Priority: Minor Reporter: Patrick Mihelich I noticed my Unix slaves on EC2 do not have a ~/.hudson-run-init file, despite running the init script (and following setup steps) successfully. As a result, when they're brought back up from a stopped state, they run the init script again, wasting ~20 minutes. Some relevant AMI configuration: Remote FS root: /home/ubuntu Remote user: ubuntu AMI Type: unix Root command prefix: sudo Init script is essentially: sudo $HOME/init_script.sh On a successfully connected slave, I expect to see /home/ubuntu/.hudson-run-init, but there's no such file. I took a quick look at EC2UnixLauncher.java, and everything looks reasonable. My only question is why touch ~/.hudson-run-init would need to be run as root. But both touch ~/.hudson-run-init and sudo touch ~/.hudson-run-init produce the expected file when run manually as the ubuntu user. So I'm a bit stumped. I'm testing out touching the file myself in the init script as a workaround. Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[perrin@opencloud.com (JIRA)]

Perrin Morrow commented on JENKINS-33443

Re: Init script fails to create ~/.hudson-run-init on completion and runs multiple times We've been seeing this behaviour too, but not consistently. Some of the time the file is created, and I can't see any obvious pattern. I am currently running a patched version of the plugin in our staging environment, with extra logging around the creation of the file to see why it might be failing. But so far it has created the file every time. It's possible my call to waitCompletion(sess); which I added to get the exit status may have caused it to work more reliably. I'll do some more testing next week.

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[perrin@opencloud.com (JIRA)]

Perrin Morrow commented on JENKINS-33443

Re: Init script fails to create ~/.hudson-run-init on completion and runs multiple times

Well "more testing next week" turned into two years, sorry about that. I've pushed the code we've been running with for those two years in this pull request.

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[raihaan.shouhell@autodesk.com (JIRA)]

Raihaan Shouhell resolved as Fixed

PR has been merged if this is still an issue please reopen this with a new version of the plugin

Jenkins / JENKINS-33443

Init script fails to create ~/.hudson-run-init on completion and runs multiple times

Change By: Raihaan Shouhell Status: Open Resolved Resolution: Fixed

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)