Should a failure happen to occur in your Cloud Manager 2.1.5 system, you can revert to Cloud Manager 2.1.4 by using the following steps:
Ensure that all Cloud Manager services are shut down. Use the following command at the Application Server command line:
/etc/init.d/netiq/cloudmanager clean
Uninstall the Cloud Manager RPMs. Use the following command at the Application Server command line:
rpm --erase netiq-cloudmanager-2.1.5 netiq-cloudmanager-lib-2.1.5
Install the Cloud Manager 2.1.4 RPMs. Use the following command at the Application Server command line:
rpm -Uvh netiq-cloudmanager-2.1.4-<build_number>.noarch.rpm
Restore the configuration file backup that the configurator collected during the upgrade Use a command similar to the following:
./backup -r -f /var/opt/netiq/cloudmanager/cfg-auto-backup-<version>-to-<new version>.tar.gz
NOTE:If you chose to perform a complete Cloud Manager file system backup, you would use a command similar to the following:
./backup -r -f /var/opt/netiq/cloudmanager/<full_backup_before_2.1.5>.tar.gz
Restore the backup of the Postgres database you used before the upgrade.
IMPORTANT:The database you have been using with Cloud Manager 2.1.5 must be clean and the database user must exist for the upgrade to succeed. You might have to drop the existing database, then re-create it before you can revert to the prior database.
When you are sure that the existing database is clean, use a command like this to restore the former database that you backed up:
sudo -u postgres psql -d cloudmanager -f /var/opt/netiq/cloudmanager/cm_database_backup.dump.out
Start the restored version of Cloud Manager:
/etc/init.d/netiq/cloudmanager start