Bug #4895

onedb fsck breaks with volatile disks

Added by Javi Fontan about 4 years ago. Updated about 4 years ago.

Status:ClosedStart date:11/03/2016
Priority:NormalDue date:
Assignee:Javi Fontan% Done:

0%

Category:CLI
Target version:Release 5.2.1
Resolution:fixed Pull request:
Affected Versions:OpenNebula 5.2

Description

This piece of code expects all disks to have an IMAGE value (fsck.rb):

    # Returns a Nokogiri::XML::Node describing an image
    # Params:
    # +disk+:: Nokogiri::XML::Node describing a disk used by a template
    def get_image_from_name(disk)
      name = disk.at_xpath("IMAGE").content # always defined
      uid = disk.at_xpath("IMAGE_UID")
      uname = disk.at_xpath("IMAGE_UNAME")

Related issues

Duplicated by Bug #4884: onedb fsck crash following migration from 4.14.1 to 5.2.0 Closed 10/27/2016

Associated revisions

Revision 4c555b0d
Added by Javi Fontan about 4 years ago

B #4895: onedb fsck breaks with volatile disks

Revision db337d8e
Added by Javi Fontan about 4 years ago

B #4895: onedb fsck breaks with volatile disks

(cherry picked from commit 4c555b0d165a7bc2c69e089d0481e095e4223311)

History

#1 Updated by Javi Fontan about 4 years ago

  • Status changed from Pending to Closed
  • Resolution set to fixed

#2 Updated by Tino Vázquez about 4 years ago

  • Target version changed from Release 5.4 to Release 5.2.1

#3 Updated by Javi Fontan over 3 years ago

  • Duplicated by Bug #4884: onedb fsck crash following migration from 4.14.1 to 5.2.0 added

Also available in: Atom PDF