Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-5851

Wait until launched virtual machine gets IP address before connecting

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • ec2-plugin
    • 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.

      Attachments

        Activity

          larsko larsko created issue -

          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-5851 Refresh ec2 dns name for every turn in the ssh connection loop.

          scm_issue_link SCM/JIRA link daemon added a comment - 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-5851 Refresh ec2 dns name for every turn in the ssh connection loop.

          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

          scm_issue_link SCM/JIRA link daemon added a comment - 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
          scm_issue_link SCM/JIRA link daemon made changes -
          Field Original Value New Value
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 135943 ] JNJira + In-Review [ 187075 ]

          People

            kohsuke Kohsuke Kawaguchi
            larsko larsko
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: