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

ec2 Plugin is launching more and more ec2 in aws on a single jenkins job trigger, but the ec2 is not connecting in jenkins as slave(jenkins says its offline)

XMLWordPrintable

      when I am triggering a build in jenkins:
      15:05:43 [Pipeline] Start of Pipeline
      15:05:44 [Pipeline] node
      15:05:59 Still waiting to schedule task
      15:05:59 'EC2 (Builder) - UPC Jenkins Builder (i-08781b66e7cb6a3ea)' is offline
      15:09:35 Aborted by Rahul, Rahul (ELS-BLR)

      it doesn't connect to the ec2 in aws, but it keeps on spinning up more and more ec2 in aws, but the agent doesn't connect in jenkins.

      I did a jenkins version upgrade yesterday from from 2.330 to Jenkins 2.332.4 and all jobs was working fine till yesterday after change, But today suddently , issue started happen, no clue about it, when I check logs in jenkins. still no clue, I have no idea what to add, as all configuration in manage jenkins --manage cloud looks good as well.
      **************************************************

      {DeleteOnTermination: true,Iops: 3000,SnapshotId: snap-055ad30dc663cff2f,VolumeSize: 10,VolumeType: gp3,Throughput: 125,Encrypted: false}

      Mar 24, 2023 9:39:09 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
      SlaveTemplate

      {description='UPC Jenkins Builder', labels='builder'}. EBS default encryption value set to: Based on AMI (null)
      Mar 24, 2023 9:39:09 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
      SlaveTemplate{description='UPC Jenkins Builder', labels='builder'}

      . Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.Terminate
      Mar 24, 2023 9:39:09 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
      SlaveTemplate

      {description='UPC Jenkins Builder', labels='builder'}. Looking for existing instances with describe-instance: {Filters: [{Name: image-id,Values: [ami-0179a2407f1cd33e8]}, {Name: instance-type,Values: [t3.large]}, {Name: key-name,Values: [upc-jenkins]}, {Name: tenancy,Values: [default]}, {Name: subnet-id,Values: [subnet-0618829c82bc8a86f]}, {Name: instance.group-id,Values: [sg-0465c8e5a1fd79a1f]}, {Name: tag:jenkins_slave_type,Values: [demand_UPC Jenkins Builder]}, {Name: tag:Name,Values: [upc.Test-bkp.jenkins.slave]}, {Name: tag:jenkins_server_url,Values: [https://jenkins-bkp.dev.privacy.elsevier.com/]}],InstanceIds: [],}
      Mar 24, 2023 9:39:09 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
      SlaveTemplate{description='UPC Jenkins Builder', labels='builder'}

      . checkInstance: i-008bf73b496496540.. false - found existing corresponding Jenkins agent: i-008bf73b496496540
      Mar 24, 2023 9:39:09 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
      SlaveTemplate

      {description='UPC Jenkins Builder', labels='builder'}. checkInstance: i-0f4704a6d6b90fcb3.. false - found existing corresponding Jenkins agent: i-0f4704a6d6b90fcb3
      Mar 24, 2023 9:39:09 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
      SlaveTemplate{description='UPC Jenkins Builder', labels='builder'}

      . checkInstance: i-0070c131a3feb873e.. false - found existing corresponding Jenkins agent: i-0070c131a3feb873e
      Mar 24, 2023 9:39:09 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
      SlaveTemplate

      {description='UPC Jenkins Builder', labels='builder'}. checkInstance: i-08781b66e7cb6a3ea.. false - found existing corresponding Jenkins agent: i-08781b66e7cb6a3ea
      Mar 24, 2023 9:39:09 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
      SlaveTemplate{description='UPC Jenkins Builder', labels='builder'}

      . checkInstance: i-0a53edc7cfef72475.. false - found existing corresponding Jenkins agent: i-0a53edc7cfef72475_
      **************************************************

          [JENKINS-70863] ec2 Plugin is launching more and more ec2 in aws on a single jenkins job trigger, but the ec2 is not connecting in jenkins as slave(jenkins says its offline)

          rahulkamboj21rahulkamboj21 Kamboj added a comment -

          thoulen could you please help on this on an urgent basis or if you could please arrange a call on rahulkamboj21.11@gmail.com

          rahulkamboj21rahulkamboj21 Kamboj added a comment - thoulen could you please help on this on an urgent basis or if you could please arrange a call on rahulkamboj21.11@gmail.com

          Mark Waite added a comment - - edited

          rahulkamboj21 the Jenkins issue tracker is used to track bugs and enhancements. It is not used as a place for user support.

          If you can describe the bug in a way that others can duplicate it with the current version of Jenkins (2.387.1 LTS or 2.396 weekly) and the current versions of the plugins you're using, you're more likely to receive help from others.

          You've not provided enough information for others to duplicate the problem. That decreases the chances that others will be willing to help you or interested to help you. The types of details you need to provide are included in "How to report an issue". In this case, you did not include the list of plugins installed or their versions. Without that information, others cannot guide you if the issue you're seeing is something that is already fixed or if it is a known issue.

          You're using an older version of Jenkins. Jenkins 2.387.1 is the current version of Jenkins. You're more likely to persuade others to help you when you have confirmed that the problem is also visible on the current version of Jenkins.

          As a simple way of saying it, your issue report is an attempt to persuade others to give you some of their time to help with your problem. People are more likely to be persuaded to give you some of their time when you provide the information they would need in order to help you. People are more likely to be persuaded to give you some of their time when you show that you've studied the problem and explored alternatives.

          Mark Waite added a comment - - edited rahulkamboj21 the Jenkins issue tracker is used to track bugs and enhancements. It is not used as a place for user support. If you can describe the bug in a way that others can duplicate it with the current version of Jenkins (2.387.1 LTS or 2.396 weekly) and the current versions of the plugins you're using, you're more likely to receive help from others. You've not provided enough information for others to duplicate the problem. That decreases the chances that others will be willing to help you or interested to help you. The types of details you need to provide are included in "How to report an issue" . In this case, you did not include the list of plugins installed or their versions. Without that information, others cannot guide you if the issue you're seeing is something that is already fixed or if it is a known issue. You're using an older version of Jenkins. Jenkins 2.387.1 is the current version of Jenkins. You're more likely to persuade others to help you when you have confirmed that the problem is also visible on the current version of Jenkins. As a simple way of saying it, your issue report is an attempt to persuade others to give you some of their time to help with your problem. People are more likely to be persuaded to give you some of their time when you provide the information they would need in order to help you. People are more likely to be persuaded to give you some of their time when you show that you've studied the problem and explored alternatives.

            thoulen FABRIZIO MANFREDI
            rahulkamboj21 rahulkamboj21rahulkamboj21 Kamboj
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: