Virtuozzo OnApp 5.5.0-90 Update
This version of a Control Panel and CloudBoot update was released on July 2, 2018. The information below refers to the release notes and upgrade instructions for the Control Panel. For information on the CloudBoot release notes and upgrade instructions, refer to Virtuozzo OnApp 5.5 Patch 6 CloudBoot Update.
| Key | Release Notes | Affects Version/s |
|---|---|---|
| CORE-11919 | Fixed the issue when there were negative values stores in Redis DB for vCloud Director virtual server disks. | 5.5 |
CORE-12141 | Fixed the issue when pending transactions were not processed and not resent from Virtuozzo OnApp daemon to RabbitMQ because of a race condition. | 5.0-5.5 |
| CORE-12142 | Fixed the issue when importing firewall rules from vCloud Director to Virtuozzo OnApp failed due to an undefined method error. Reimplemented the logic of processing firewall rules via Advanced Edge Gateway to handle only rules where both source and destination are IP addresses. | 5.5 |
CORE-12224 | Fixed the issue when a billing calculator was not updated based on the pricing and limits set for data store zones in the bucket while users were editing a disk size. | 5.5 |
| CORE-12255 | Fixed the issue when removing a vCloud Director instance from CP failed due to a missing network in a network join. | 5.5 |
| CORE-12269 | Fixed the issue when simultaneously destroying multiple virtual servers with swap disks caused the Redlock::LockError error while the primary disk was deactivated but the second volume remained active. | 5.5 |
| INSTALLER-346 | Fixed the issue when the virsh tool was unavailable after upgrading to libvirt 4.1 on CentOS 6 Xen. | All Virtuozzo OnApp versions |
| INSTALLER-348 | Fixed the issue when the installer did not manage the Xen Dom0 maximum memory value that was set via a kernel option in the boot loader. | All Virtuozzo OnApp versions |
| INSTALLER-351 | Fixed the issue when incorrect guest statuses were reported for compute resources with 400 and more virtual servers - updated the vnc_ports.sh script to increase the speed of the VNC ports reporting via SNMP. | All Virtuozzo OnApp versions |
Patch Installation
Upgrade Control Panel Server
To apply the patch into Control Panel (running 5.5.0 version):
Update Virtuozzo OnApp YUM repository file:
1# rpm -Uvh http://rpm.repo.onapp.com/repo/onapp-repo-5.5.noarch.rpmUpdate the Control Panel installer package:
1# yum update onapp-cp-installRun the Control Panel installer:
1# /onapp/onapp-cp-install/onapp-cp-install.shAt the end of the update, you need to reply ‘yes’ when the system offers to download ISOs and images. This is required to install version 6.9 recovery images.
Upgrade Static Compute Resources
Make sure your compute resource is visible and online in the Control Panel.
Download and install the latest Virtuozzo OnApp YUM repository file:
1# rpm -Uvh http://rpm.repo.onapp.com/repo/onapp-repo-5.5.noarch.rpmUpgrade Virtuozzo OnApp compute resource installer package:
1# yum update onapp-hv-installUpdate your server OS components (if required):
1# /onapp/onapp-hv-install/onapp-hv-xen-install.sh -yRun compute resource installer: For CentOS XEN compute resources:
1# /onapp/onapp-hv-install/onapp-hv-xen-install.shFor CentOS KVM compute resources:
1# /onapp/onapp-hv-install/onapp-hv-kvm-install.sh
Reboot static compute resources.
Xen CentOS 6 compute resources must be rebooted to complete the update procedure.
Patch Installation for Clouds with High Availability Control Panel
To apply the patch for clouds with the High Availability Control Panel run the following commands on all Control Panel servers:
Disable managing resources on all nodes by running the following command once on any of the nodes:
1# crm configure property maintenance-mode=trueUpdate Virtuozzo OnApp YUM repository file:
1# rpm -Uvh http://rpm.repo.onapp.com/repo/onapp-repo-5.5.noarch.rpmRun the Control Panel installer:
1# /onapp/onapp-cp-install/onapp-cp-install.shAt the end of the update, you need to reply ‘yes’ when the system offers to download ISOs and images. This is required to install version 6.9 recovery images.
Switch all nodes back online by running the following command once on any of the nodes:
1# crm configure property maintenance-mode=falseEnsure that the lsyncd service is not started during the whole CP upgrade procedure. In separate consoles, connect to all three CP servers and run the following command:
1watch -n 0.1 /etc/init.d/lsyncd stop