cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharat Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-568) Source template id is recorded incorrectly.
Date Fri, 30 Nov 2012 05:19:58 GMT
Bharat Kumar created CLOUDSTACK-568:
---------------------------------------

             Summary: Source template id is recorded incorrectly.
                 Key: CLOUDSTACK-568
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-568
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: ISO, Template, Volumes
    Affects Versions: pre-4.0.0
         Environment: Operating System: All
Platform: PC 
            Reporter: Bharat Kumar
             Fix For: 4.0.1


In the database, there appears to be three templates that have their parents (source_template_id)
set to the VMWare tools or XenServer tools ISOs instead of the ISO actually used to install
the VM the template was generated from:

mysql> select id, name, format, source_template_id from vm_template where source_template_id
in (200,201);
+-----+----------------------------------+--------+--------------------+
| id | name | format | source_template_id |
+-----+----------------------------------+--------+--------------------+
| 271 | Windows 2008 Ent. R2 64bit (XEN) | VHD | 200 |
| 272 | W2k8 R2 Ent 64 bit vSphere | OVA | 201 |
| 273 | W2K8 R2 Ent. 64bit | OVA | 201 |
+-----+----------------------------------+--------+--------------------+
3 rows in set (0.00 sec)

According to Kelven, this could happen if you launch a VM from an ISO, then later attach the
tools ISOs before taking a snapshot and creating the template.

The source_template_id is often used to determine billing information by upstream systems
(such as CloudPortal), so this can cause incorrect billing.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message