Bug #4728

Template boot order is not converted during upgrade to 5.0

Added by EOLE Team over 4 years ago. Updated over 4 years ago.

Status:ClosedStart date:08/19/2016
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

0%

Category:Core & System
Target version:Release 5.2
Resolution:fixed Pull request:
Affected Versions:OpenNebula 5.0

Description

Hello, follow up of my forum post.

I just upgrade our production 4.14 OpenNebula to 5.0.2 following the documentation.

I just have an issue with already existing templates:

Thu Aug 18 16:33:30 2016 [Z0][ReM][E]: Req:8464 UID:5 TemplateInstantiate result FAILURE [TemplateInstantiate] Error allocating a new virtual machine template. Wrong OS/BOOT value: "hd" should be a comma-separated list of disk# or nic#

I thought this would be managed by the onedb upgrade.

I made a onedb patch file to fix most of the cases, I only skip templates when the image referenced by a DISK is not found, so I can't check the index disk0, disk1, ...

Here is the log of the patch command:

  • Skipping some template because of missing image:
    Skipping template 1380 Install CDROM 40Go (i386): No image named 'eole-2.4.1-rc2-i386.iso' for uid '9'
    Skipping template 1381 Install CDROM 40Go (amd64): No image named 'eole-2.4.1-rc2-amd64.iso' for uid '9'
    
  • Updating a template after skipping an nonexistant boot device type:
    Warning template 13219 coreos-amd64: skip nonexistent boot device 'cdrom'
    Template 13219 coreos-amd64: 'hd,cdrom' -> 'disk0'
    
  • Updating a template without any problem, note that the first boot device CDROM is the second DISK:
    Template 2349 Run Any: 'CDROM,hd' -> 'disk1,disk0'
    

The Warning and Skipping messages are not conditionned on ops[:verbose], it may even requires a dedicated logger for admin to follow what's happening.

Regards.

5.0_boot_devices.rb Magnifier (6.15 KB) EOLE Team, 08/19/2016 02:33 PM

Associated revisions

Revision f4383616
Added by Carlos Martín over 4 years ago

Bug #4728: Integrate Daniel Dehennin's contribution in onedb fsck

Revision f632b939
Added by Carlos Martín over 4 years ago

Bug #4728: Integrate Daniel Dehennin's contribution in onedb fsck

(cherry picked from commit f438361689e12671f795989a9dceedc2268c3f4e)

History

#1 Updated by Carlos Martín over 4 years ago

  • Category set to Core & System
  • Status changed from Pending to New
  • Target version set to Release 5.2

Thanks for your excellent contribution, we'll integrate this in the next release

#2 Updated by EOLE Team over 4 years ago

Thanks,

Comments line 70-72 are not correct:

  • Template is skipped only if the image referenced by a DISK is not found
  • Boot device in BOOT is skipped if no DISK reference this kind of device

Regards.

#3 Updated by Carlos Martín over 4 years ago

  • Status changed from New to Closed
  • Assignee set to Carlos Martín
  • Resolution set to fixed

This is now integrated in the fsck command, thank you.

Also available in: Atom PDF