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

Jenkins EC2 plugin often has its nodes fail to connect to the Jenkins Main

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • ec2-plugin
    • EC2 plugin 1.51
      Jenkins version 2.235.2
      Jenkins server running on m4.4xlarge EC2 instance

      There are some cases where when the EC2 plugin gets triggered to spin up a new node, the below output appears. The temp fix is to just relaunch the agent and that fixes itself, however, this always requires manual intervention. If it fails, it will keep on spinning up new nodes and constantly fail for some reason. 

      ssh -o StrictHostKeyChecking=no -i /tmp/ec2_4311748328328850426.pem ubuntu@null -p 22  java  -jar /tmp/remoting.jar -workDir /var/lib/jenkins
      ssh: Could not resolve hostname null: Temporary failure in name resolution

          [JENKINS-66141] Jenkins EC2 plugin often has its nodes fail to connect to the Jenkins Main

          Steven added a comment -

          thoulen Hi Fabio,

           

          Just wondering if you've ever seen this?

          Steven added a comment - thoulen  Hi Fabio,   Just wondering if you've ever seen this?

          Steven added a comment -

          Or if anyone in general has seen this

          Steven added a comment - Or if anyone in general has seen this

          Steven added a comment -

          Any assistance? thoulen

          Steven added a comment - Any assistance? thoulen

          Looks like it failed to get the ip of the instance

          Raihaan Shouhell added a comment - Looks like it failed to get the ip of the instance

          Steven added a comment -

          raihaan yea it did, but I'm unsure why? There's not too many SSH connections going on and the EC2 plugin generally handles all of that

          Steven added a comment - raihaan  yea it did, but I'm unsure why? There's not too many SSH connections going on and the EC2 plugin generally handles all of that

          Your instance is configured to connect via public / private ip / DNS?

          You might want to upgrade your installation. The current ec2-plugin is 1.63. And the recent Jenkins LTSes are quite far ahead

          Raihaan Shouhell added a comment - Your instance is configured to connect via public / private ip / DNS? You might want to upgrade your installation. The current ec2-plugin is 1.63. And the recent Jenkins LTSes are quite far ahead

          Steven added a comment -

          raihaan yea it happened again :/ 

          We're aware of Jenkins being a out of date and we're slowly planning to upgrade eventually but as of now, there are some independent plugins that break if we upgrade Jenkins, which is unfortunate. But yea, regarding the EC2 plugin, I'll go ahead an update it tonight to 1.58! Didn't know we were behind

          Steven added a comment - raihaan  yea it happened again :/  We're aware of Jenkins being a out of date and we're slowly planning to upgrade eventually but as of now, there are some independent plugins that break if we upgrade Jenkins, which is unfortunate. But yea, regarding the EC2 plugin, I'll go ahead an update it tonight to 1.58! Didn't know we were behind

            thoulen FABRIZIO MANFREDI
            stoiven Steven
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: