Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 29 May 2013 00:38:20 +0000 (UTC)
From: "Alena Prokharchyk (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12649830.1369787816044.32681.1369787900632@arcas>
In-Reply-To: <JIRA.12649830.1369787816044@arcas>
References: <JIRA.12649830.1369787816044@arcas>
Subject: [jira] [Created] (CLOUDSTACK-2728) 41-42 DB upgrade: add step to
 upgrade system templates
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Alena Prokharchyk created CLOUDSTACK-2728:
---------------------------------------------

             Summary: 41-42 DB upgrade: add step to upgrade system templates
                 Key: CLOUDSTACK-2728
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2728
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
            Reporter: Alena Prokharchyk
            Priority: Blocker


This bug is a blocker for the DB upgrade testing. As the system vm got changed in CS 4.2, we have to add upgrade steps for 4.1 users. Usually the steps are:

1) While being on 4.1, upload the system template (it should be named properly)
2) During the 4.1 ->4.2 db upgrade, the script should change the vm_template_id for all the system vms, to the id of the new template
3) All the system vms have to be restarted afterwards. 

Right now step #2 is not a part of the DB upgrade script

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