cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9807) 4.5->4.10 upgrade fails. db upgrade script looking for ssvm template-4.6 when having 4.10 already installed.
Date Wed, 08 Mar 2017 10:42:38 GMT

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

ASF subversion and git services commented on CLOUDSTACK-9807:
-------------------------------------------------------------

Commit 1ed7e3d6b07f65b37978729ccae10be34dde9774 in cloudstack's branch refs/heads/master from
[~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1ed7e3d ]

Bug-ID: CLOUDSTACK-9807: 4.10.0.0 systemvm template upgrade.

Removed systemvm template upgrade code on 4.6 upgrade. Added 4.10 system
vm template upgrade changes with new urls and md5sum


> 4.5->4.10 upgrade fails. db upgrade script looking for ssvm template-4.6 when having
4.10 already installed.
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9807
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9807
>             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 upgrade instructions from this page: http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.10/upgrade/upgrade-4.5.html
> I’ve registered the template with the right naming: "systemvm-kvm-4.10”, waited until
it was in Ready status.
> Then following the upgrade procedure, upgraded the management and the cs-agent. 
> Upon starting the management the db.upgrade kicked in, but it failed with the following
error: 
> com.cloud.utils.exception.CloudRuntimeException: 4.6.0KVM SystemVm template not found.
Cannot upgrade system Vms
> It appears that the upgrade script is still looking for 4.6 ssvm template while a newer
version is installed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message