action #6770
closed
worker does not recover from early qemu fail
Added by lnussel about 9 years ago.
Updated about 9 years ago.
Category:
Regressions/Crashes
Description
the worker dies if qemu quits early, e.g. due to wrong parameters. qemu.pid is left then and the worker can't be started anymore unless manually deleting qemu.pid
actually we should remove this qemu.pid check and just cleanup the pool. Since we made the qemu shutdown safer I never had a case where qemu really was running still
- Target version set to Sprint 15
- Status changed from New to Resolved
- Assignee set to coolo
- Status changed from Resolved to New
- Assignee changed from coolo to lnussel
- Target version changed from Sprint 15 to Sprint 16
since I deployed it we had 3 cases, so I reverted the removal - but added more time for the qemu killing.
So we should still not allow the worker to continue if there is a qemu.pid. But we can check if the qemu.pid is real or just a file.
- Status changed from New to In Progress
- % Done changed from 0 to 90
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
Also available in: Atom
PDF