Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
The eucalyptus cloud we are using initially reports the IP address of the instance as 0.0.0.0. This persists for a while after the instance is running before DHCP kicks in. Hudson tries to connect and launch the slave immediately after the instance is reported as running and thus tries to connect to 0.0.0.0 and fails.
It would be nice if Hudson could wait until the instance has a valid IP address before trying to connect.
Code changed in jenkins
User: bitter
Path:
src/main/java/hudson/plugins/ec2/ssh/EC2UnixLauncher.java
http://jenkins-ci.org/commit/core/dc1c19568ce58d469ba06665d2d46912ab003e0e
Log:
[FIXED JENKINS-5851] Since 0.0.0.0 may answer a shh connection we need to explicitly check against that address
Compare: https://github.com/jenkinsci/ec2-plugin/compare/c03c91a...dc1c195