Feature #11981

Delete the Vagrant VM used for an ISO build once it is finished

Added by intrigeri 2016-11-21 14:57:54 . Updated 2017-05-23 09:05:00 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Build system
Target version:
Tails_3.0~rc1
Start date:
2016-11-21
Due date:
% Done:

100%

Feature Branch:
wip/11972-use-vagrant-in-jenkins
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:
289

Description

Given Feature #11980, this is needed to avoid wasting lots of disk space.

Subtasks

Related issues

Blocked by Tails - Feature #11980: Create and provision a new Vagrant VM for every ISO build Resolved 2016-11-21

History

#1 Updated by intrigeri 2016-11-21 14:58:06

  • blocked by Feature #11980: Create and provision a new Vagrant VM for every ISO build added

#2 Updated by anonym 2017-03-15 02:27:54

  • Status changed from Confirmed to In Progress
  • Assignee set to bertagaz
  • Target version set to Tails_2.12
  • % Done changed from 0 to 50
  • Feature Branch set to wip/feature/11980-per-branch-vagrant-build-vm

#3 Updated by anonym 2017-03-15 13:04:40

  • QA Check set to Ready for QA
  • Feature Branch changed from wip/feature/11980-per-branch-vagrant-build-vm to feature/11980-static-build-env

#4 Updated by intrigeri 2017-04-20 07:15:54

  • Priority changed from Normal to Elevated
  • Target version changed from Tails_2.12 to Tails_3.0~rc1

(The plan is to complete this early in the 3.0 cycle, so it doesn’t get in the way of 3.0~rc1 and 3.0 final.)

#5 Updated by bertagaz 2017-04-29 10:12:30

  • Assignee changed from bertagaz to anonym
  • QA Check changed from Ready for QA to Info Needed

I’ve made some test of this feature (which was merged into wip/11972-use-vagrant-in-jenkins), and it seems that it’s not working as I thought.

I’ve set up our vagrant isobuilder in Jenkins to use the forcecleanup option, and added rake basebox:clean_all (the last one just to test, as we can’t use the basebox:clean_old way yet). It appears that in the libvirt default storage there still is a disk image for the basebox:

bertagaz@isobuilder1:~$ sudo virsh vol-list default
 Name                 Path                                    
------------------------------------------------------------------------------     
 tails-builder-amd64-jessie-2017042704-feature-11980_vagrant_box_image_0.img \
 /var/lib/libvirt/images/tails-builder-amd64-jessie-2017042704-feature-11980_vagrant_box_image_0.img

Same on my local isobuilder.

Was it intended?

#6 Updated by bertagaz 2017-04-29 10:13:00

  • Feature Branch changed from feature/11980-static-build-env to wip/11972-use-vagrant-in-jenkins

#7 Updated by anonym 2017-05-03 16:36:15

  • Assignee changed from anonym to bertagaz
  • QA Check deleted (Info Needed)

bertagaz wrote:
> It appears that in the libvirt default storage there still is a disk image for the basebox:

Ah, tha was an oversight on my part! Should be fixed with commit:3e574431b5d2fe154f81ef1f304e04a438e211b4.

#8 Updated by bertagaz 2017-05-04 14:58:05

  • % Done changed from 50 to 100
  • QA Check set to Pass

anonym wrote:
> Ah, tha was an oversight on my part! Should be fixed with commit:3e574431b5d2fe154f81ef1f304e04a438e211b4.

Indeed works better. Well done!

#9 Updated by bertagaz 2017-05-09 13:57:58

  • Status changed from In Progress to Fix committed

Applied in changeset commit:79b7f9ca5f09584bcaa4d948bff56ca2d9ffa30a.

#10 Updated by bertagaz 2017-05-10 10:05:38

  • Assignee deleted (bertagaz)

#11 Updated by intrigeri 2017-05-23 09:05:00

  • Status changed from Fix committed to Resolved