-
Improvement
-
Resolution: Fixed
-
Major
-
Jenkins 1.525, Amazon EC2 plugin v1.19-unreleased (last commit: #1e009adfa3)
From the help message in EC2Cloud configuration, I need to let spot instance notify the Jenkins master that this slave is available.
As my AMI is based on CentOS, I cannot take the script directly as it mentioned. So I have gone through the script and here is my understanding on the callback process.
Jenkins master does the spot-instance request also with a default parameter in instance userdata, like:
JENKINS_URL=http://1.1.1.1:8080/&SLAVE_NAME=XXXXXXX&USER_DATA=
Then the callback script will first download the "slave.jar" and use it to notify Jenkins Master that this slave is alive:
java -jar slave.jar -jnlpUrl http://1.1.1.1:8080/XXXXXXX/slave-agent.jnlp
However, due to my Jenkins master deployed internally with no public access, Jenkins master will keep considering this slave not ready.
I also try to run these commands on an internal machine and wish Master could let it go. But only get the "403 forbidden" response.
Could you please help me on this issue?
I feel this deployment is also quite common then.
Thanks
Henry
[JENKINS-19059] [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access)
Henry Huang
created issue -
Henry Huang
made changes -
| Description |
Original:
From help message in EC2Cloud Configuration, I need to let spot instance notify Jenkins master know this slave alive after it is available. As My AMI is based on CentOS, I cannot take the script it mentioned. Here is my understanding on the callback process. Jenkins Master does the spot instance request also with a default parameter in instance userdata, like: JENKINS_URL=http://1.1.1.1:8080/&SLAVE_NAME=XXXXXXX&USER_DATA= Then the callback script will first download the "slave.jar" and use it to notify Jenkins Master know this slave alive: java -jar slave.jar -jnlpUrl http://1.1.1.1:8080/XXXXXXX/slave-agent.jnlp However, due to my Jenkins master deployed internally with no public access, so it makes Jenkins master considers this slave not ready. I also try to run these commands into an internal machine and wish Maser could let it go. But with 403 forbidden response. Could you please help me on this issue? I feel this deployment is also quite common. Thanks Henry |
New:
From the help message in EC2Cloud configuration, I need to let spot instance notify the Jenkins master that this slave is available. As my AMI is based on CentOS, I cannot take the script directly as it mentioned. So I have gone through the script and here is my understanding on the callback process. Jenkins master does the spot-instance request also with a default parameter in instance userdata, like: JENKINS_URL=http://1.1.1.1:8080/&SLAVE_NAME=XXXXXXX&USER_DATA= Then the callback script will first download the "slave.jar" and use it to notify Jenkins Master that this slave is alive: java -jar slave.jar -jnlpUrl http://1.1.1.1:8080/XXXXXXX/slave-agent.jnlp However, due to my Jenkins master deployed internally with no public access, Jenkins master will keep considering this slave not ready. I also try to run these commands on an internal machine and wish Master could let it go. But only get the "403 forbidden" response. Could you please help me on this issue? I feel this deployment is also quite common then. Thanks Henry |
Francis Upton
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Francis Upton
made changes -
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JNJira [ 150506 ] | New: JNJira + In-Review [ 206848 ] |
