Issue Details (XML | Word | Printable)

Key: ABICLOUD-262
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Pedro Navarro Pérez
Reporter: Diego Parrilla
Votes: 0
Watchers: 0
Operations

Email this issue
Send issue summary in email
If you were logged in you would be able to see more operations.
Abiquo

When a Virtual Machine does not start properly, the Virtual Machine stays in the hypervisor endlessly

Created: 18/Oct/09 10:00 PM   Updated: 10/Dec/09 03:20 PM   Resolved: 26/Nov/09 09:21 AM
Component/s: Virtualization
Affects Version/s: abicloud-1.0.0PR, abicloud-1.0.0PR2
Fix Version/s: abicloud-1.0.0-RC2

Time Tracking:
Not Specified


 Description  « Hide
When the deployment of a virtual image with a new virtual machine fails, the virtual machine stays in the hypervisor endlessly.

This is not the correct behaviour: if the deployment of a virtual machine fails, it's a must to execute a rollback process to return the hypervisor to the state previous to the deployment of the virtual machine. So, at least, the failed virtual machine must be always deleted when failure.

Marc Morata added a comment - 22/Oct/09 11:51 AM
currently, If the deploy fails when the virtualfactory is starting the vmachine, the rollback process doesn't works.

Albert Puig added a comment - 03/Nov/09 01:06 PM
added ABICLOUD-208 as requirement, when the operation fails the cloned virtual image should disappear.

Pedro Navarro Pérez added a comment - 04/Nov/09 01:23 PM
- The hypervisor is rollecd back now when the VM powers up fails (after first deployment).

Diego Parrilla added a comment - 23/Nov/09 11:25 PM - edited
See ABICLOUDPREMIUM-51