JClouds leaves cloud instances behind without cleaning them up

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major
    • Component/s: jclouds-plugin
    • None
    • Environment:
      Jenkins 1.466.2, JClouds Plug-In 2.3.1, Ubuntu 12.04 x64. Connecting to Amazon EC2 trying to run an Ubuntu 12.04 image

      When failures happen during initialization, the plug-in often leaves behind unterminated instances even after all its cleanup. This could be costly

      See JENKINS-15727 for a couple different ways I've had failures. Usually it seems like the first machine it attempts to start works fine and terminates correctly. It is the second machine that it attempts to start that gets left behind.

            Assignee:
            Andrew Bayer
            Reporter:
            Nathan Sharp
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: