cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harikrishna Patnala (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-2728) 41-42 DB upgrade: add step to upgrade system templates
Date Wed, 05 Jun 2013 11:31:20 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Harikrishna Patnala resolved CLOUDSTACK-2728.
---------------------------------------------

       Resolution: Fixed
    Fix Version/s: 4.2.0
    
> 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
>            Assignee: Harikrishna Patnala
>            Priority: Blocker
>             Fix For: 4.2.0
>
>
> 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

Mime
View raw message