Bug #464

VMs created on opennebula_2.0-1 fails to restart under opennebula_2.0.1-1

Added by Marlon Nerling about 9 years ago. Updated about 8 years ago.

Status:ClosedStart date:01/11/2011
Priority:HighDue date:
Assignee:Ruben S. Montero% Done:

0%

Category:Core & System
Target version:-
Resolution:fixed Pull request:
Affected Versions:OpenNebula 2.2

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!!

Associated revisions

Revision 107ee183
Added by Juan Jose Montiel Cano over 2 years ago

F #5204 Show Simple restricted attribute (#464)

Revision 27bde4a6
Added by Juan Jose Montiel Cano over 2 years ago

F #5204 Show Simple restricted attribute (#464)

(cherry picked from commit 107ee18380023feb58542fda427e06a2ecfd22bd)

History

#1 Updated by Ruben S. Montero about 9 years ago

  • Target version deleted (Release 1.2.1)

#2 Updated by Ruben S. Montero about 8 years ago

  • Status changed from New to Closed
  • Resolution set to fixed
  • Affected Versions OpenNebula 2.2 added

I think most of this is covered by the upgrade tool. Closing this one

Also available in: Atom PDF