Virtuozzo OnApp 6.3 Patch 1 (6.3.1-1)

02 December 2020

This document provides information on fixes implemented as a part of the 6.3.1-1 update, as well as the upgrade instructions for:

The upgrade instructions for CloudBoot are available at Virtuozzo OnApp 6.3 Patch 1 CloudBoot Update.

Fixes

The following issues were fixed in the scope of the Virtuozzo OnApp 6.3 Patch 1 update.

Key	Release Notes	Affected Versions
CORE-17656	It was impossible to copy the CDN CNAME URL to a clipboard.	6.0 Patch 9
STORAGE-2307	A fully loaded Storage Controller was allowing to overcommit memory which could cause OOM issues.	6.1 Patch 1 - 6.3
STORAGE-2268	The vDisk related API calls on Static Hypervisors running Integrated Storage did not always complete without delays.	6.1
INSTALLER-537	The HA installation failed on Centos 7 operating systems.	6.3

Patch Installation

The instructions below are relevant if you already run Virtuozzo OnApp 6.3.

Upgrade Control Panel Server

To apply the patch to a Control Panel based on Virtuozzo OnApp 6.3, run the Control Panel installer:

1
# /onapp/onapp-cp-install/onapp-cp-install.sh --quick-update

Upgrade Static Compute Resources with Integrated Storage (CentOS7 KVM only)

To upgrade static compute resources with integrated storage, you should first check if you have enough memory for the storage upgrade. To do that, run the following command:

1
/usr/pythoncontroller/python3 /usr/pythoncontroller/check_ram_before_upgrade.pyc

If there is enough RAM and you can proceed with upgrade, you will see the following response:
1
Cloud is ready to upgrade

If there is not enough memory on the storage controller for the upgrade, you will see the following response:

1
2
3
Warning increase RAM for IS Controller 0 at HV 192.168.1.37 at least to 2278 MB
Warning increase RAM for IS Controller 1 at HV 192.168.1.38 at least to 1248 MB
Warning increase RAM for IS Controller 0 at HV 192.168.1.38 at least to 1248 MB

In that case, you should increase the Controller RAM to the number shown in the above script. After doing that you can proceed with the upgrade.

Before initiating the upgrade, there should be no degraded disks.
After performing the upgrade on each compute resource, you should repair degraded disks before starting on the next.

To upgrade static compute resources with Integrated Storage, follow the next procedure:

Disable services monitoring (by monit, if used), stop storage controller, and libvirt related services:

1
2
3
4
# monit unmonitor all
# /etc/init.d/SANController stop
# systemctl stop libvirtd
# /etc/init.d/storageAPI stop

Update system packages (if required):

1
# /onapp/onapp-hv-install/onapp-hv-kvm-install.sh -y

Run compute resource installer (to update Virtuozzo OnApp, compute resource, and Integrated Storage components):
1
# /onapp/onapp-hv-install/onapp-hv-kvm-install.sh
Reboot compute resource if it is requested by the installer (on step 3).
If reboot isn’t required, remove the onapp-storage-startup.lock file:
1
# rm -f /run/onapp-storage-startup.lock

If reboot isn’t required, run Storage startup script:

1
# /onapp/onapp-storage-startup/onapp-storage-startup.sh

Upgrade Backup Server with Integrated Storage (CentOS7 KVM Only)

To upgrade backup servers with Integrated Storage, follow the next procedure:

Stop storage controller related services:

1
2
# /etc/init.d/SANController stop
# /etc/init.d/storageAPI stop

Update system packages (if required):

1
# /onapp/onapp-bk-install/onapp-bk-install.sh -y

Run Backup Server installer (to update Virtuozzo OnApp Backup Server and Integrated Storage components):
1
# /onapp/onapp-bk-install/onapp-bk-install.sh
If reboot isn’t required (you are on the recent kernel): remove the onapp-storage-startup.lock file:
1
# rm -f /run/onapp-storage-startup.lock
If reboot isn’t required (you are on the recent kernel): run Storage startup script:
1
# /onapp/onapp-storage-startup/onapp-storage-startup.sh