Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
After updating the plugin I can no longer provision EC2 machines.
It connects with success but it fails with
"Could not find /init.sh"
I've fixed by reverting to previous version.
Attachments
Issue Links
- is duplicated by
-
JENKINS-26559 EC2 slaves not connecting
-
- Resolved
-
Activity
Field | Original Value | New Value |
---|---|---|
Description |
After updating the plugin I can no longer provision EC2 machines. It connects with success but it fails with "Could not find /init.sh" I've fixed by reverting to previous version. |
Priority | Blocker [ 1 ] | Major [ 3 ] |
Summary | Weird "Could not find /init.sh" after update | Slave does not start if the temp dir is not set to anything after upgrade to 1.25 |
Link |
This issue is duplicated by |
Status | Open [ 1 ] | In Progress [ 3 ] |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Workflow | JNJira [ 160601 ] | JNJira + In-Review [ 208360 ] |