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/EC2Computer.java
src/main/java/hudson/plugins/ec2/ssh/EC2UnixLauncher.java
http://jenkins-ci.org/commit/core/ba86f6d538e5c8d14f24211d1c2874758119353e
Log:
JENKINS-5851Refresh ec2 dns name for every turn in the ssh connection loop.