Bug #1557
A failed restart from unknown should end in unk. again, not failed
| Status: | Closed | Start date: | 10/16/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 3.8 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 3.6 |
Associated revisions
Bug #1557: Add new VM LCM state in core, BOOT_UNKNOWN. A failed boot returns the VM to UNKNOWN
Bug #1557: Add BOOT_UNKNOWN state to xsd and dot documentation files
Bug #1557: Add BOOT_UNKNOWN state to CLI, and OCA (both Ruby & Java)
Bug #1557: Add BOOT_UNKNOWN state to oZones
Bug #1557: Add new VM LCM state in core, BOOT_POWEROFF. A failed boot returns the VM to POWEROFF
Bug #1557: Add BOOT_POWEROFF state to OCA (both Ruby & Java)
Bug #1557: Add BOOT_POWEROFF state to oZones
Bug #1557: Add BOOT_POWEROFF state to xsd and dot documentation files
bug #1557: Added state to sunstone. Update log messages for BOOT failures
History
#1
Updated by Carlos Martín over 8 years ago
Same thing for poweroff, a failed restart should not move the VM to failed
#2
Updated by Carlos Martín over 8 years ago
- Assignee changed from Carlos Martín to Daniel Molina
#3
Updated by Daniel Molina over 8 years ago
- Assignee changed from Daniel Molina to Ruben S. Montero
#4
Updated by Ruben S. Montero over 8 years ago
- Status changed from New to Closed
- Resolution set to fixed