Return-Path: 
 <cloudstack-dev-return-20465-apmail-incubator-cloudstack-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id E09BBD463
	for <apmail-incubator-cloudstack-dev-archive@minotaur.apache.org>;
 Mon,  4 Feb 2013 22:16:13 +0000 (UTC)
Received: (qmail 28771 invoked by uid 500); 4 Feb 2013 22:16:13 -0000
Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org
Received: (qmail 28697 invoked by uid 500); 4 Feb 2013 22:16:13 -0000
Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:cloudstack-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:cloudstack-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:cloudstack-dev@incubator.apache.org>
List-Id: <cloudstack-dev.incubator.apache.org>
Reply-To: cloudstack-dev@incubator.apache.org
Delivered-To: mailing list cloudstack-dev@incubator.apache.org
Received: (qmail 28304 invoked by uid 99); 4 Feb 2013 22:16:13 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2013 22:16:13 +0000
Date: Mon, 4 Feb 2013 22:16:13 +0000 (UTC)
From: "Tamas Monos (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <JIRA.12630765.1360016068899.241947.1360016173106@arcas>
In-Reply-To: <JIRA.12630765.1360016068899@arcas>
References: <JIRA.12630765.1360016068899@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-1151) vmware systemVm template
 upgrade is missing in 4.0 upgrade
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-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570681#comment-13570681 ] 

Tamas Monos commented on CLOUDSTACK-1151:
-----------------------------------------

Tamas,
  Looks like vmware systemVm template upgrade is missing in 4.0 upgrade. 

You can try the below work around:

1.  Add new vmware template to CS with name systemvm-vmware-4.0 2.  Wait till the template is downloaded and installed successfully 3.  Look up id of this template in DB (Name should match the input provided in step # 1)
   mysql> select id from `cloud`.`vm_template` where name = 'systemvm-vmware-4.0' and removed is null; 4. Update template type to SYSTEM
   mysql> update `cloud`.`vm_template` set type='SYSTEM' where id = <id-from-step3>; 5. Update template Id for all system Vms
   mysql> update `cloud`.`vm_instance` set vm_template_id = <id-from-step3> where type <> 'User' and hypervisor_type = 'VMware'; 6. Restart all system Vms

~kishan

                
> vmware systemVm template upgrade is missing in 4.0 upgrade
> ----------------------------------------------------------
>
>                 Key: CLOUDSTACK-1151
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1151
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Template
>    Affects Versions: 4.0.0
>         Environment: vmware esx 4.1/5.1
>            Reporter: Tamas Monos
>            Priority: Blocker
>             Fix For: 4.0.2
>
>
> I have upgraded from 3.0.2 to 4.0.0 and the management server started and updated the database just fine, however the rest of the upgrade procedure just does not work.
> I'm running the script: "nohup cloud-sysvmadm -d 192.168.1.5 -u cloud -p password -c -r > sysvm.log 2>&1 &" accordingly to my environment and see in its log it is trying to stop/start a router.
> It stops it, then recreates the same secondary datastore (vmware) and then starts the same router rather than deploying the new imported systemVM template and creating a new one.
> It neither touches the sec-storage VM nor the console-proxy VM so new management system, old systemVMs.
>  
> No errors during running the script no errors in the log:
> Stopping and starting 1 running routing vm(s)...
> Done restarting router(s).

--
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