Virtuozzo Hybrid Infrastructure 5.0 Update 1 (5.0.1-42)¶
Issue date: 2022-03-03
Applies to: Virtuozzo Hybrid Infrastructure 5.0
Virtuozzo Advisory ID: VZA-2022-009
This update provides support for more guest operating systems, as well as bug fixes and improvements.
2. New Features¶
[Compute] Added support for Windows Server 2022, AlmaLinux, and Rocky Linux as guest operating systems.
3. Bug Fixes¶
Fixed the false-positive alert “Swap space is used.” (VSTOR-50067)
Fixed the false-positive alert “Disk may run out of space” that appears for a cache disk after a bulk storage disk assignment. (VSTOR-51196)
The flavor list is empty during a VM creation if more than 100 flavors are available. (VSTOR-51171)
Third-party IdP authentication fails if an IdP provider has multiple keys in a key jar. (VSTOR-50943)
Unable to create high availability if an update is downloaded but not installed. (VSTOR-50815)
A UX improvement for a domain user creation via vinfra. (VSTOR-50472)
Authorization is no longer required to configure notifications to use SMTP. (VSTOR-50314)
Impossible to use a vGPU configuration file with letters in a hexadecimal PCI address. (VSTOR-50248)
Fixed the reason of the “Conflicting resource provider name” error. (VSTOR-50141)
Fixed usage for a placement quota. (VSTOR-49906)
Entering the maintenance mode may fail, though there are enough resources to enter. (VSTOR-49458)
Fixed a wrong archive size for some cases. (VSTOR-47111, VSTOR-48869)
Stability and performance improvements. (VSTOR-49719, VSTOR-49700, VSTOR-49499, VSTOR-51249, VSTOR-51639, VSTOR-51232, VSTOR-51125, VSTOR-50968, VSTOR-50915, VSTOR-50725, VSTOR-50627, VSTOR-50251)
4. Installing the Update¶
You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is required to complete the upgrade. Upgraded nodes will be rebooted automatically, one at a time. During the reboot, the storage service and the admin panel might be unavailable on cluster configurations without the redundancy of services or data.
The source of this advisory is available in the JSON file.