[
https://issues.apache.org/jira/browse/CLOUDSTACK-9808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968593#comment-15968593
]
ASF GitHub Bot commented on CLOUDSTACK-9808:
--------------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/2023
> 4.9->4.10 upgrade does not upgrade global settings to point to new template
> ---------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9808
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9808
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Upgrade
> Affects Versions: 4.10.0.0
> Reporter: Boris Stoyanov
> Assignee: Kishan Kavala
> Priority: Blocker
>
> Following the same source of information
> (http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.10/upgrade/upgrade-4.9.html)
> I’ve registered the template with the right naming: "systemvm-kvm-4.10”,
> waited until it was in Ready status.
> Then upgraded management and the cloudstack-agent on all hosts.
> Upon starting the management, the DB upgrade was successful. I’ve logged in
> the system and observed that it was still using 4.6.0 ssvm templates. The
> option to upgrade the VR wasn’t available as well. Checking global settings
> it turns out minreq.sysvmtemplate.version = 4.6.0 and router.template.kvm was
> pointing to the original ssmv template (not systemvm-kvm-4.10). The original
> ssvm template is still in active state but it should be in InActive.
> This basically leaves the user unable to upgrade ssvm (which are not working
> btw) without hacking the DB and global settings
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
