cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "shweta agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-5208) upgrade from 3.0.6 to 4.3 is not throwing any exception if new System VM template is not registered with proper name
Date Wed, 20 Nov 2013 06:37:21 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827381#comment-13827381
] 

shweta agarwal commented on CLOUDSTACK-5208:
--------------------------------------------

with the fix of this bug 
https://issues.apache.org/jira/browse/CLOUDSTACK-4585

Commit ae231444bc885ee5e9a5d4bb3003bef651c849d6 in branch refs/heads/master from Kelven Yang
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ae23144 ]

CLOUDSTACK-4585: make run-time datastore folder migration, VM snapshot, bug in root disk controller
type carried from previous version work under upgrade situation


that part of code is commented which throws exception on not finding system vm template



> upgrade from 3.0.6 to 4.3 is not throwing any exception if new System VM template is
not registered with proper name
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5208
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5208
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade
>    Affects Versions: 4.3.0
>         Environment: upgrade from 3.0.6 to 4.3
>            Reporter: shweta agarwal
>            Priority: Blocker
>             Fix For: 4.3.0
>
>         Attachments: cloud-after-upgrade.dmp, cloud306.dmp, management-server.log.2013-11-19.tar.gz
>
>
> Created a 3.0.6 setup
> Registered new system vm templates with name systemvm-xenserver-4.3  instead of 4.2
> performed  upgrade 
> and restarted Ms
> Bug:
> Didn't hit any exception /error of  new system template not found
> And after than even start/stop system vm is restarting system vm with old template .
Destroying and recreating system vm is also recreating system vm with old templates 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message