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 0B1D6FBCD for ; Mon, 29 Apr 2013 10:04:17 +0000 (UTC) Received: (qmail 62179 invoked by uid 500); 29 Apr 2013 10:04:16 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 62147 invoked by uid 500); 29 Apr 2013 10:04:16 -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 62139 invoked by uid 500); 29 Apr 2013 10:04:16 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 62136 invoked by uid 99); 29 Apr 2013 10:04:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Apr 2013 10:04:16 +0000 Date: Mon, 29 Apr 2013 10:04:15 +0000 (UTC) From: "Nicolas Lamirault (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present 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-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Lamirault updated CLOUDSTACK-2207: ------------------------------------------ Fix Version/s: 4.1.0 Affects Version/s: 4.1.0 > Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present > ---------------------------------------------------------------- > > Key: CLOUDSTACK-2207 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2207 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Affects Versions: 4.1.0 > Reporter: Nicolas Lamirault > Fix For: 4.1.0 > > > We're trying to upgrade from 2.2.14 to 4.1.0. > DatabaseUpgradeChecker failed : > 2013-04-26 12:11:45,205 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup > com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm template not found. Cannot upgrade system Vms > at com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713) > at com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82) > at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258) > at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379) > at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91) > at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > According to the documentation, there is no VMware SystemVm 3.0.0 to install. -- 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