Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Prerequisites

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

Previous steps, backup, stop services, blah blah blah

Perform the packages upgrade

This step must be done on all Abiquo servers, including Abiquo Management Server, Remove 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 updates repositories, please locate the abiquo-release-ee package of your destination version and install it with next command, for latest abiquo version this would be

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
Is there a known issue with upgrades from 3.2 versions where next message appears and fails to apply the liquibase update:
 
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 next command and retry the abiquo-liquibase update command.
 
abiquo-liquibase clearCheckSums

Redis on Abiquo Remote Services and Monolithic servers

Before logging in to Abiquo after an upgrade, all users must clear the browser cache on their machines. Check that the Abiquo GUI reports the correct version in the bottom left of the browser. 

Test the Upgrade

Perform basic testing to validate the installation, for example:

  1. Deploy VM
  2. Create instance
  3. Create persistent VM
  4. Deploy VM with external storage

Unable to render {include} The included page could not be found.

Unable to render {include} The included page could not be found.

  • No labels