Bug #3212
Recover poweroff state after positive monitoring
| Status: | Closed | Start date: | 09/29/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 4.10 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.8 |
Description
If a VM ends up in the Poweroff state due to a monitor error, the core should be able to recover it on the next successful monitorization.
Associated revisions
bug #3212: Update monitor state reporting from KVM, Xen, ESX and vCenter drivers
bug #3212: STATE='d' moves the VM to POWEROFF instead of SUSPENDED
bug #3212: Move VMs to poweroff if the were running last time we got monitor data from the host. Move VMs to running if they are recovered. Remove unused code for vmware_driver
bug #3212: Only move VMs to poweroff it they have been successfully monitored at least once.
bug #3212: Update monitor state reporting from KVM, Xen, ESX and vCenter drivers
bug #3212: STATE='d' moves the VM to POWEROFF instead of SUSPENDED
bug #3212: Move VMs to poweroff if the were running last time we got monitor data from the host. Move VMs to running if they are recovered. Remove unused code for vmware_driver
bug #3212: Only move VMs to poweroff it they have been successfully monitored at least once.
History
#1
Updated by Ruben S. Montero almost 7 years ago
- Assignee set to Ruben S. Montero
#2
Updated by Ruben S. Montero over 6 years ago
- Status changed from Pending to Closed
- Resolution set to fixed