View Source

Prerequisites

You can upgrade from any version of Abiquo 3.0.0-GA or 3.x version to the latest Abiquo version.

Remember to stop services and check for queued jobs or conversions and perform a full backup. See Prepare to Upgrade Abiquo 3.x Versions

UI configuration

The upgrade will OVERWRITE lang_en_US.json. If you have custom labels or translations, back them up before the upgrade and add them afterwards as lang_xx_XX_custom.json
The upgrade deprecates client-config.json. Add custom configuration to client-config-custom.json after the upgrade

Perform the packages upgrade

This step must be done on all Abiquo servers, including Abiquo Management Server, Remote Services, KVM Servers and LVM Servers.

Configure Repositories

Remove previous repo packages

yum remove abiquo-release*

Install destination repo package

There is one package for each major version that installs base and update repositories. Please locate the abiquo-release-ee package of your destination version and install it with the following command. This example is for the latest Abiquo major version of 3.6.

yum localinstall http://mirror.abiquo.com/abiquo/3.6/os/x86_64/abiquo-release-ee-3.6.0-2.el6.noarch.rpm

Update yum cache

yum clean all && yum makecache

Update abiquo packages

yum update 'abiquo-*'

Update databases

This step must be done on the database server.

Main Abiquo database

Ensure your hostname is in your DNS or in your /etc/hosts file.

abiquo-liquibase [-h DB hostname] [-P DB port] [-u user] [-p password] update

There is a known issue with upgrades from 3.2 versions where the following message appears and the liquibase update fails:

Liquibase update Failed: Validation Failed:
1 change sets check sum
src/X.X.X-XX/kinton-X.X.X.xml::ABICLOUDPREMIUM-XXXX-XxxxxxxxXXxXxxxxxxXxxxxx::XXXXXXXXX is now: 7:ee2fa6e058ec76c7abf801567898917d
For more information, use the --logLevel flag

This can be easily solved by executing the following command and retrying the abiquo-liquibase update command.