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

Provide an option for deleting extra volumes produced by terminated ec2 instances

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • ec2-plugin
    • None

      After an ec2 instance is started by hudson and its job is finished, the instance gets terminated in cca 30 minutes. It would be nice to have an option for deleting associated volumes remaining after the instance termination – otherwise they remain as available volumes and ec2 user pays for its storage. Thanks.

          [JENKINS-9292] Provide an option for deleting extra volumes produced by terminated ec2 instances

          akostadinov added a comment -

          what volumes are left available? I don't see such.

          akostadinov added a comment - what volumes are left available? I don't see such.

          Currently having this same 'problem', EBS Volumes are detached but still stored after an Instance is terminated . It would benefit to have a option to remove all generated EBS Volumes after the termination/shutdown of its associated instance.

          Mustapha Ahmed added a comment - Currently having this same 'problem', EBS Volumes are detached but still stored after an Instance is terminated . It would benefit to have a option to remove all generated EBS Volumes after the termination/shutdown of its associated instance.

          Craig Ringer added a comment -

          Really, Jenkins should be setting the EBS "delete on terminate" flag on the instance root volume. That way this issue won't arise.

          Craig Ringer added a comment - Really, Jenkins should be setting the EBS "delete on terminate" flag on the instance root volume. That way this issue won't arise.

          Craig Ringer added a comment -

          Also note that this only occurrs if your AMIs are created from an instance that has delete on terminate turned off. If you turn delete on terminate on before creating AMIs this won't be a problem.

          That's a bit of a pain when you don't control the AMIs, though.

          I'm currently working around this by having Jenkins stop the instances rather than terminate them. This is also saving lots of setup time.

          Craig Ringer added a comment - Also note that this only occurrs if your AMIs are created from an instance that has delete on terminate turned off. If you turn delete on terminate on before creating AMIs this won't be a problem. That's a bit of a pain when you don't control the AMIs, though. I'm currently working around this by having Jenkins stop the instances rather than terminate them. This is also saving lots of setup time.

            kohsuke Kohsuke Kawaguchi
            xmsauer Max Sauer
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: