UTAH

Temporary files are not removed

Bug #1088377 reported by Jean-Baptiste Lallement
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
UTAH
Fix Released
Medium
Javier Collado

Bug Description

UTAH doesn't clean temporary files which results in an important waste of disk space and causes system issues:

# du -sch /tmp/utah*|tail -1
106G total

Related branches

lp:~javier.collado/utah/bug1101186
Andy Doan (community): Approve
Max Brustkern (community): Approve
Javier Collado (community): Needs Resubmitting
Diff: 894 lines (+364/-145)
16 files modified
debian/changelog (+1/-0)
debian/control (+1/-1)
docs/source/reference.rst (+9/-0)
examples/run_install_test.py (+5/-1)
examples/run_test_bamboo_feeder.py (+5/-1)
examples/run_test_cobbler.py (+5/-1)
examples/run_test_vm.py (+5/-1)
examples/run_utah_tests.py (+3/-0)
utah/cleanup.py (+210/-0)
utah/process.py (+56/-11)
utah/provisioning/baremetal/bamboofeeder.py (+6/-5)
utah/provisioning/baremetal/cobbler.py (+11/-10)
utah/provisioning/baremetal/power.py (+3/-2)
utah/provisioning/provisioning.py (+39/-109)
utah/provisioning/vm/vm.py (+3/-3)
utah/url.py (+2/-0)
Gema Gomez (gema)
Changed in utah:
importance: Undecided → Medium
Revision history for this message
Javier Collado (javier.collado) wrote :

What would be the desired cleanup strategy?

This is a problem that happens when running lots of tests in the same machine
that shouldn't be addressed in the utah binary itself in my opinion.

Would a script that is executed as a jenkins job that removes temporary files
older than some threshold be a good solution? What would be a good value for
that threshold (hours, days, ...)?

Changed in utah:
status: New → Incomplete
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

UTAH must remove any temporary file/directory it creates and adding a job to do the cleaning would just be a workaround.

Revision history for this message
Javier Collado (javier.collado) wrote :

Some of the files there can be useful to troubleshoot problems, but I agree on
that it's not really needed to always have them. Alternatively, we could just
add a command line flag to keep those files when we really need them when
troubleshooting a problem. Would that be ok for you?

Revision history for this message
Max Brustkern (nuclearbob) wrote :

I think the solution for this will be related to https://bugs.launchpad.net/utah/+bug/1081280 since they're both part of the cleanup process.

Revision history for this message
Javier Collado (javier.collado) wrote :

This is related to bug1101186 as well.

Revision history for this message
Javier Collado (javier.collado) wrote :

This shouldn't be a problem anymore after the enhancements to the cleanup
module in the linked branch. Please reopen if that's not the case.

Changed in utah:
assignee: nobody → Javier Collado (javier.collado)
status: Incomplete → Fix Committed
status: Fix Committed → Fix Released
Revision history for this message
Javier Collado (javier.collado) wrote :

Fixed in lp:utah (rev. 846)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.