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

Conflicts with ec2-plugin when there are dead spot fleet instances still registered

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • ec2-fleet-plugin
    • None
    • 1.651.3 LTS
      ec2-fleet 1.0
      ec2-plugin 1.34

    Description

      I can create both spot fleet instances and spot instances from ec2-plugin.

      The issue is when a spot fleet instance had been terminated it's still logged in the system and the ec2-plugin can see it. When you delete a ec2-plugin instance it removes it from AWS but can not clean up locally as it falls over the dead ec2 fleet instance. This leaves the ec2 plugin instance still configured locally but with no matching record in AWS so it will cause Jenkins to crash when it tries to start up, also you end up will lots of slave nodes listed.

      I will try to capture stack traces next time it breaks and include them, priority was to get Jenkins back up.

      Attachments

        Activity

          jpd4nt John-Paul Drawneek created issue -
          rtyler R. Tyler Croy made changes -
          Field Original Value New Value
          Workflow JNJira [ 172936 ] JNJira + In-Review [ 184837 ]
          markl_lagendijk Mark Lagendijk made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          markl_lagendijk Mark Lagendijk made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

          People

            cyberax Aleksei Besogonov
            jpd4nt John-Paul Drawneek
            Votes:
            4 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: