menu_acs_logo

Upgrading CloudStack

This document contains the instructions for upgrading CloudStack from prior releases, to the current release. Please read through all sections carefully before starting.

From ACS 4.16 onwards, seeding of system-VM Template is optional, as this will be taken care of by either the upgrade process or in case of a fresh deployment, registration of the systemVM Template(s) is handled during the addition of the first image store to a zone. The cloudstack-management package will now include the systemVM Templates for KVM, XenServer and VMWare. In case Templates aren’t already registered either prior upgrade or during fresh installation, ACS will handle the Template registration automatically, by mounting the secondary store onto the management server, copying the respective Templates to the store and then creating the template.properties file.

From ACS 4.20.3 and 4.22.1 onwards, a starting Management Server that detects an upgrade is needed will abort if it also finds mshost entries for other Management Servers that are up. If as an operator starting a Management Server you get the error Database upgrade is required but the management server is running in a clustered environment. during upgrade, check if you have stopped all other Management Servers in your environment and retry. If it still fails, it might be that a Management Server has stopped un-gracefully and you need to fix the DB-entry for it. For example, make sure all Management Servers are stopped by checking the hosts in the output of select name from mshost where state <> ‘Down’ and then, when all is safe, run update mshost set state = ‘Down’

Note

For information on the API changes and issues fixed in this release, please see the Release Notes section of the documentation

Contents: