[
https://issues.apache.org/jira/browse/CLOUDSTACK-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734586#comment-13734586
]
Harikrishna Patnala edited comment on CLOUDSTACK-4205 at 8/9/13 9:26 AM:
-------------------------------------------------------------------------
Hi, this is happening because it is picking the old system template for
deployment. We should mark the old template as removed. My patch is in review
board that 'll fix the issue.
was (Author: harikrishna.patnala):
Hi, this is happening because it is picking the old system template for
deployment. We should mark the old template as removed. My patch is review
board that 'll fix the issue.
> [Upgrade] [KVM]System VMs are not booting up with new templates after Upgrade
> from 3.0.6 to 4.2.
> ------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4205
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4205
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, SystemVM, Upgrade
> Affects Versions: 4.2.0
> Environment: upgrade from 3.0.6 to 4.2
> Reporter: manasaveloori
> Assignee: Harikrishna Patnala
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: agent.log, management-server.log, mysqldumpAfterUp.dmp,
> mysqldumpBeforeUp.dmp
>
>
> Steps:
> 1. Have CS with 3.0.6 patch E build and KVM host.
> 2. Register the 4.2 templates before upgrade.
> 3. Upgrade to 4.2.
> Observation:
> Observed that the system VMs are not coming up.
> Attaching the MS logs ,agent logs and Db dumps before and after
--
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
