Bug #464
VMs created on opennebula_2.0-1 fails to restart under opennebula_2.0.1-1
| Status: | Closed | Start date: | 01/11/2011 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Ruben S. Montero |
% Done: | 0% |
|
| Category: | OpenNebula Core | |||
| Target version: | - | |||
| Resolution: | fixed | Affected Version: | OpenNebula 2.2 | |
| Story points | - | |||
| Velocity based estimate | - |
Description
Beetwen the release 2.0-1 and 2.0.1-1 of opennebula was inserted the Mandatory template attribute OS/ARCH, or under the version 2.0-1 it was not made mandatory.
By onevm restart the scheduler tries to generate a new deployment file for the VM, but will not find the XML attribute ARCH under vm_pool.template and set the VM as Failed, with all the typical headaches:
The Disks will be deleted and the data on the VM is lost.
The only possible workaround I found was to get throught the vm_pool.template and UPDATE it by hand.
It is thinks like this opennebula, it is thinks like this!!
History
Updated by Ruben S. Montero over 1 year ago
- Target version deleted (
Release 1.2.1)
Updated by Ruben S. Montero about 1 month ago
- Status changed from New to Closed
- Resolution set to fixed
- Affected Version set to OpenNebula 2.2
I think most of this is covered by the upgrade tool. Closing this one