cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9808) 4.9->4.10 upgrade does not upgrade global settings to point to new template
Date Thu, 30 Mar 2017 13:12:41 GMT


ASF GitHub Bot commented on CLOUDSTACK-9808:

Github user DaanHoogland commented on the issue:
    @karuturi I think it is easiest to just reapply and not search for the cause of an 8 month
old PR resulting in conflicts. (if the original code has the right URLS in it)

> 4.9->4.10 upgrade does not upgrade global settings to point to new template
> ---------------------------------------------------------------------------
>                 Key: CLOUDSTACK-9808
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade
>    Affects Versions:
>            Reporter: Boris Stoyanov
>            Assignee: Kishan Kavala
>            Priority: Blocker
> Following the same source of information (
> 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

View raw message