Bug #804
The Image Manager tries to move non-existent files
| Status: | Closed | Start date: | 09/12/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 3.0 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: |
Description
When a VM is created, it tries to acquire the Image for each Disk.
If an Image can't be used (for instance it is persistent and already used), then the VM will release all the Images, even the ones that were not acquired.
This causes the image manager to move non-existent files, so the image ends in error state.
A related bug is that the Image Manager tries to move files to the repository when a VM in pending state is deleted.
Associated revisions
Bug #804: Better image release rollback when a VM can't be created
Bug #804: Better image release rollback when a VM can't be created
(cherry picked from commit 91d554b3aa9d78008ecc4399c673325fa58a2309)
Bug #804:removed unneeded return
Bug #804:removed unneeded return
(cherry picked from commit 2fc3d7fbb4a49d89c088125435789d6cb962252f)
Bug #804: Fix core unit tests
Bug #804: Fix core unit tests
(cherry picked from commit 32421690f3acefb5a8e0e758a5b8460dbbd9a3b0)
History
#1
Updated by Carlos Martín almost 10 years ago
- Status changed from New to Closed
- Resolution set to fixed