[mk-sbuild] does not cleanup the incomplete chroot if it fails
Bug #429215 reported by
Marko Poutiainen
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntu-dev-tools (Ubuntu) |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: ubuntu-dev-tools
If mk-sbuild-lv fails to finish, it will leave behind residue that requires manual cleaning before the command can be rerun. This can happen if e.g. the network is down.
There are two things that are not removed:
- The logical volume is created but not removed and
- The entry in /etc/schroot/
If the script is run again without removing these first, the script will fail with an error.
| summary: |
- mk-sbuild-lv does not do a clean exit after error + [mk-sbuild-lv] does not do a clean exit after error |
| Changed in ubuntu-dev-tools (Ubuntu): | |
| importance: | Undecided → Low |
Revision history for this message
| Stefano Rivera (stefanor) wrote Re: [mk-sbuild-lv] does not do a clean exit after error | #1 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in ubuntu-dev-tools (Ubuntu): | |
| status: | New → Confirmed |
| summary: |
- [mk-sbuild-lv] does not do a clean exit after error + [mk-sbuild] does not cleanup the incomplete chroot if it fails |
Revision history for this message
| Dan Streetman (ddstreet) wrote | #3 |
| Changed in ubuntu-dev-tools (Ubuntu): | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
The schroot.conf bit I've fixed by fixing LP: #736808 (which lets it overwrite the chroot's configuration instead of repeating it), but I'm not about to tackle cleanup after failures.