Bug #2502
deleting image in locked state leaves current operation in progress and files not cleaned
| Status: | New | Start date: | 11/27/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | - | |||
| Resolution: | Pull request: | |||
| Affected Versions: | OpenNebula 4.4 |
Description
We can delete image in locked state, when some operation, for e.g. clone is still in progress.
The results - operation is still running and destination file left in datastore.
Solutions:
1) don't allow delete image in locked state - dangerious if image is stuck in locked state.
2) cancel datastore operation and after do cleanup.
What would be if long running image operation is interrupted by reboot or crash ?
Related issues
History
#1
Updated by Ruben S. Montero over 7 years ago
- Status changed from Pending to New
#2
Updated by Ruben S. Montero about 7 years ago
- Related to Bug #2998: Deleting an image deletes the record from the database even if the delete fails added