Virtuozzo OnApp 6.0 Patch 9 (6.0.0-275)
9 January 2020
This is an update for the Control Panel server and Static compute resources. This document provides information on improvements and fixes implemented as a part of the 6.0.0-275 update, as well as the upgrade instructions for:
Improvements
The following improvements were implemented in the scope of the 6.0.0-275 update.
| Key | Release Notes |
|---|---|
| CORE-15508 | Improved handling of transactions execution delays. |
| CORE-15524 | Improved the vCloud statistics by providing more details in log output, and added a notification in case of statistics collecting failure. |
| CORE-15525 | Now you get an alert notification in case vCloud statistics gathering transaction fails. |
| CORE-15725 | The Control Panel server now uses a new version of an image (7.7) for Recovery Mode. |
| CORE-15811 | Now you can create a VS from an OVA template with no backup server if you set NULL value for the backup server ID in the template’s database after it is uploaded. |
| CORE-16035 | Improved handling error output with special symbols while processing recipe on a VS with custom localization. |
| CORE-16101 | Now the IO limits are updated after hot migration of VS disk. |
| CORE-16126 | Now when enabling DRaaS for a VS, an additional 1GB disk is created on the shadow VS to store replication metadata and resume replication after a crash. |
| CORE-16128 | Improved DRaaS error handling if connection between source and shadow VSs is lost. |
| CORE-16176 | Updated the kernel for shadow VSs with DRaaS functionality to avoid crashes on Xen compute resources with Integrated Storage after update to Virtuozzo OnApp 6.0. |
| INSTALLER-465 | Installers for static compute resources and Control Panel now use a new version of an ISO template (7.7) for recovery. |
Fixes
The following issues were fixed in the scope of the 6.0.0-275 update.
| Key | Release Notes | Affected Versions |
|---|---|---|
| CORE-12356 | When you tried to create vApp via API, the transaction failed with a system error. | 6.0.0-196 |
| CORE-12966 | When you tried to delete the primary network interface from the VS associated with a vApp at the VS details page, the network interface was deleted but the transaction failed with a system error in the Logs menu. | 6.0.0-62 - 6.1 Edge 1 |
| CORE- | If you tried to import vCloud resources, and then resynced it, both transactions were successful, but the data store was not imported. | 6.0.0-196 |
| CORE-14717 | After you created a Linux-based VS from a template imported from vCenter, and then tried to add an IP address to this VS at the Assign IP Address page, the transaction failed. | 6.1 Edge 1 - 6.0.0-196 |
| CORE-14804 | If a vCenter Windows-based VS had 3 disks assigned, you deleted one of the disks and then tried to assign a new one, the transaction failed with a system error. | 6.1 Edge 1 - 6.0.0-196 |
| CORE-15073 | After you imported a vCenter VS with password encryption option enabled to Control Panel and tried to set root password, the popup elements were displayed incorrectly. | 6.0.0-196 |
| CORE-15110 | After you enabled/disabled disk autobackups, the message in the confirmation notification was not decoded properly. | 6.0.0-62 |
| CORE-15230 | If you sorted VSs by labels at the Virtual Servers page, the order changed back to the default identifier-sorted one as you navigated to another page. | 6.0.0-196 |
| CORE-15254 | When you tried to deploy a vCenter VS from some OVA templates, the transaction failed with a system error. | 6.0.0-196 - 6.1 Edge 2 |
| CORE-15302 | You could not assign an IP address to a VS at the Assign IP Address page without the All actions on virtual server's IP addresses permission enabled. | 6.0.0-238 |
| CORE-15334 | When you selected a new language with just several translated phrases and tried to enable this language for a specific user, the 500 Interanl Server error appeared at the Locales page. | 6.2 Edge 1 |
| CORE-15357 | It was possible to delete a VS disk with the Destroy any disk permission disabled, if the Manage Virtuozzo OnApp Storage permission was enabled. | 5.10 |
| CORE-15385 | When you tried to migrate a VS to the compute resource without the network bridge, the transaction failed. | 6.0.0-238 |
| CORE-15413 | You could not assign an IP address to the network interface of the vCenter Windows-based VS. | 6.0.0-238 |
| CORE-15435 | After you uploaded custom logo and favicon during editing a new theme in Look and Feel Settings menu, the corresponding fields shifted in the Virtuozzo OnApp interface. | 6.1 Edge 2. - 6.1 |
| CORE-15469 | When you tried to add a compute zone with a newly-generated certificate to federation at the Compute Zones page, the transaction failed. | 6.0.0-238 - 6.2 Edge 1 |
| CORE-15476 | When you created a VS with the remote console password containing the "<", ">", or "&" symbols, you couldn't access the VNC console. | 6.0.0-238 - 6.1 |
| CORE-15492 | When you tried to remove an IP address from vCenter Windows-based VS, the Resource not found error message appeared. | 6.0.0-238 |
| CORE-15502 | When you tried to generate the VS hourly statistics through API call, the Outstanding amount was set to incorrect value at the User Details page. | 6.0.0-196 |
| CORE-15512 | When you tried to decrease a vDisk's size of an Integrated Storage data store, the actual size of the disk and the one indicated in the logs were different. | 6.0.0-196 - 6.1 Edge 2 |
| CORE-15576 | When you clicked the labels of the Disks r/w columns to sort the results at the Usage Statistics page, the results were not displayed in the correct order. | 6.0.0-196 |
| CORE-15592 | If you cancelled a zombie transaction at the Logs page, it was displayed as failed instead of cancelled. | 6.1 - 6.2 Edge 1 |
| CORE-15611 | It was possible to set higher than 100% CPU priority minimal or default limit for Compute Zone at the Access Control page. | 6.0.0-196 |
| CORE-15625 | After you imported a vCenter VS to Virtuozzo OnApp and set a root password, the text in the Set Password pop-up window became Set password for virtual machine instead of Set current password for virtual machine. | 6.0.0-196 - 6.1 Edge 2 |
| CORE-15670 | After you changed an owner for a VS with backup schedules, the schedules were not reassigned to the new VS's owner, and the latter was not able to manage them. | 6.0 |
| CORE-15708 | Swap size equal to doubled RAM size was automatically allocated to a Windows-based VS and deducted from the general disk size at the Resources step of VS creation wizard. | 6.0.0-196 |
| CORE-15805 | It was impossible save edited values of limits for compute zones in the Access Control section of a bucket. | 6.0.0-238 |
| CORE-15880 | Sometimes, if you ran several backups on a compute resource, the transactions failed. | 6.0.0-159-6.0.0-196 |
| CORE-16057 | After the cold migration of the VS between compute resources with local storage, the VS's disk was corrupted. | 6.0.0-196 |
| CORE-16075 | It you tried to perform resize without reboot while VS backup transaction was running, the reboot was still performed. | 6.0.0-196 |
| CORE-16094 | The 500 Internal Server Error appeared at the Custom Recipe Variables page if you tried to add a custom recipe variable to a template. | 6.0.0-238 - 6.2 Edge 1 |
| CORE-16184 | CPU Benchmark and CPU Score graphs were displayed in one Scores and Benchmarks pop-up window instead of being divided into two corresponding tabs. | 6.0.0-196 |
| CORE-16245 | If autoscaling for RAM and CPU was enabled, estimated price per hour for memory was doubled on autoscaling event. | 6.0.0-196 |
| CORE-16307 | You could not log in to your CP account using Google OAuth. | 6.0 |
Patch Installation
Upgrade Control Panel Server
To apply the patch to a Control Panel server based on Virtuozzo OnApp 6.0:
Upgrade the Virtuozzo OnApp Control Panel installer package:
1# yum update onapp-cp-installRun the Control Panel installer:
1# /onapp/onapp-cp-install/onapp-cp-install.sh --quick-update='monit rabbitmq'Start Virtuozzo OnApp related services (like onapp, onapp-licensing, httpd) if ‘—quick-update’ option was used for the installer.
Upgrade Static Compute Resources
Make sure your compute resource is visible and online on the Control Panel. Then you can proceed to the following procedure and run the steps, depending on a version from which you upgrade.
If you upgrade from Virtuozzo OnApp = 6.0.0-238, run the following steps (1-2).
Upgrade the Virtuozzo OnApp compute resource installer package:
1# yum update onapp-hv-installInitiate recovery images/iso download by running installer with -t option with the following command:
For KVM compute resources
1# /onapp/onapp-hv-install/onapp-hv-kvm-install.sh -tFor Xen compute resources:
1# /onapp/onapp-hv-install/onapp-hv-xen-install.sh -t
If you upgrade from Virtuozzo OnApp =< 6.0.0-62, run the following steps (1-3).
If you have CentOS 7 Xen resources, remove the centos-release-xen-46 package:
1# rpm -e centos-release-xen-46Upgrade the Virtuozzo OnApp compute resource installer package:
1# yum update onapp-hv-installRun Static compute resource installer:
For KVM compute resources
1# /onapp/onapp-hv-install/onapp-hv-kvm-install.shFor Xen compute resources
1# /onapp/onapp-hv-install/onapp-hv-xen-install.shPlease confirm the download of Recovery Templates and other ISOs/images when you are prompted.
Upgrade Static Backup Server
If you upgrade from Virtuozzo OnApp = 6.0.0-238, skip the upgrade static backup procedure.
If you upgrade from Virtuozzo OnApp =< 6.0.0-62, follow the next procedure to upgrade static backup server.
Upgrade the Virtuozzo OnApp backup server installer package:
1# yum update onapp-bk-installUpdate tar on CentOS 6 backup servers:
1# yum update tarRun the installer:
1# sh /onapp/onapp-bk-install/onapp-bk-install.sh
