add configurable workspace cleanup to Jenkins scripts
Bug #1702186 reported by
Tim Kuhlman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mojo: Continuous Delivery for Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
I recently discovered that our CI server was running out of disk space. On investigation in "/srv/mojo/
The primary problem is there are so many lxc images on disk, this may be related to how the Jenkins job scripts are performing or it may relate to the secondary issue of the odd lxc image in an lxc image path problem.
Changed in mojo: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in codetree: | |
status: | New → Triaged |
importance: | Undecided → Medium |
importance: | Medium → Undecided |
no longer affects: | codetree |
Changed in mojo: | |
status: | Triaged → New |
importance: | Medium → Undecided |
summary: |
- Mojo has lxc image embedded in another lxc image + add configurable workspace cleanup to Jenkins scripts |
Changed in mojo: | |
importance: | Undecided → Low |
To post a comment you must log in.
As far as I can tell this is pretty much how LXCs and workspaces are set up in Mojo. The only difference from my local LXC-enabled projects is ROOTFS being a directory (on my machine it's a symlink back to /var/lib/ lxc/mojo- foo.xenial/ rootfs) but this may be something to do with how we create containers in CI and our desire to not store them in /var/lib/lxc. I'm not seeing from this description where the second LXC image comes into the picture.
I think our space problems are simply that we have too many Mojo workspaces and we never delete them. For example software- center- agent has 31 workspaces weighing in at 1.1G each even though we've only retained the last 6 runs in Jenkins.