[
https://issues.apache.org/jira/browse/CLOUDSTACK-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek updated CLOUDSTACK-5208:
-------------------------------------------
Assignee: Harikrishna Patnala (was: Kelven Yang)
> 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
> Assignee: Harikrishna Patnala
> 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.4#6159)
