Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7829910476 for ; Fri, 26 Jul 2013 12:12:03 +0000 (UTC) Received: (qmail 38472 invoked by uid 500); 26 Jul 2013 12:12:03 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 38233 invoked by uid 500); 26 Jul 2013 12:12:02 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 38111 invoked by uid 500); 26 Jul 2013 12:12:02 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 37959 invoked by uid 99); 26 Jul 2013 12:12:02 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Jul 2013 12:12:02 +0000 Date: Fri, 26 Jul 2013 12:12:01 +0000 (UTC) From: "Donal Lafferty (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-3723) System VM Template for XenServer has wrong guest OS type Information on the Database MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-3723: --------------------------------------- Component/s: Upgrade > System VM Template for XenServer has wrong guest OS type Information on the Database > ------------------------------------------------------------------------------------ > > Key: CLOUDSTACK-3723 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3723 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Upgrade > Affects Versions: 4.2.0 > Reporter: Chandan Purushothama > Assignee: Sanjay Tripathi > Priority: Critical > Fix For: 4.2.0 > > > Observe that the guest_os id of the System VM Template for XenServer is 133 > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type from vm_template where id=1 \G > *************************** 1. row *************************** > id: 1 > name: SystemVM Template (XenServer) > type: SYSTEM > format: VHD > display_text: SystemVM Template (XenServer) > guest_os_id: 133 > hypervisor_type: XenServer > 1 row in set (0.00 sec) > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type from vm_template where id=8 \G > *************************** 1. row *************************** > id: 8 > name: SystemVM Template (vSphere) > type: SYSTEM > format: OVA > display_text: SystemVM Template (vSphere) > guest_os_id: 15 > hypervisor_type: VMware > 1 row in set (0.00 sec) > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type from vm_template where id=3 \G > *************************** 1. row *************************** > id: 3 > name: SystemVM Template (KVM) > type: SYSTEM > format: QCOW2 > display_text: SystemVM Template (KVM) > guest_os_id: 15 > hypervisor_type: KVM > 1 row in set (0.00 sec) > mysql> > mysql> select * from guest_os where id=133; > +-----+-------------+------+--------------------------------------+----------------------------+ > | id | category_id | name | uuid | display_name | > +-----+-------------+------+--------------------------------------+----------------------------+ > | 133 | 2 | NULL | 0099b9c8-f320-11e2-b49d-06cba2000705 | Debian GNU/Linux 6(64-bit) | > +-----+-------------+------+--------------------------------------+----------------------------+ > 1 row in set (0.00 sec) > The System VM deployed from the XenServer System VM Template is not a 64 bit machine. > The above correction is crucial for Upgrades -- 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