You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2014/07/21 23:42:39 UTC

[jira] [Resolved] (CLOUDSTACK-7140) Upgrade 4.2.1 -> 4.4.0rc2

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alena Prokharchyk resolved CLOUDSTACK-7140.
-------------------------------------------

    Resolution: Invalid

Closing the bug as invalid. 

The first attempt to upgrade failed because the new system template wasn't pre-downloaded prior to upgrade (the requirement reflected in Release notes, for the cases when template is changed between CS versions)

What should have been done to fix the problem:

* manually roll back your DB to the pre-upgraded version. Currently CS doesn't support automatic rollback in case of failure
* while being on prev version, download the template
* start management server 

If you attempt to start MS for the second time when the first start failed due to upgrade problem, w/o rolling back, the MS will try to run upgrade one more time on the partially upgraded DB. And it will fail.

Please follow the steps above to fix the problem on your system.


> Upgrade 4.2.1 -> 4.4.0rc2
> -------------------------
>
>                 Key: CLOUDSTACK-7140
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7140
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade
>    Affects Versions: 4.4.0
>         Environment: CloudStack 4.2.1 on CentOS 6.5
>            Reporter: Pierre-Luc Dion
>            Priority: Critical
>         Attachments: 4.2.1-to-4.3_management-server.log, catalina.out, management-server.log
>
>
> Upgrading CloudStack management 4.2.1 to 4.4.0rc2 fail to upgrade database.



--
This message was sent by Atlassian JIRA
(v6.2#6252)