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 5F0FEF1B0 for ; Tue, 6 Aug 2013 04:20:51 +0000 (UTC) Received: (qmail 48785 invoked by uid 500); 6 Aug 2013 04:20:49 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 48683 invoked by uid 500); 6 Aug 2013 04:20:49 -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 48644 invoked by uid 500); 6 Aug 2013 04:20:48 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 48634 invoked by uid 99); 6 Aug 2013 04:20:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Aug 2013 04:20:48 +0000 Date: Tue, 6 Aug 2013 04:20:47 +0000 (UTC) From: "Ram Ganesh (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-4066) [Object_store_Refactor] [VMWare]Template sync deletes the routing template entry from DB if the pre-seeded template is systemvmtemplate-4.2-vh8.ova 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-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-4066: ----------------------------------- Assignee: Sateesh Chodapuneedi > [Object_store_Refactor] [VMWare]Template sync deletes the routing template entry from DB if the pre-seeded template is systemvmtemplate-4.2-vh8.ova > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-4066 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4066 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Oracle VM (OVM), Storage Controller > Affects Versions: 4.2.0 > Environment: Latest build from ACS 4.2 branch. > Storage: NFS for both primary and secondary storage > Cluster: VMWare > Reporter: Sanjeev N > Assignee: Sateesh Chodapuneedi > Priority: Blocker > Fix For: 4.2.0 > > Attachments: cloud.dmp, management-server.rar > > > Template sync deletes the routing template entry from DB if the pre-seeded template is systemvmtemplate-4.2-vh8.ova. So VM deployment fails with error "Template 8 has not been completely downloaded to zone 1" > Steps to Reproduce: > ================ > 1.Pre-seed secondary storage with systemvmtemplate-4.2-vh8.ova > 2.Bring up CS with vmware cluster with ESX5.1 > 3.Wait for the System vms to come up > 4.Try to deploy guest vm with default cent os template > Result: > ====== > Failed to start instance VM[User|vm1-default] > com.cloud.utils.exception.CloudRuntimeException: Template 8 has not been completely downloaded to zone 1" > Observations: > ============ > For VMWare we are providing two routing templates : > systemvmtemplate-4.2-vh7.ova > systemvmtemplate-4.2-vh8.ova > vh7.ova is for 4.x and higher and vh8 is for 5.x and when these two templates were provided we were informed that vh8 has good performance compared to vh7. However templates.sql file has entry only for systemvmtemplate-4.2-vh7.ova file. > After SSVM is up Template sync deleted all the routing template entries from template_store_ref table including vmware routing template since the pre-seeded template is not the one present in vm_template table. Also vmware system template entry got deleted from template_store_ref table. > Since system template entry is not found in template_store_ref table VR deployment fails hence VM deployment. > Following is the log snippet during template sync: > ===================================== > 2013-08-04 04:39:09,204 INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-2:null) Template Sync did not find routing-1 on image store 4, may request download based on available hypervisor types > 2013-08-04 04:39:09,204 INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-2:null) Removing leftover template routing-1 entry from template store table > 2013-08-04 04:39:09,291 INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-2:null) Template Sync did not find routing-3 on image store 4, may request download based on available hypervisor types > 2013-08-04 04:39:09,292 INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-2:null) Removing leftover template routing-3 entry from template store table > 2013-08-04 04:39:09,357 INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-2:null) Template Sync did not find routing-8 on image store 4, may request download based on available hypervisor types > 2013-08-04 04:39:09,359 INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-2:null) Removing leftover template routing-8 entry from template store table > 2013-08-04 04:39:09,367 INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-2:null) Template Sync did not find routing-9 on image store 4, may request download based on available hypervisor types > 2013-08-04 04:39:09,370 INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-2:null) Removing leftover template routing-9 entry from template store table > 2013-08-04 04:39:09,380 INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-2:null) Template Sync did not find routing-10 on image store 4, may request download based on available hypervisor types > 2013-08-04 04:39:09,380 INFO [storage.image.TemplateServiceImpl] (AgentConnectTaskPool-2:null) Removing leftover template routing-10 entry from template store table > Attached management server log file and cloud DB. -- 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