Pierre-Luc Dion created CLOUDSTACK-7365:
-------------------------------------------

             Summary: Upgrading without proper systemvm template corrupt 
cloudstack management server
                 Key: CLOUDSTACK-7365
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7365
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.3.0, 4.4.1
            Reporter: Pierre-Luc Dion


Since 4.3.0, also affecting 4.4.0 and 4.4.1. When upgrading CloudStack 
management server, it is required to have systemvm template properly named 
prior to the upgrade. otherwise the management server will fail to restart with 
after upgrading database schema.

The possible repair method is to revert packages to previously installed 
CloudStack and restore the database which have been upgraded.

This is not a viable upgrade path since management servers packages could be 
accidentally upgraded after a  "yum upgrade" or "apt-get update".

Upgrading CloudStack management-server without previously uploading systemvm 
template should not fail to start the management-server. if the systemvm 
template is not in place, then the management-server cannot start.





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

Reply via email to