preexisting build directories cause builds to fail
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| launchpad-buildd |
Triaged
|
High
|
Unassigned | ||
Bug Description
Symptoms
========
When a build is started, if the build directory we're going to use already exists, lp-buildd throws it hands in the air and says 'Fault <8002>'.
Analysis
========
A buildd shutdown via SIGTERM won't delete the in-progress build directory, nor will one restarted via an ASR. The build path is hard coded (vs e.g. unique-per-build) and so a build interrupted in either of these fashions will lead to this situation.
Solutions
=========
* The build directory could be rm -rf'd on machine startup
* lp-buildd could rm-rf just-in-time
* Either of the above two things, but move to a unique name and call for sysadmin review (to allow analysis incase an attack caused the ASR - keep the evidence).
* A unique build path could be used always (with something gc'ing uncleaned builds periodically)
It is not clear which is the most appropriate solution - probably wants GSA discussion.
| affects: | soyuz → launchpad-buildd |
| description: | updated |
| Changed in launchpad-buildd: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| summary: |
- soyuz should just deal with a preexisting build directory on build start + preexisting build directories cause builds to fail |
| description: | updated |
| description: | updated |
| description: | updated |
