Bug #1594

Wrong source file path for contextualization iso

Added by Giovanni Toraldo almost 8 years ago. Updated almost 8 years ago.

Status:ClosedStart date:10/26/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Core & System
Target version:Release 3.8.1
Resolution:fixed Pull request:
Affected Versions:OpenNebula 3.8

Description

With a template like this:

NAME = base-lamp
MEMORY = 512
CPU = 0.5

DISK = [IMAGE_ID = "12"]
NIC  = [NETWORK="default"]

GRAPHICS = [ 
  TYPE    = "vnc",
  LISTEN  = "0.0.0.0" ]

CONTEXT = [
  hostname   = "$NAME",
  ip_public      = "$NIC[IP, NETWORK=\"default\"]",
  netmask_public = "$NETWORK[NETMASK, NETWORK=\"default\"]",
  gateway_public = "$NETWORK[GATEWAY, NETWORK=\"default\"]",
  dns_public     = "$NETWORK[DNS, NETWORK=\"default\"]",
  files = "/srv/cloud/scripts/debian/10networking.sh /srv/cloud/scripts/debian/VMwareTools-8.6.0-425873.tar.gz" ]

The generated deployment.0 contains a an erroneous path to the ISO path (should be disk.1.iso):

<domain type='vmware'>
        <name>one-49</name>
        <memory>524288</memory>
        <os>
                <type arch='i686'>hvm</type>
        </os>
        <devices>
                <disk type='file' device='disk'>
                        <source file='[0] 49/disk.0/disk.vmdk'/>
                        <target dev='hda'/>
                </disk>
                <disk type='file' device='cdrom'>
                        <source file='[0] 49/disk.0.iso'/>
                        <target dev='hdb'/>
                        <readonly/>
                </disk>
                <interface type='bridge'>
                        <source bridge='VM Network'/>
                        <mac address='02:00:c0:a8:02:da'/>
                </interface>
                <graphics type='vnc' listen='0.0.0.0' port='5949'/>
        </devices>
</domain>

History

#1 Updated by Giovanni Toraldo almost 8 years ago

Seems fixed in bc61fa78, right?

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

  • Status changed from New to Closed
  • Target version set to Release 3.8.1
  • Resolution set to fixed

Yes Giovanni, this is now fixed. This is important enough to plan a maintenance. We are aiming at today (Oct. 26th) EOB, or Monday (29th) at the latest

THANK YOU!

Also available in: Atom PDF