1. Overview

This update introduces a new service for virtual machine migration between infrastructures, read-only project access, and support for additional guest operating systems. It also includes improvements to platform stability and reliability and addresses issues identified in previous releases.

2. New Features

• [User management] Read-only project access. Added support for read-only access for self-service users. Administrators can manage view-only permissions via the admin panel and the vinfra command-line tool to enable secure troubleshooting and monitoring without granting full access.

• [Compute service] Migration service (early access). Introduced a migration service that enables moving virtual machines and workloads between infrastructures. This feature is intended for evaluation purposes only and is not recommended for use in production environments. The feature is available in both the admin and self-service panels.

  The initial release provides the following capabilities:

  • Migration of virtual machines from VMware vSphere

  • Agentless virtual machine migration

  • Changed Block Tracking (CBT) support

  • Operating system morphing

  • IP and MAC address preservation

  • Parallel migration support

  To perform migrations, you must provide your own VMware Virtual Disk Development Kit (VDDK). For details, refer to the product documentation.

  If you do not have access to a Broadcom account, contact our support team for assistance. To provide feedback about this feature, contact your account manager or email info@virtuozzo.com.

• [Compute service] New guest OS support. Added support for Debian 13 and CentOS Stream 10.

3. Improvements

• Improved reliability of week-long testing. The updated testing framework provides enhanced system load analysis, improved consistency and leak detection, better failure handling, scalable guest loaders, and more reliable long-duration test execution through automated log rotation and cluster state preservation.

4. Bug Fixes

• A VM could fail to start or migrate after an NFS snapshot deletion timeout left inconsistent volume metadata. (VSTOR-118159)

• Failed live migrations could leak compute placement reservations under heavy load. (VSTOR-119720)

• A false low-disk alert could appear when several policies share the same erasure-coding scheme. (VSTOR-121112)

• Chunked S3 uploads without a Content-Length header could return HTTP 400. (VSTOR-126176)

• NetApp ONTAP volume scheduling could fail near LUN limits. (VSTOR-126598)

• The PCI-enabled flag could remain after a cold resize to a flavor without PCI devices. (VSTOR-128162)

• The Pure Storage driver could return empty volume statistics on new or lightly loaded arrays. (VSTOR-128551)

• Fixed the limited-use text in the UI. (VSTOR-128693)

• Incorrect physical core count could be reported on asymmetric NUMA hosts. (VSTOR-128762)

• Archive migration via ARP with redirects could fail during upstream authentication for pull operations. (VSTOR-129264)

• The Cinder default scheduler could omit the driver filter and goodness weigher during volume placement. (VSTOR-130186)

• Live resize could be unavailable when the Nova API ran only on controller nodes without the compute role. (VSTOR-130609)

5. Installing the Update

You can update Virtuozzo Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• Backend initialization could fail when more than one project used the name ‘admin’. (VSTOR-128568)

• The Backup Gateway service could crash when removing an empty file. (VSTOR-129614)

• Collecting a problem report could temporarily consume significant root disk space. (VSTOR-130137)

• Stability fixes for the hypervisor. (VSTOR-120606, VSTOR-129333, VSTOR-129336, VSTOR-129974)

• Stability fixes for object storage. (VSTOR-128142, VSTOR-128767, VSTOR-129393, VSTOR-129499)

3. Installing the Update

You can update Virtuozzo Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• Improved error messages for QEMU updates. (VSTOR-127496)

• Creating a load balancer could fail with “Unable to find security_group”. (VSTOR-128436)

• Neutron could consume excessive memory when listing networks with a large number of RBAC rules. (VSTOR-129065)

• Gnocchi could be overloaded by repeated PATCH requests. (VSTOR-129274)

3. Installing the Update

You can update Virtuozzo Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This release focuses on technical improvements, user experience enhancements, storage performance, and S3 protocol capabilities. It also introduces the product rename from Virtuozzo Hybrid Infrastructure to Virtuozzo Infrastructure. Additionally, this release delivers stability fixes and addresses issues identified in previous releases.

2. New Features

• [Compute] VM migration management. System administrators can monitor migration progress, cancel or retry migrations, and view the history of migration tasks. For failed migrations, the system shows the exact step where the failure occurred.

• [Compute] GPU metering. Added support for creating custom metrics and mapping GPU-enabled flavors to these metrics, enabling GPU usage tracking in GPU-hours.

• [Object storage] S3 storage multitenancy. Introduced initial support for aligning S3 storage with the compute tenancy model (project-based isolation). In this release, the functionality is available via the command-line interface. Further enhancements are planned in future releases.

3. Improvements

• Updated S3 API schemas to support protocol extensions, including Object Tagging.

• Improved performance for workloads using small block sizes (for example, 8 KB) with erasure coding, resulting in better storage efficiency and responsiveness.

• Introduced a Grafana dashboard that provides improved visibility into the data healing (replication) process, including preliminary estimated completion times (ETAs).

4. Bug Fixes

• Unsupported baseline CPU models could be offered for a cluster, preventing some VMs from being created. (VSTOR-96428)

• License alerts did not respect the automatic license renewal period. (VSTOR-102166)

• Deleting a volume snapshot could block the UI until the operation completed. (VSTOR-104120)

• Creating a load balancer could fail when Proxy Protocol was enabled together with a UDP listener. (VSTOR-104559)

• The CS service could enter a failed state if its repository directory remained locked for too long. (VSTOR-106595)

• Upgrade eligibility checks and upgrade tasks could start before update packages were downloaded. (VSTOR-119967)

• CSD services with RDMA enabled could fail to recover automatically after a network restart. (VSTOR-120417)

• Backup storage throttling could be configured on a node that did not run backup storage services, causing the operation to fail. (VSTOR-120792)

• The S3 ACC service could indefinitely retry requests to the name service. (VSTOR-121082)

• Stale shaman_node_crash_threshold metrics could remain after a node was released from the cluster. (VSTOR-121148)

• A node could remain stuck in the ‘Entering maintenance’ state. (VSTOR-121204)

• Removing a compute VLAN network could fail if the VLAN interface was already absent. (VSTOR-121404)

• A conflict could occur when resuming a virtual machine that had already been resumed. (VSTOR-121409)

• Clients could continue to be redirected to an old upstream for too long after a redirect policy was changed. (VSTOR-121454)

• The nova-compute service could get stuck while running nova-qcow2-backup if a required public key was missing. (VSTOR-121902)

• More PCI devices than requested could be reserved during VM rescheduling. (VSTOR-122298)

• The qemu-img check could fail to repair a corrupted QCOW2 image. (VSTOR-122354)

• Object storage alerts did not correctly distinguish between S3 and NFS volumes. (VSTOR-122521)

• Downloading updates could fail when /tmp was mounted as tmpfs. (VSTOR-123125)

• The system could report an unmount error for a mount point that was already unmounted. (VSTOR-123203)

• Users could not dismiss the telemetry consent banner. (VSTOR-123871)

• Prometheus 3.3.1 could not collect metrics when Consul was still running an older version. (VSTOR-124089)

• The load balancer backend could set an incorrect session persistence type for HTTP cookie-based persistence. (VSTOR-124852)

• A race condition could occur in hostd while resolving the current host name. (VSTOR-124904)

• VM live resize was not fully restricted in unsupported scenarios. (VSTOR-125086)

• Incorrect metadata tier information was displayed in settings after configuring an S3 cluster. (VSTOR-125304)

• Incremental backups could fail on heavily loaded clusters. (VSTOR-125509)

• The public Barbican endpoint could be used instead of the internal endpoint during load balancer creation. (VSTOR-125563)

• A KeyError could occur during live migration after a failed live NIC detach operation. (VSTOR-125622)

• The backend could resume Shaman too early during a node update. (VSTOR-125693)

• OpenStack Watcher audits could remain pending after a node stopped acting as a controller. (VSTOR-125836)

• VM live migration could fail after increasing the number of vCPUs using live resize. (VSTOR-126349)

• Node registration settings could be removed even if registration did not complete successfully. (VSTOR-126413)

• Flavor lists were not paginated in the Kubernetes worker edit dialog. (VSTOR-126426)

• Load balancer ‘Overview’ charts showed incorrect throughput units (traffic displayed in bit/s instead of bytes/s). (VSTOR-126928)

5. Installing the Update

You can update Virtuozzo Infrastructure in the SETTINGS > UPDATES section of the admin panel. A reboot is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update delivers important stability fixes and includes a product name change.

2. New Features

• The product name has changed from Virtuozzo Hybrid Infrastructure to Virtuozzo Infrastructure.

3. Bug Fixes

• Improved monitoring and dashboard responsiveness on large clusters by optimizing metric caching. (VSTOR-122117)

• Updates could fail on nodes with floppy drives. (VSTOR-124715)

• Background operations (such as disk replacement or repository checks) could fail or get stuck because database objects were incorrectly used across worker threads. (VSTOR-125077)

• A stability fix for virtual machines. (VSTOR-125367)

4. Installing the Update

You can update Virtuozzo Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a security fix and stability fixes for the storage service.

2. Bug Fixes

• Bucket object lock is removed after setting a bucket policy. (VSTOR-122723)

• Archive files are not accessible if there are issues with replication. (VSTOR-123191)

• A security fix for CVE-2025-15467. (VSTOR-123590)

• Stability fixes for the storage service. (VSTOR-120193, VSTOR-124043, VSTOR-124138)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a security fix.

2. Bug Fixes

• A security fix for CVE-2025-15467. (VSTOR-123590)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a security fix.

2. Bug Fixes

• A security fix for CVE-2025-15467. (VSTOR-123590)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a security fix.

2. Bug Fixes

• A security fix for CVE-2025-15467. (VSTOR-123590)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a security fix.

2. Bug Fixes

• A security fix for CVE-2025-15467. (VSTOR-123590)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a security fix.

2. Bug Fixes

• A security fix for CVE-2025-15467. (VSTOR-123590)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a security fix.

2. Bug Fixes

• A security fix for CVE-2025-15467. (VSTOR-123590)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure introduces support for two-factor authentication (2FA) for system administrators and self-service users, along with several other new features and improvements. Additionally, this release delivers stability fixes and addresses issues found in previous releases.

2. New Features

• [Security] System administrators and self-service users can now configure TOTP-based two-factor authentication (2FA) using Google Authenticator or Microsoft Authenticator. Administrators can enforce 2FA usage to strengthen compliance and improve account security.

• [Compute service] Custom MAC address prefixes can now be set for all VM network interfaces. This allows system administrators to avoid MAC duplication when running multiple clusters within the same L2 network segments.

• [Compute service] Support for new guest operating systems:

  • Red Hat Enterprise Linux 10

  • AlmaLinux 10

  • Rocky Linux 10

  • SUSE Linux Enterprise 15 SP6 and SP7

  • Oracle Linux 10

3. Improvements

• [Updates] QEMU hypervisor updates no longer require rolling maintenance with VM migration and node reboots. Future updates to the compute service that include the QEMU hypervisor will not trigger rolling maintenance, reducing operational overhead.

• [Core storage] Sequential write performance doubles on tiers using replication redundancy with checksumming enabled. This improvement benefits workloads such as append-only databases and speeds up mass volume backups and snapshot operations.

• [Core storage] Improved erasure coding schema selection when managing storage policies. The system now recommends an optimal schema based on the number of available failure domains. Administrators can also configure custom M+N schemas for non-standard configurations directly in the admin panel, without using command-line tools.

• [Object storage] A new S3 health check API endpoint allows system administrators to verify node health from an external HAProxy load balancer, ensuring traffic is routed only to healthy nodes.

• [Networking] Infrastructure network migration now supports networks with both IPv4 and IPv6 subnets. This significantly reduces the time required to prepare clusters for physical migration and simplifies dual-stack network management.

4. Bug Fixes

• The cluster join command has a retry issue. (VSTOR-47080)

• Added a missing alert for degraded storage arrays. (VSTOR-80691)

• Crash reports consume all available disk space on hosts without internet access. (VSTOR-86950)

• The check-for-updates task may get stuck. (VSTOR-87198)

• The S3 service does not restart after a storage mount restart. (VSTOR-89576)

• Router connectivity issues affect multiple routers after a processing error. (VSTOR-91120)

• Snapshot deletion causes VM info file synchronization issues. (VSTOR-93041)

• NFS storage is created without proper redundancy settings. (VSTOR-94861)

• A libvirt race condition causes VM management issues. (VSTOR-95999)

• An upgrade fails on older installations that are missing a configuration file. (VSTOR-98221)

• Network creation allows spaces in names. (VSTOR-99460)

• The disk reservation state persists after an agent restart. (VSTOR-101927)

• Error messages are missing from task logs. (VSTOR-102057)

• Security fixes. (VSTOR-101281, VSTOR-102955)

• DHCP high availability degrades after node replacement. (VSTOR-103562)

• A compute node is not removed from the placement service on deletion. (VSTOR-104797)

• The Neutron service hangs for five minutes after OVS reconnection. (VSTOR-106311)

• The Gnocchi service status is incorrectly reported on secondary management nodes. (VSTOR-106602)

• A misleading critical alert appears when the compute backup service is misconfigured. (VSTOR-106690)

• The compute backup scheduler allows excessive recovery points (up to 999). (VSTOR-107185)

• The node status is incorrectly shown as failed due to a single service failure. (VSTOR-107214)

• An upgrade fails when the registry is disrupted during tarball unpacking. (VSTOR-107868)

• A race condition exists in network configuration during VM interface attachment. (VSTOR-108710)

• A kernel workqueue crash occurs in the network event handler. (VSTOR-108908)

• The post-upgrade script accesses unassigned nodes. (VSTOR-109418)

• VPN logs are deleted when a router is re-enabled. (VSTOR-109422)

• VM unshelving fails after evacuation. (VSTOR-109679)

• High availability reconfiguration may get stuck. (VSTOR-109896)

• A kernel crash may occur with checksumless chunk servers. (VSTOR-109945)

• The disk replacement task blocks system upgrades. (VSTOR-110037)

• An upgrade fails due to stuck NFS mount points. (VSTOR-110351)

• Manual instance evacuation conflicts with a running evacuation task. (VSTOR-110962)

• An incorrect 404 error is returned for pending disk reservations. (VSTOR-110978)

• Stability fixes. (VSTOR-113129, VSTOR-115462)

• Spice packages are missing in Red Hat Enterprise Linux 9. (VSTOR-113536)

• Domain name parsing fails for block nodes. (VSTOR-113808)

• Disk auto-replacement is not canceled when the repository is deleted. (VSTOR-113962)

• Nested virtualization is misconfigured on AMD processors during upgrade. (VSTOR-114793)

• Fixed an S3 recycle bin path validation issue. (VSTOR-115086)

• A compute node cannot be added with an OVS VLAN interface without network assignment. (VSTOR-115455)

• SR-IOV port attachment does not update the PCI device status. (VSTOR-116308)

• A load balancer remains stuck in the deletion state when TLS storage is unavailable. (VSTOR-116344)

• A file is not detached on a push error. (VSTOR-116577)

• The agent does not use cached CPU information. (VSTOR-116774)

• Snapshot creation fails for shelved VMs. (VSTOR-116783)

• The Accept-Ranges header is missing from S3 GetObject responses. (VSTOR-117834)

• Fixed duplicate quiesce calls during image creation. (VSTOR-117856)

• The S3 lifecycle configuration rejects empty filters. (VSTOR-118251)

• The backup process blocks storage mount operations. (VSTOR-118451)

• A network interface is not removed from the configuration after a detach failure. (VSTOR-118626)

• The same node in the HA configuration is repeatedly elected as primary. (VSTOR-118651)

• Storage re-encoding is blocked by invalid metadata. (VSTOR-118697)

• Failed to delete snapshots of shelved VMs. (VSTOR-118825)

• VM tag restrictions prevent underscore and dash characters. (VSTOR-118892)

• Fixed an incorrect command for setting password requirements. (VSTOR-119187)

• The UI prevents storage policy tier and failure-domain changes. (VSTOR-119333)

• Geo-replication creates empty files on unconfigured secondary nodes. (VSTOR-119537)

• Compute options are not rolled back on reconfiguration failure. (VSTOR-119570)

• OVS Manager creation fails at agent startup. (VSTOR-120216)

• A vGPU device is not deallocated during cold migration. (VSTOR-120502)

• Router connectivity fails after failover. (VSTOR-120603)

5. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. A reboot is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides important stability fixes.

2. Bug Fixes

• A stability fix for libvirt. (VSTOR-115013)

• Failed to add a node to the compute cluster. (VSTOR-115455)

• Fixed missing FUA write processing on dm-qcow2 and dm-ploop devices. (VSTOR-118628)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides important stability fixes.

2. Bug Fixes

• A stability fix for libvirt. (VSTOR-115013)

• Failed to add a node to the compute cluster. (VSTOR-115455)

• Fixed missing FUA write processing on dm-qcow2 and dm-ploop devices. (VSTOR-118628)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides important security fixes.

2. Bug Fixes

• A fix for volume attachment. (VSTOR-89294)

• Failed to move domains to a mount point during an update. (VSTOR-107377)

• A stability fix for QEMU. (VSTOR-111693)

• Failed to set the VirtIO video driver for VMs. (VSTOR-115326)

• A stability fix for the nova-compute service. (VSTOR-115470)

• kRPC failed to connect to certain chunk services. (VSTOR-116184)

• The OpenStack Watcher client does not recognize the –os-interface option. (VSTOR-116427)

• Failed to join a node to the storage cluster. (VSTOR-117529)

• An improvement for updates. (VSTOR-117823)

• Stability fixes for the storage service. (VSTOR-108984, VSTOR-116630)

• Stability fixes for the kernel. (VSTOR-116266, VSTOR-116268, VSTOR-116270, VSTOR-117191, VSTOR-116414, VSTOR-116467)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• Stability fixes for the storage service. (VSTOR-106269, VSTOR-108984, VSTOR-116630)

• A stability fix for QEMU. (VSTOR-111693)

• kRPC failed to connect to certain chunk services. (VSTOR-116184)

• A stability fix for the kernel. (VSTOR-116467)

• Failed to open an archive file. (VSTOR-116577)

• Failed to join a node to the storage cluster. (VSTOR-117529)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes and support for cumulative updates. Clusters running version 6.3.1 or later can now upgrade directly to the latest available version in a single step.

2. Bug Fixes

• A stability fix for vstorage-mount. (VSTOR-105770)

• Stability fixes for the Backup Gateway service. (VSTOR-104585, VSTOR-106556)

• Stability fixes for object storage. (VSTOR-107460, VSTOR-109406)

• The eligibility check fails after a second attempt to update the compute cluster. (VSTOR-108801)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes and support for cumulative updates. Clusters running version 6.2.1 or later can now upgrade directly to the latest available version in a single step.

2. Bug Fixes

• Failed to retry updating the kernel. (VSTOR-91715)

• Improvements for the storage garbage collector. (VSTOR-93149, VSTOR-100823)

• Failed to evacuate GPU VMs. (VSTOR-94519)

• Stability fixes for vstorage-mount. (VSTOR-97963, VSTOR-103996, VSTOR-105770)

• An incorrect quota for geo-replicating and migrating accounts. (VSTOR-98089)

• VM live migration failed. (VSTOR-98159)

• VMs lost network connectivity after stopping the neutron-ovs-agent. (VSTOR-100168)

• An improvement for the Backup Gateway recycle bin. (VSTOR-100875)

• Improvements for the Backup Gateway service. (VSTOR-89300, VSTOR-100883)

• The MDS service may fail to balance CS services during massive replication. (VSTOR-102823)

• The eligibility check fails after a second attempt to update the compute cluster. (VSTOR-108801)

• Stability fixes for object storage. (VSTOR-88635, VSTOR-91155, VSTOR-99249, VSTOR-99689, VSTOR-101301, VSTOR-107460)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a range of new features that cover the compute service, file and object storage, as well as updates. Additionally, this release delivers stability improvements and addresses issues found in previous releases.

2. New Features

• [Compute service] Resource policies. Introduced two policies with automatic VM live migration to balance workloads and prevent resource contention across compute nodes:

  • Dynamic consolidation places tagged VMs onto the minimum number of nodes.

  • Dynamic distribution spreads VMs evenly across nodes to balance compute capacity.

• [Compute service] New guest OS support. Added support for Windows 11 and Windows Server 2025 as guest operating systems. For these OSes, UEFI, Secure Boot, and TPM 2.0 are mandatory and enabled by default.

• [File storage] SMB 3.0 storage. New SMB 3.0 file storage enables high-performance file access from Windows and compatible clients.

• [Object storage] S3 observability improvements. Expanded the scope of collected data, refined existing metrics with additional labels, and increased bucket granularity for more precise monitoring and alerting in Grafana.

• [Updates] Cumulative update path. Clusters running version 6.2.1 or later can now upgrade directly to the latest available version in a single step. Clusters on earlier versions must first upgrade to 6.2.1 to enable cumulative updates.

3. Important Notes

• Alerts related to vCPU and RAM shortages on compute nodes are now marked with the lowest severity (‘Info’). With the introduction of resource policies, these alerts have reduced importance for capacity management. We recommend enabling resource policies instead of relying on these alerts and updating your operational processes accordingly.

4. Bug Fixes

• Fixed an issue with the Gnocchi service. (VSTOR-91660)

• The journal is not cleaned up if deleting the chunk service data takes too long. (VSTOR-95975)

• Failed to upload files to an S3 bucket. (VSTOR-101292)

• Improved connectivity for infrastructure networks assigned to multiple interfaces on a node. (VSTOR-103004)

• Unable to change the role of an SSD disk. (VSTOR-103537)

• Cannot create a VLAN Ethernet device if the physical device name is longer than 10 characters. (VSTOR-104016)

• A stability fix for Windows 2016 VMs. (VSTOR-104655)

• Not all OVS VLANs are created on a node when it is added to the compute cluster. (VSTOR-104995)

• Protected the vstorage-ui-backend services from starting accidentally while in standby. (VSTOR-106412)

• Fixes for the Neutron service. (VSTOR-97151, VSTOR-106418, VSTOR-108601, VSTOR-114214)

• Failed to delete snapshots. (VSTOR-106830)

• Stability fixes for maintenance mode. (VSTOR-101819, VSTOR-107062)

• Fixed the false-positive alert “Zero storage disks.” (VSTOR-107098)

• Disk cleanup is not synchronized with multiple released chunk services. (VSTOR-107582)

• Fixed the misleading UI for the All ICMP protocol in security group creation. (VSTOR-109067)

• Fixed the false-positive alert “Virtual DHCP server is unavailable from node.” (VSTOR-110177)

• Failed to proceed with an update after resetting the update state. (VSTOR-110362)

• Fixes for updating the compute cluster during an upgrade. (VSTOR-110398, VSTOR-112386)

• A stability fix for uploading S3 multipart objects. (VSTOR-110913)

• Stability fixes for the Cinder service. (VSTOR-111288, VSTOR-111660)

• Allocations for evacuated instances are not cleaned up when the usage quota is exceeded. (VSTOR-111732)

• vinfra tasks keep following nodes that were forcibly released. (VSTOR-112809)

• Fixed an error when changing the S3 metadata tier. (VSTOR-113197)

5. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• A stability fix for the Backup Gateway service. (VSTOR-104585)

• A stability fix for the S3 service. (VSTOR-109406)

• Stability fixes for the compute service. (VSTOR-112370, VSTOR-113126)

• Stability fixes for the storage service. (VSTOR-102304, VSTOR-112356, VSTOR-112454, VSTOR-113848)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a stability fix.

2. Bug Fixes

• A stability fix for VM live migration. (VSTOR-110793)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a stability fix.

2. Bug Fixes

• A stability fix for the chunk service. (VSTOR-109853)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a range of new features that cover the compute service, object and core storage, networking, as well as monitoring and alerts. Additionally, this release delivers stability improvements and addresses issues found in previous releases.

2. New Features

• [Compute service] UI for external storage management. Administrators can now attach, manage, and monitor external storage systems, including Pure Storage®, NetApp®, and any OpenStack-compatible FC/iSCSI/NFS array, directly from the admin panel, reducing CLI usage and minimizing configuration errors.

• [Compute service] Default security group templates. Using the OpenStack API, administrators can define project-wide ingress and egress rules that apply automatically upon project creation. This eliminates per-project manual rule setup and minimizes the risk of insecure defaults.

• [Compute service] New network port screen. The new screen provides key information about all network ports, helping administrators troubleshoot networking issues in the compute cluster.

• [Object storage] IPv6 support. The S3 service now supports IPv6 in addition to IPv4, removing address-space limits in large-scale or dual-stack deployments.

• [Object storage] Graphical bucket policy builder. The self-service panel now includes a user-friendly policy builder for creating bucket access policies. Beginners can use guided wizards, while advanced users can paste full JSON policy definitions.

• [Object storage] Faster GET throughput. Internal optimizations increase read performance to approximately 12 GB/s per node, significantly accelerating analytics, AI/ML, and media workloads.

• [Core storage] Smarter usage metering during erasure coding changes. A tunable overhead parameter prevents temporary usage spikes from causing overbilling or quota violations during large dataset re-encoding.

• [Core storage] Automatic SSD/NVMe wear-level detection. New disk health analytics trigger alerts when a disk’s remaining lifetime drops below 10% (warning) or 5% (critical). Once the wearout threshold is reached, affected chunk services are placed into maintenance mode to preserve data redundancy and system availability.

• [Core storage] Replication write modes. The storage cluster now supports two write modes for replication redundancy: CS fanout and client fanout. When enabled, these modes optimize storage performance based on network conditions and workload types.

• [Networking] Multi-subnet support within a single network. External infrastructure networks can now be assigned multiple IPv4 subnets. This removes the need for additional VLANs and helps prevent public IP exhaustion.

• [Monitoring and alerts] Cluster configuration monitoring and alerting. New metrics and alerts enable system administrators to monitor core and management services across cluster nodes and receive notifications about configuration anomalies.

3. Important Notes

• The Compute API will be unavailable for up to 15 minutes during the update, temporarily disabling the ability to manage compute workloads.

4. Bug Fixes

• Improved alerts on memory and swap usage. (VSTOR-95964)

• A stability fix for block storage. (VSTOR-97082)

• Fixed incorrect VPN connection status. (VSTOR-97157)

• Stability fixes for the Neutron service. (VSTOR-98157, VSTOR-98509, VSTOR-99169, VSTOR-101941)

• Fixed a false-positive alert on port check. (VSTOR-98184)

• Fixed the Nginx error “Too many open files.” (VSTOR-99055)

• A VIP address can be assigned outside the allocation pool during load balancer creation. (VSTOR-99359)

• Fixed a potential infinite loop in the SNMP parsing code. (VSTOR-99624)

• A stability fix for Kubernetes. (VSTOR-99870)

• Locked archives affect the calculation of space usage. (VSTOR-100409)

• Added the ‘tenant_id’ label to volume backup metrics. (VSTOR-100472)

• A stability fix for the Gnocchi service. (VSTOR-100484)

• Fixed an incorrect self-service URL in the IDP settings. (VSTOR-101119)

• Decreased the maximum number of snapshots to 32 per volume. (VSTOR-102028)

• Fixed incorrect hypervisor information on compute nodes with similar hostnames. (VSTOR-102694)

• Fixed a UEFI boot failure for VMs with multiple virtIO disks. (VSTOR-102711)

• A security fix for neighbor VMs in the same network. (VSTOR-103381)

• Volumes may be removed from a backup plan when the volume QOS policy is updated. (VSTOR-103429)

• A security fix for the Keystone service. (VSTOR-104443)

• Fixed EPYC CPU model names. (VSTOR-106482)

• A load balancer may get stuck pending updates. (VSTOR-108065)

5. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. A reboot is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• Live migration failed for VMs with both vstorage and iSCSI volumes. (VSTOR-88806)

• Fixed the false-positive alerts “Virtual machine state mismatch” and “Volume attachment details mismatch.” (VSTOR-89155)

• The Backup Gateway service failed to start. (VSTOR-95308)

• Failed to remove an RBAC policy. (VSTOR-96887)

• Fixed the false-positive alert “Volume is stuck in transitional state.” (VSTOR-99600)

• Fixed a false-positive alert on extra vCPU reservation. (VSTOR-100148)

• VMs lose network connectivity after stopping the Neutron Open vSwitch agent. (VSTOR-100168)

• Fixed an issue with the Neutron DHCP service. (VSTOR-100410)

• Failed to delete a VM due to issues with temporary snapshots. (VSTOR-100575)

• Fixed an issue with rebooting nodes after a cluster update. (VSTOR-101702)

• Failed to add a worker to the compute cluster. (VSTOR-101806)

• Virtual DHCP server’s HA degraded during an update. (VSTOR-101892)

• Fixed an issue with updating Kubernetes clusters. (VSTOR-101905)

• Fixed an issue with restarting the Neutron service. (VSTOR-101972)

• Failed to update a node due to relocating domains. (VSTOR-102283)

• The first volume snapshot after resizing has an incorrect size if the VM volume size was specified in MB. (VSTOR-102472)

• Fixed an issue with update notifications in the admin panel. (VSTOR-102849)

• VM backup failed on a VM with a SATA CD-ROM drive. (VSTOR-102912)

• Fixed NUMA balancing for nodes with high memory load. (VSTOR-103516)

• The guest OS failed to boot from a VM’s second disk. (VSTOR-103640)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• Disks may be erroneously marked as ill. (VSTOR-85873)

• Improvements in the garbage collector. (VSTOR-93149, VSTOR-100823)

• Added the volume ID to LUN details. (VSTOR-94512)

• Increased the speed of node fencing and unfencing after uploading a new license. (VSTOR-95095)

• Improved validation of S3 bucket policies. (VSTOR-95955)

• Fixed a deadlock in the Neutron QoS plugin caused by limited database pool. (VSTOR-97105)

• Fixed a degradation in ploop performance. (VSTOR-97840)

• The vstorage-mount process may crash when disabling re-encoding. (VSTOR-97963)

• UI improvements. (VSTOR-97976, VSTOR-98562, VSTOR-98564, VSTOR-101059)

• Fixed I/O failures when reading files from multiple nodes simultaneously. (VSTOR-98159)

• Fixed a false-positive S3 latency alert. (VSTOR-98733)

• Outgoing traffic from a VM to an external network is flooded to other VMs on the same compute node. (VSTOR-98870)

• The S3 service may return the 504 error during deletion requests. (VSTOR-99249)

• Improved physical space usage reporting in the file-stats output. (VSTOR-99389)

• Fixed overflow during chunk splitting for chunks larger than 4 GB. (VSTOR-99689)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a range of new features that cover improvements in the compute service, core and object storage, as well as monitoring and alerting. Additionally, this release delivers stability and security improvements, and addresses issues found in previous releases.

2. New Features

• [Compute service] New guest OS support. Added support for the following guest operating systems:

  • Ubuntu 24.04 LTS

  • Debian 11.x and 12.x

  • CentOS 9.x Stream

  • Oracle Linux 8.x and 9.x with Unbreakable Enterprise Kernel and Red Hat Compatible Kernel

• [Compute service] Support for Kubernetes version 1.31.

• [Core storage] Dynamic chunk allocation when a chunk server is out of space. Enhanced storage behavior by introducing dynamic allocation of a new chunk when the current chunk of a data stream is located on an out-of-space chunk server. This helps to maintain efficient data streaming and reduce the risk of write failures due to exhausted storage.

• [Object storage] Erasure coding redundancy change for object storage. It is possible to change a redundancy scheme for object storage, including the encoding mode, tier, and failure domain. Such a configurable redundancy scheme improves cost-efficiency for object storage in a growing cluster (for example, switching from the 3+2 encoding mode to 7+2 reduces storage overhead by 38%). The re-encoding progress can be monitored on the “Reencoding overview” Grafana dashboard.

• [Monitoring and alerting] Storage space and redundancy warning. Introduced a proactive warning mechanism in core storage that alerts users if a node release or cluster update may result in insufficient storage space or compromised data redundancy. Before initiating an update or releasing a node, the system evaluates the current storage levels and redundancy configurations. If there is a potential lack of storage space or failure domains, a clear warning is displayed to allow users to take corrective actions.

3. Important Notes

• Kubernetes version 1.27 is no longer supported. Kubernetes 1.28 will be deprecated in future releases. Update to the currently supported version 1.29 or newer.

• The HTTP status code for Compute API failures has changed. The HTTP code 502 is now returned instead of 521.

4. Bug Fixes

• A stability fix for the S3 service. (VSTOR-88635)

• A VM created during migration has incorrect instance mapping. (VSTOR-89280)

• Fixed an issue with the application credentials. (VSTOR-92413)

• Improved messaging for increasing a VM volume when the quota is exceeded. (VSTOR-94824)

• Fixed the progress reporting after a backup fails to be uploaded to an external storage. (VSTOR-95741)

• Fixed extending a volume for multipath devices. (VSTOR-95905)

• A stability fix for Backup Gateway. (VSTOR-96883)

5. Known Issues

• VMs are in the error state after a failed live and cold migration attempt. (VSTOR-97170)

6. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• A stability fix for Backup Gateway. (VSTOR-86739)

• Stability fixes for the S3 service. (VSTOR-95704, VSTOR-95706)

• A stability fix for the storage service. (VSTOR-97935)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• Stability fixes for Backup Gateway. (VSTOR-96085, VSTOR-96883)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• Stability fixes for Backup Gateway. (VSTOR-96085, VSTOR-96883)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a stability fix.

2. Bug Fixes

• A stability fix for Backup Gateway. (VSTOR-96085)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a stability fix.

2. Bug Fixes

• A stability fix for Backup Gateway. (VSTOR-96085)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides security fixes.

2. Bug Fixes

• Security fixes for Backup Gateway. (VSTOR-95697, VSTOR-95700)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides security fixes.

2. Bug Fixes

• Security fixes for Backup Gateway. (VSTOR-95697, VSTOR-95700)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides security fixes.

2. Bug Fixes

• Security fixes for Backup Gateway. (VSTOR-95697, VSTOR-95700)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides security fixes.

2. Bug Fixes

• Security fixes for Backup Gateway. (VSTOR-95697, VSTOR-95700)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability and performance improvements.

2. Bug Fixes

• A performance improvement. (VSTOR-91833)

• Increased the number of Grafana dashboards that can be added to the Dashboard Directory. (VSTOR-94382)

• In the admin panel, LUNs are not displayed for a new target group. (VSTOR-94508)

• When a VM is shelved by a host evacuation task, its attached PCI devices are not released. (VSTOR-94519)

• Failed to allocate replicas though there were available chunk services in every failure domain. (VSTOR-94551)

• Stability fixes for the S3 service. (VSTOR-94387, VSTOR-94598)

• Stability fixes for MDS. (VSTOR-94733, VSTOR-94770)

• Fixed in-progress notifications. (VSTOR-87733, VSTOR-94754)

• The Neutron server containers are stopped after retrying to upgrade Kolla Ansible. (VSTOR-94776)

• Added the volume ID to some volume operation logs. (VSTOR-94783)

• Failed to upload a new S3 object after changing a bucket policy. (VSTOR-94806)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update. During the update from version 6.3, nodes will enter maintenance without VM migration.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• In the admin panel, LUNs are not displayed for a new target group. (VSTOR-94508)

• When a VM is shelved by a host evacuation task, its attached PCI devices are not released. (VSTOR-94519)

• Failed to allocate replicas though there were available chunk services in every failure domain. (VSTOR-94551)

• Stability fixes for the S3 service. (VSTOR-94387, VSTOR-94598)

• Stability fixes for MDS. (VSTOR-94733, VSTOR-94770)

• The Neutron server containers are stopped after retrying to upgrade Kolla Ansible. (VSTOR-94776)

• Added the volume ID to some volume operation logs. (VSTOR-94783)

• The storage services do not get priority over VMs in terms of CPU time under a high load. (VSTOR-94796)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• Volume resize fails when the Nova API is not upgraded. (VSTOR-90793)

• A stability fix for the S3 service. (VSTOR-94387)

• When a VM is shelved by a host evacuation task, its attached PCI devices are not released. (VSTOR-94519)

• Failed to allocate replicas though there were available chunk services in every failure domain. (VSTOR-94551)

• Stability fixes for MDS. (VSTOR-94733, VSTOR-94770)

• The Neutron server containers are stopped after retrying to upgrade Kolla Ansible. (VSTOR-94776)

• Added the volume ID to some volume operation logs. (VSTOR-94783)

• The storage services do not get priority over VMs in terms of CPU time under a high load. (VSTOR-94796)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a range of new features that cover the compute service and our ecosystem of backup and disaster recovery solutions. Additionally, this release delivers stability and security improvements, and addresses issues found in previous releases.

2. New Features

• [Compute service] Updated licensing models and screens. Added support for multiple licensing models: lease (pay-as-you-go), annual subscription, and perpetual. The product shows the license type, limits, and current usage of licensed resources.

• [Compute service] External Fibre Channel (FC) storage support. Starting from this release, FC-based external storages with the OpenStack Cinder driver are supported as an experimental feature.

• [Compute service] Q35 virtual machine chipset support. By default, the Q35 virtual chipset will now be used instead of i440fx, to provide better performance for virtual machines and the ability to use thin-provisioned volumes with high-performance volume types.

• [Compute service] Virtuozzo Storage update without VM migration. Decreased a number of updates with maintenance for VM migration by allowing the ability to update the integrated Virtuozzo Storage without downtime.

• [Compute service] Integrated backup: incremental backup support. The integrated backup service supports incremental backups that help to decrease the amount of space needed to store backup files. A system administrator can enable or disable the incremental backup functionality in the cluster settings.

• [Compute service] Using Cilium CNI for Kubernetes by default. Starting from Kubernetes version 1.30, the Cilium CNI will be used as the default Kubernetes network plugin.

• [Compute service] Support for Kubernetes version 1.30.

• [Compute service] New CPU models. Added new CPU models to the hypervisor, to support new CPU generations and provide compatibility between multiple generations for a single cluster.

• [Integrations] New disaster recovery (DR) solutions: Storware Backup and Recovery, and CloudBase Coriolis. To allow customers to provide DR capabilities for their virtual machines and legacy applications, we support multiple third-party DR solutions. In this release, we are adding support for Storware Backup and Recovery, and CloudBase Coriolis, in addition to the already supported solutions.

• [Integrations] Backup solutions: Commvault. Commvault is a very popular backup solution that supports multiple virtualization solutions, including OpenStack. Starting from this release, we also support Commvault as a backup solution for Virtuozzo Hybrid Infrastructure.

• [Integrations] Compatibility with Vertica in Eon Mode. Vertica is a unified analytics data warehouse with a massively scalable architecture. The performed validation tests confirmed compatibility between Vertica in Eon Mode and Virtuozzo Hybrid Infrastructure S3 storage.

3. Important Notes

• Kubernetes version 1.26 is deprecated. Update to the currently supported version 1.27.

4. Bug Fixes

• The DHCP agent fails on networks with the MTU value lower than 1280. (VSTOR-62540)

• Some VMs located on controller nodes lost internet access due to issues with the Neutron L3 agent. (VSTOR-80462)

• Stale cache disks in the database cause issues with listing disks in the admin panel. (VSTOR-82889)

• Unable to delete VMs by using the Nova API. (VSTOR-84273)

• The command ‘vinfra service compute server reset-state’ does not clean up a task state. (VSTOR-86363)

• An inefficient structure of a huge PostgreSQL database may cause the compute API degradation. (VSTOR-86875)

• Fixed an issue with the OpenStack service health check. (VSTOR-88241)

• Unable to switch network access from full to routed if a floating IP exists in this network. (VSTOR-88453)

• Some task statuses are not updated in the admin panel after the primary node change. (VSTOR-89213)

• The command ‘vinfra service compute server create –placements’ does not accept placement names. (VSTOR-89463)

• Failed to cancel a node release after the release of its chunk service was canceled. (VSTOR-89678)

• The Nova and Cinder multipath parameters are not compatible with the Synology storage. (VSTOR-91197)

• Prevented simultaneous volume cloning and uploading to an image in order to avoid locks. (VSTOR-91373)

• Fixed an issue with detaching volumes. (VSTOR-91461)

• The vstorage-mount process may use swap intensively resulting in the I/O slowdown. (VSTOR-91831)

• Unable to create a flavor with more than 64 vCPUs. (VSTOR-92388)

• Unable to create an iSCSI target group in the admin panel due to the “Node has no IP address” error. (VSTOR-93005)

• Improved usage data collection on clusters with over 1000 VMs. (VSTOR-94283)

5. Known Issues

• With the new default Q35 chipset, virtual machines will not boot if they are created from images without the virtio-blk driver installed. To prevent using the Q35 chipset in such cases, an image should have a special property requesting the legacy machine type ‘pc’. You can set this property for an image by using the following command: ‘openstack –insecure image set <image_id> –property hw_machine_type=pc’.

6. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. A reboot is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• Cannot update a cluster due to little free space on the boot partition. (VSTOR-93320)

• During a cluster update, VM live migration may fail with the libvirt error. (VSTOR-93349)

• Fixed detaching CD-ROM drives from VMs. (VSTOR-93365)

• Improved usage data collection on clusters with over 1000 VMs. (VSTOR-94283)

• Stability fixes for the S3 service. (VSTOR-94293, VSTOR-94294)

• Added support for multiple iSCSI targets per node. (VSTOR-91633, VSTOR-92788)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability and security fixes.

2. Bug Fixes

• Fixed an issue with iSCSI persistent reservations. (VSTOR-86581)

• A stability improvement for the compute service. (VSTOR-90084)

• Fixed an error with extending volumes. (VSTOR-90793)

• A security fix for CVE-2024-41090 and CVE-2024-41091. (VSTOR-90465)

• Fixed buffer processing for S3 POST bucket uploads. (VSTOR-93903)

• Fixed an incorrect update status in the admin panel. (VSTOR-93909)

• Improved usage data collection on clusters with over 1000 VMs. (VSTOR-94283)

• Stability fixes for the S3 service. (VSTOR-90379, VSTOR-93908, VSTOR-94293, VSTOR-94294)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides security, stability, and performance fixes.

2. Important Notes

• In this update, Ubuntu 16.04 becomes deprecated and is no longer supported as a guest operating system.

3. Bug Fixes

• Network and disk information is missing in hci_info.disks due to a race. (VSTOR-88709)

• VMs are in the shutoff state after upgrading the libvirt package. (VSTOR-89823)

• An improvement in the QEMU log rotation. (VSTOR-90644)

• Added new metrics for the compute service. (VSTOR-90912)

• Unable to delete a Kubernetes cluster after manually deleting its worker VM and volume. (VSTOR-91070)

• Filtering VMs by ID does not work. (VSTOR-91209)

• Fixed buffer processing for S3 POST bucket uploads. (VSTOR-91448)

• VM creation fails due to the DHCP connectivity checker issues. (VSTOR-91706)

• The S3 account control service may crash after deleting an S3 user and its account. (VSTOR-91718)

• Fixed an issue with ploop overflow that may lead to corruption of images larger than 5 TB. (VSTOR-92189)

• Boosted replication priority for failed chunk services. (VSTOR-92420)

• Unsuccessfully deleted VMs trigger the alerts “Attachment details mismatch” and “State of virtual machine mismatch.” (VSTOR-92564)

• The port checker reports only one DHCP reply instead of two. (VSTOR-92748)

• Deleting a VM during its creation may cause the VM to get stuck in the “Build” status. (VSTOR-92772)

• The vstorage-mount process may use swap intensively resulting in the I/O slowdown. (VSTOR-92776)

4. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides stability and performance improvements, as well as addresses issues found in previous releases.

2. Important Notes

• Kubernetes 1.26 will be deprecated in future releases. Update to the currently supported version 1.27 or newer.

• Oracle Linux 7.3 as a guest operating system will be deprecated in future releases.

3. Bug Fixes

• Failed to deploy the compute cluster due to an issue with the default storage policy. (VSTOR-68405)

• Fixed the false-positive alert “Virtual network port check failed.” (VSTOR-88055)

• Failed to assign a role to a disk due to non-unique disk IDs. (VSTOR-88743)

• Fixed an issue with S3 object listing. (VSTOR-89112)

• Unable to list over 1000 flavors per placement. (VSTOR-89196)

• Fixed an issue with displaying VM details when switching between projects in the self-service panel. (VSTOR-89258)

• Fixed sorting of VMs by status in the admin panel. (VSTOR-89292)

• Fixed an issue with updates for VMs with vGPUs. (VSTOR-89327)

• A stability improvement for compute volume backups. (VSTOR-89723)

• VM migration failed due to an issue with disk information retrieval. (VSTOR-89834)

• A stability improvement for the compute service. (VSTOR-90084)

• Improved handling of VM temporary snapshots. (VSTOR-90195)

• Fixed issues with checks for updates. (VSTOR-88095, VSTOR-88750, VSTOR-89478, VSTOR-89849)

4. Known Issues

• The L2 port provisioning may get stuck for router ports. (VSTOR-87520)

5. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability and performance improvements.

2. Bug Fixes

• A stability fix for the Backup Gateway service. (VSTOR-76224)

• Improved the size calculation of erasure coding files. (VSTOR-81226)

• Decreased the memory consumption by Prometheus. (VSTOR-88511)

• Fixed issues with S3 operations with multipart objects. (VSTOR-88576)

• Fixed an issue with calculating storage usage. (VSTOR-89300)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• A stability and performance improvement for the core storage. (VSTOR-76914)

• Improved the size calculation of erasure coding files. (VSTOR-81226)

• VM live migration failed due to a missing snapshot traceback. (VSTOR-86571)

• Stability fixes for the hypervisor. (VSTOR-87531, VSTOR-89251)

• Fixed an issue with calculating storage usage. (VSTOR-89300)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• VM live migration failed due to a missing snapshot traceback. (VSTOR-86571)

• Stability fixes for the hypervisor. (VSTOR-87531, VSTOR-89251)

• An error is triggered after disabling account replication. (VSTOR-88449)

• Fixed issues with updating Kubernetes clusters. (VSTOR-88554, VSTOR-89057)

• Fixed an issue with calculating storage usage. (VSTOR-89300)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• VM live migration failed due to a missing snapshot traceback. (VSTOR-86571)

• Stability fixes for the hypervisor. (VSTOR-87057, VSTOR-87531, VSTOR-89251)

• Fixed an issue with calculating storage usage. (VSTOR-89300)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides security and stability fixes.

2. Bug Fixes

• Stability fixes for the hypervisor. (VSTOR-75009, VSTOR-76816, VSTOR-87057)

• Fixed an issue with storage space calculation for the “Other” category in the “Logical space” chart in the admin panel. (VSTOR-87588)

• A stability fix for the Neutron service. (VSTOR-87977)

• A security fix for networks. (VSTOR-88832)

• Fixed an issue with missing firewall rules for certain ports. (VSTOR-88987)

• A security fix for CVE-2024-4467. (VSTOR-89010)

• Load balancers are not displayed in the admin panel if one of them is in the error state. (VSTOR-89055)

• Fixed an issue with S3 user authentication via the Amazon Signature Version 4 algorithm. (VSTOR-89106)

• A security fix for CVE-2024-6409. (VSTOR-89156)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides security and stability fixes.

2. Bug Fixes

• Stability fixes for the hypervisor. (VSTOR-75009, VSTOR-76816)

• Stability fixes for the chunk service. (VSTOR-85653, VSTOR-87742)

• A security fix for networks. (VSTOR-88832)

• A security fix for CVE-2024-4467. (VSTOR-89010)

• Fixed an issue with S3 user authentication via the Amazon Signature Version 4 algorithm. (VSTOR-89106)

• A security fix for CVE-2024-6409. (VSTOR-89156)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides security and stability fixes.

2. Bug Fixes

• Stability fixes for the hypervisor. (VSTOR-75009, VSTOR-76816)

• Fixed an issue with delayed file creation on NFS. (VSTOR-86808)

• Fixed a high availability issue with incorrect paths of NFS shares. (VSTOR-88495)

• Decreased the memory consumption by Prometheus. (VSTOR-88511)

• A stability improvement for the Cinder service. (VSTOR-88572)

• Fixed issues with S3 operations with multipart objects. (VSTOR-88576)

• Fixed issues with S3 object listing. (VSTOR-87293, VSTOR-88628)

• A stability fix for the S3 gateway. (VSTOR-88629)

• A security fix for networks. (VSTOR-88832)

• Incorrect storage policy parameters are inherited and applied. (VSTOR-88982)

• A security fix for CVE-2024-4467. (VSTOR-89010)

• Fixed an issue with parsing S3 metrics. (VSTOR-89060)

• A security fix for CVE-2024-6409. (VSTOR-89156)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability and performance fixes.

2. Bug Fixes

• Fixed an issue with missing firewall rules for certain ports. (VSTOR-78110)

• New settings may be missing in the S3 gateway, which blocks access to the S3 user panel. (VSTOR-85979)

• The chunk service journal is not clean and prevents assigning a new role to the disk. (VSTOR-86340)

• Some NFS backups may not be visible in the filesystem due to incorrect timestamps. (VSTOR-86808)

• Fixed a high availability issue with incorrect paths of NFS shares. (VSTOR-87028)

• I/O in the storage mount service may get stuck after a huge number of requests. (VSTOR-88507)

• A stability improvement for the Cinder service. (VSTOR-88572)

• Fixed issues with S3 operations with multipart objects. (VSTOR-88576)

• Errors appear when listing volumes due to incorrect processing of UUIDs. (VSTOR-88623)

• The chunk service failed due to inconsistent writes in the fast write mode. (VSTOR-88626)

• The chunk service checkpoint gets stuck on an empty journal. (VSTOR-88627)

• Fixed issues with S3 object listing. (VSTOR-87293, VSTOR-88628)

• The S3 gateway crashes after a request is aborted with a network error. (VSTOR-88629)

• A non-privileged user cannot delete a volume that has a backup. (VSTOR-88630)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides important security fixes.

2. Bug Fixes

• A security fix for CVE-2024-6387. (VSTOR-88638)

• Other security and stability fixes for OpenSSH.

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides important security fixes.

2. Bug Fixes

• A security fix for CVE-2024-6387. (VSTOR-88638)

• Other security and stability fixes for OpenSSH.

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides important security fixes.

2. Bug Fixes

• A security fix for CVE-2024-6387. (VSTOR-88638)

• Other security and stability fixes for OpenSSH.

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a range of new features that cover the compute service, high availability of the management node, object storage management, networking, and monitoring. Additionally, this release delivers stability improvements and addresses issues found in previous releases.

2. New Features

• [Compute service] Improved Backup and Restore as a Service. Now, with the compute backup service, you have the ability to set quotas for storage space usage and number of backups on external storage systems. Additionally, the newly added statistics for total provisioned and total used storage space for the entire cluster and per project help to improve metering capabilities. Starting from this version, the compute backup service also supports volumes based on external storages such as iSCSI and NFS.

• [Compute service] Simplified performance settings for load balancers. During load balancer creation, self-service users have the possibility to select a load balancer flavor and configure access rules based on allowed network CIDR ranges. System administrators can create as many load balancer flavors as required.

• [Compute service] Cilium CNI support for Kubernetes version 1.29. Self-service users can use the Cilium network plugin, instead of the default Flannel CNI, for Kubernetes clusters with version 1.29. In this release, the Cilium CNI support is an experimental feature, which is not intended for use in production environments. Starting from the next release, all new Kubernetes versions will be switched to the Cilium CNI by default.

• [Compute service] Update of the load balancer image to Ubuntu 22.04 and haproxy 2.4.

• [Compute service] In-place upgrade and repair of Windows virtual machines. Added the ability to perform in-place updates of Windows guest operating systems according to the Microsoft recommendations. This can be used to upgrade and repair virtual machines.

• [Management node high availability] Primary management node replacement. It is now possible to change the primary management node in the high availability configuration in the user or command-line interface.

• [Object storage] Object storage management in the self-service portal. Self-service users have the ability to manage S3 credentials, S3 objects, and properties in the self-service panel, previously used only for compute resource management.

• [Networking] IPv6 support for node network interfaces. Cluster networking can be configured to use mixed IPv6 and IPv4 addresses for more efficient IP packet processing and non-limited IP addressing.

• [Monitoring] Virtual DHCP connectivity checks. Added a new metric to integrated Prometheus, to show availability of the virtual DHCP servers in the compute cluster.

• [Monitoring] Log forwarding with Filebeat. With the built-in Filebeat service, it is now possible to send logs to any external log analysis system.

3. Important Notes

• Ubuntu 16.04 as a guest operating system will be deprecated in future releases.

4. Bug Fixes

• Only nodes in the HA configuration should report the HA services. (VSTOR-45749)

• Failed to clean up backup slices after promoting the secondary cluster to primary. (VSTOR-56264)

• Compute reconfiguration failed after changes in the HA configuration. (VSTOR-61703)

• Improved message logging for the MDS Paxos consensus algorithm. (VSTOR-74942)

• Added status tracking for the compute service configuration tasks. (VSTOR-77524)

• Improved stability of the bulk file delete operation. (VSTOR-78567)

• Fixed false-positive alerts on high request error rates during an update. (VSTOR-83747)

• When creating a VM in the self-service panel, the default storage policy is not applied. (VSTOR-84265)

• Fixed adding new members to load balancer pools that were created bypassing the backend API. (VSTOR-84508)

• Some task statuses are not updated in the admin panel after the primary node change. (VSTOR-84752)

• Fixed a memory leak in the S3 service. (VSTOR-85081)

• Improved message logging and error handling for FUSE. (VSTOR-85086)

• Increased the inotify limits for Kubernetes. (VSTOR-85254)

• Improved NFS performance by changing the client default configuration. (VSTOR-85296)

• A stability fix for PCI devices. (VSTOR-85617)

• The chrony package was not installed due to connection issues. (VSTOR-85849)

• Fixed pagination for cases with more than 1000 flavors. (VSTOR-85978)

• A stability improvement for the Cinder service. (VSTOR-86331)

• Errors appear when listing volumes due to incorrect processing of UUIDs. (VSTOR-86365)

• Fixed fencing alerts. (VSTOR-86399)

• Prevented the storage version from setting to zero. (VSTOR-86429)

• Improved checks of spectre mitigation when choosing compute CPU models. (VSTOR-86448)

• A stability fix for MDS. (VSTOR-86452)

• OVS interfaces are removed from the management node database if they are down. (VSTOR-86491)

• Improved protection of user passwords. (VSTOR-86548)

• Improved kernel diagnostics via sysrq. (VSTOR-86633)

• logrotate is not enabled on some clusters. (VSTOR-86877)

• Limited the space consumption by crash reports on hosts without internet access. (VSTOR-86950)

• Fixed an incorrect update status in the admin panel. (VSTOR-87330)

• Enabled adding one volume to multiple backup plans. (VSTOR-87464)

5. Known Issues

• During the update, you may receive false-positive alerts. Please wait until the update installation is complete, as the raised alerts will be cleared automatically. (VSTOR-67373)

• An inefficient structure of a huge PostgreSQL database may cause the compute API degradation. (VSTOR-86875)

6. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. A reboot is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a stability improvement.

2. Bug Fixes

• Enabled adding multiple devices to the boot sequence of Linux VMs. (VSTOR-85986)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a stability improvement.

2. Bug Fixes

• A stability fix for Backup Gateway. (VSTOR-85872)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability and performance improvements.

2. Bug Fixes

• Improvements in certificate eligibility checks. (VSTOR-80766, VSTOR-81600, VSTOR-85345)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a stability improvement.

2. Bug Fixes

• A stability fix for Backup Gateway. (VSTOR-86420)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure enables virtual CPU and RAM overcommitment per node, as well as provides stability and performance improvements, and addresses issues found in previous releases.

2. New Features

• [Compute service] Flexible virtual CPU and RAM overcommitment. Added the possibility to set the virtual CPU and memory overcommitment ratio per node. System administrators are now able to configure different overcommitment levels that can serve different types of workloads for each node in the compute cluster.

3. Bug Fixes

• Network errors occur when migrating a VM that was previously released from its security group. (VSTOR-49565)

• Disk assignment is stuck on a failed disk. (VSTOR-75742)

• Failed to resize a disk of a Kubernetes VM under a high load. (VSTOR-76058)

• Unable to detach a volume while cloning it. (VSTOR-80734)

• Domain administrators cannot list projects and groups for their own domain users. (VSTOR-82861)

• Incorrect S3 storage size is displayed in the admin panel. (VSTOR-82918)

• Fixed an issue with disks’ identical GPT UUIDs. (VSTOR-83126)

• Incorrect storage policy parameters are inherited and applied (VSTOR-83149)

• Using an incorrect URL path for metadata may result in the 500 HTTP error for the Nova API. (VSTOR-83673)

• Failed to retry upgrading a single-master Kubernetes cluster with insufficient quotas for temporary master nodes. (VSTOR-83678)

• The “Backend task state” dashboard does not show when a task was completed. (VSTOR-83687)

• Unable to add a node to a cluster if the node interfaces have a low speed. (VSTOR-83812)

• Added alerts for the expiration of the management panel SSL certificates. (VSTOR-84766)

• Assigning a storage disk timed out. (VSTOR-85229)

• Fixed an issue with ploop overflow that may lead to corruption of images larger than 2 TB. (VSTOR-85428)

• Stability improvements for compute volume backups. (VSTOR-83777, VSTOR-84356, VSTOR-84686, VSTOR-84949)

4. Known Issues

• IPMI Remote Console may stop responding after updating a node to 6.1. In this case, you can reboot the node to fix it. (VSTOR-84303)

5. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a stability improvement.

2. Bug Fixes

• Fixed an issue with ploop overflow that may lead to corruption of images larger than 2 TB. (VSTOR-85582)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a stability improvement.

2. Bug Fixes

• Fixed iSCSI persistent reservations. (VSTOR-84827)

3. Known Issues

• If an iSCSI persistent reservation already exists, the update may fail on some nodes due to inability to restart the iSCSI kernel module. In this case, please contact the technical support to assist you with the manual update. (VSTOR-84827)

4. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability improvements.

2. Bug Fixes

• Fixed iSCSI persistent reservations. (VSTOR-84476)

• Load balancer members get the “Unhealthy” status after upgrading from 6.0 to 6.1. (VSTOR-84499)

• Fixed a memory issue for NFS clusters with more than 15 nodes. (VSTOR-84646)

3. Known Issues

• If an iSCSI persistent reservation already exists, the update may fail on some nodes due to inability to restart the iSCSI kernel module. In this case, please contact the technical support to assist you with the manual update. (VSTOR-84476)

4. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Placing nodes in the maintenance mode is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure enables selective updates of specific Kubernetes node groups, as well as provides stability and performance improvements.

2. New Features

• [Compute service] Selective worker group updates for Kubernetes. Now, users can select specific Kubernetes worker groups for updating the Kubernetes version. This decreases the required maintenance window for applications running inside Kubernetes, as well as makes the update process more stable.

3. Bug Fixes

• Cannot filter backup plans by using the “Disabled” status. (VSTOR-83526)

• Added Grafana dashboards for the nginx metrics. (VSTOR-83662)

• Provided more system metadata for S3 requests. (VSTOR-83728)

• Fixed an RDMA issue with the splice buffer. (VSTOR-83964)

• The pre-update checks fail with the error “internal endpoint for container service was not found.” (VSTOR-83986)

• The software update error was not reset after retrying. (VSTOR-84007)

• Backup plans with the “Disabled” status are not displayed in the admin panel. (VSTOR-84267)

• Decreased the period of a database cleanup. (VSTOR-84366)

• The license expiration date is not displayed correctly. (VSTOR-84431)

4. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure introduces a new service—Backup and Restore as a Service—as well as provides a range of new features that cover improvements in the compute services and object storage. Additionally, this release delivers stability and security improvements, and addresses issues found in previous releases.

2. New Features

• [Compute service] Integrated Backup and Restore as a Service. The new backup service allows you to back up VM volumes, and then restore virtual machines and volumes from them. This helps to prevent data loss and mitigate issues with software or hardware. The service supports external and integrated storage (NFS and Object Storage) as a backup destination, thus eliminating the need for purchasing an external backup solution and decreasing the product TCO.

• [Compute service] New features for load balancers. Added support for the HTTP headers, PROXY protocol, TLS, and certificate upload for the load balancing service.

• [Compute service] External iSCSI storage support. Starting from this release, the compute service supports any external iSCSI storage system that has the OpenStack Cinder driver. You can find the list of available iSCSI drivers at https://docs.openstack.org/cinder/xena/reference/support-matrix.html.

• [Compute service] Support for new Kubernetes versions: 1.26, 1.27, 1.28. Starting from this release, the Kubernetes release support policy will be the following:

  • We support only the four latest minor versions. For example: 1.28, 1.27, 1.26, and 1.25.

  • We support only the latest patch for the supported minor version.

  • We provide support for a new minor version during a six-month period after the upstream release.

• [Compute service] Baseline CPU model per node. To combine multiple generations of the same CPU vendor, you need to set the baseline CPU model based on the oldest generation, to make all CPUs compatible with each other. Previously available only for the entire compute cluster, the baseline CPU model now can be set on the per-node basis. Thus, you can have multiple sets of CPU generations in a single cluster covered by multiple CPU models.

• [Compute service] Improved domain quota management. Now, you can set domain quotas for vCPUs, RAM, and storage policy space in the admin panel.

• [Compute service] Improved monitoring for virtual machines. The new monitoring charts available in the admin and self-service panels show separate metrics for each VM volume and network interface.

• [Compute service] SSL protocol support for Kafka connection. Added the possibility to configure the SSL protocol for Kafka connection, to secure message transfer between your cluster and metering solution. SSL can be configured for encryption and also serves as two-way authentication between the Kafka server and client.

• [Compute service] New guest OS support. Added support for SUSE Linux Enterprise 15 (SP3, SP4, SP5) as a guest operating system.

• [Object storage] Performance improvements. Added the possibility to place NS and OS journals on a faster storage tier than is used for data, to improve S3 storage performance.

3. Bug Fixes

• Introduced partially synchronous writes of memory cache limits to catch potential errors at an early stage. (VSTOR-59718)

• Creating a snapshot may get blocked by the process of deleting another snapshot. (VSTOR-61552)

• Increased the speed of volume resize operations. (VSTOR-61692)

• Fixed an issue with the IPsec bypass rules. (VSTOR-66435)

• Add recurrent tasks for handling snapshots that were not deleted completely. (VSTOR-74476)

• A snapshot is created incorrectly if the previous top snapshot was not removed completely. (VSTOR-74824)

• Improvements in the email notification configuration. (VSTOR-75647, VSTOR-79808)

• After a failed attempt to release a node from the backup storage, the retry is not requested until the node is back online. (VSTOR-75699)

• A cluster node crashed due to a race condition. (VSTOR-76384)

• Created a log record for a load balancer moving into the pending state. (VSTOR-76628)

• Live migration failed after aborting the blockcommit job. (VSTOR-76813)

• The chunk service in the direct_io mode fails on drives with 4k sectors. (VSTOR-77130)

• The admin panel shows the IP address for a domain if the DNS name is configured for the compute API. (VSTOR-77131)

• A storage policy name cannot be changed in the admin panel if it has a space at the end. (VSTOR-78315)

• NFS container archive validation may fail. (VSTOR-78479)

• A stability fix for the chunk service journal. (VSTOR-78664)

• Degradation of write speed to the backup storage with the Amazon S3 destination on high-speed connections. (VSTOR-79332)

• A virtual machine may get stuck in the shelving status. (VSTOR-79378)

• Fixed the filter value in the Neutron service log. (VSTOR-79494)

• A network interface may go offline after changes in its parameters. (VSTOR-79909)

• An inactive event loop in the S3 account control service. (VSTOR-79981)

• The S3 gateway crashes when trying to generate too many access keys. (VSTOR-80092)

• A stability improvement for the kernel updates. (VSTOR-80323)

• Irrelevant nodes are mentioned in the S3 service alerts. (VSTOR-80743)

• Improved the size calculation of erasure coding files. (VSTOR-81226)

• Some geo-replication metrics may drop below zero and cause an S3 service failure. (VSTOR-81326)

• Changing properties of an interface with VLANs results in the loss of dependent routes. (VSTOR-81343)

• Fixed an issue with incorrect trap names in the Zabbix template. (VSTOR-81530)

• Improved parsing options for commas in vinfra. (VSTOR-82493)

• Listing domain users fails if an admin user has locked IP addresses. (VSTOR-82506)

• Cluster total space increases after the chunk service restart. (VSTOR-82639)

• Fixed an incorrect subnet value in the documentation. (VSTOR-82983)

• iSCSI volumes may stop responding if moving to the Standby mode was not completed before setting the Active path. (VSTOR-83102)

4. Known Issues

• A stability issue with RDMA under a high load. If you use RDMA, please wait for the next update in order to update the cluster without any issues. (VSTOR-83964)

• Domain storage policy quotas are not validated during the creation of a Kubernetes cluster. (VSTOR-81220)

• The cluster is not available via the virtual IP address after a failover during the HA reconfiguration. (VSTOR-82626)

• The “Nodes” tab is not displayed properly after creating target groups with several volumes. (VSTOR-83316)

• Cannot select multiple times per day in the backup plan schedule. (VSTOR-83416)

• Failed to retry upgrading a single-master Kubernetes cluster with insufficient quotas for temporary master nodes. (VSTOR-83678)

• The “Backend task state” dashboard does not show when the task was completed. (VSTOR-83687)

5. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. A reboot is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability improvements.

2. Bug Fixes

• A stability fix for iSCSI targets. (VSTOR-70238)

• ISCSI volumes may become unavailable due to a race between switching to standby mode and revoking volumes. (VSTOR-83102)

• Failed to migrate Windows EFI VMs after restarting the libvirtd service. (VSTOR-83744)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATES section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability improvements.

2. Bug Fixes

• Deploying a Kubernetes cluster may take longer than expected. (VSTOR-82695)

• Restarting libvirtd causes EFI VMs to reboot. (VSTOR-82730)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability improvements.

2. Bug Fixes

• Snapshot creation for volumes stored on external NFS may fail under certain circumstances. (VSTOR-80869)

• Some requests to the S3 service may fail with the 504 HTTP error. (VSTOR-81489)

• Fixed issues with updating the storage policy after a node crash. (VSTOR-81846)

• Stability fixes for libvirt. (VSTOR-82127, VSTOR-82256)

• Live migration failed due to a volume stuck in the attaching state. (VSTOR-82309)

• Removing a volume with the ‘Error deleting’ status fails with the error ‘Volume status must be available…’ (VSTOR-82372)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. Neither a reboot nor maintenance is required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability and performance improvements.

2. Bug Fixes

• Increased the speed of VM filtering in clusters with a huge number of existing projects. (VSTOR-72592)

• Parts of a multipart object are not deleted. (VSTOR-79462)

• Fixed issues related to deleting snapshots. (VSTOR-79650, VSTOR-80493)

• A stability fix in the kernel for clusters with RDMA connection. (VSTOR-79838)

• For S3 objects uploaded by using multipart upload, replacing one object with another with the same name leaves some files orphaned. (VSTOR-79881)

• The compute cluster is not updated correctly after updating to 6.0.1 without the management panel. (VSTOR-80262)

• Unable to create a Kubernetes cluster in a VLAN compute network. (VSTOR-80316)

• Fixed search for nested projects in the ‘Projects and domains’ filter. (VSTOR-80490)

• Improved performance for S3 long uploads. (VSTOR-80833)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. Maintenance is required.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability and performance improvements.

2. Bug Fixes

• Reworked eligibility checks for third-party packages. (VSTOR-79658, VSTOR-80254)

• For S3 objects uploaded by using multipart upload, replacing one object with another with the same name may leave some parts orphaned. (VSTOR-79881)

• Failed to automatically regenerate agent certificates. (VSTOR-80494)

• Fixed the hardware validation check that prevents an update of Virtuozzo Hybrid Infrastructure inside a Hyper-V virtual machine. (VSTOR-80828)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update. Maintenance is not required.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a range of new features that cover improvements in the compute service, object storage, alerts and monitoring. Additionally, this release delivers stability and security improvements, and addresses issues found in previous releases.

2. New Features

• [Compute service] OpenStack Networking improvement. Added the possibility to detach specific TCP ports from one VM to another by using the standard API.

• [Compute service] Autoscaling to zero for Kubernetes. For the supported versions of Kubernetes and Autoscaler, it is now possible to downsize Kubernetes worker groups to zero nodes, instead of one node.

• [Compute service] Support for an upgrade to Kubernetes version 1.25.

• [Compute service] More supported guest operating systems. Added support for the latest versions of Rocky Linux 9, AlmaLinux 9, Red Hat Enterprise Linux 9, and Ubuntu 22.04.

• [Compute service] Compute service update improvement. Starting from the next update, the OpenStack components will be updated while a node is in the maintenance mode, not at the end of the update process.

• [Compute service] Domain quotas support. Quotas for vCPUs, RAM, storage policy space can now be set on the domain level. It is also possible to enable nested quota validation.

• [Compute service] Host gateway mode for Kubernetes clusters connected to a private network. Starting from this release, all new Kubernetes clusters connected to a private network will use the Flannel host-gw mode by default.

• [Object storage] New CORS options. A system administrator can now configure the default CORS behavior to either disable or enable all cross-origin resource sharing configurations for a bucket, if no other CORS policy is specified.

• [Object storage] Introduced checks for free storage space. To prevent S3 data from occupying all space in the storage cluster, the S3 service now has a limit on storage space usage.

• [Object storage] Added storage quotas for S3 users and buckets. Now, you can set, query, and delete storage quotas for S3 users and buckets by using the S3 command-line tool.

• [Object storage] Improved bucket notification messaging and SNS compatibility. Added notifications for bucket replication events.

• [Object storage] Configurable number of S3 gateways per node. It is now possible to permanently change the number of S3 gateway services running on each node. This can significantly improve the overall S3 storage performance in clusters with hardware capable of higher storage throughput. The default number of gateways is set to 4 for new deployments.

• [Security] Improved user authentication with external identity providers. Added the SSL certificate validation option and possibility to change the authentication timeout by using the vinfra tool.

• [Alerts and monitoring] New metrics for object storage. Added metrics for recurring errors in RPC communications between the object storage services. The new metrics help improve and simplify troubleshooting by monitoring RPC communication issues.

• [Alerts and monitoring] Alerts for failed system disks. Added alerts to notify about a system disk failure by using the S.M.A.R.T. metrics.

• [Alerts and monitoring] License expiration alerts. Added reminders about license expiration in 21 and 7 days.

3. Bug Fixes

• The Gnocchi service gets stuck with zero-size files. (VSTOR-55676)

• Unable to disable the security setting in the SMTP configuration of email notifications. (VSTOR-61439)

• Unable to re-add a node to the compute cluster if it was removed in the fenced state from the compute cluster. (VSTOR-73088)

• Unable to update a Kubernetes cluster after changing a storage policy name. (VSTOR-74391)

• Unable to create a Kubernetes cluster if the SSH public key has unexpected symbols. (VSTOR-74880)

• Fixed volume detachment caused by duplicate Block Device Mapping (BDM) records. (VSTOR-74908)

• Notify the kernel about changes in a block device’s partition table. (VSTOR-75602)

• Unable to resize a VM disk by using the VirtIO-SCSI protocol under high load. (VSTOR-76058)

• Unable to upgrade a Kubernetes cluster if all master nodes are in the NotReady state. (VSTOR-76226)

• Fixed floating IP attachment to load balancers. (VSTOR-76381, VSTOR-76970)

• Cannot select a node with a soft placement for migrating a VM without a placement in the admin panel. (VSTOR-77100)

• Unable to stop a backup export after the nova-compute service restart. (VSTOR-77123)

• An incorrect storage policy may be assigned when cloning volumes. (VSTOR-77622)

• Recreation of the neutron-openvswitch-agent container leads to deactivation of the hypervisor’s bond interfaces. (VSTOR-77875)

• The host binding values of the router gateway and SNAT ports should be consistent with the active router node. (VSTOR-79503)

• Important stability and performance improvements for the backup storage, core storage, and compute services. (VSTOR-75891, VSTOR-76190, VSTOR-76224, VSTOR-76914, VSTOR-76940, VSTOR-77127, VSTOR-78361)

4. Known Issues

• During the update, you may receive false-positive alerts. Please wait until the update installation is complete, as the raised alerts will be cleared automatically. (VSTOR-67373)

• A VPN connection may be down after the router gets into the split-brain state. (VSTOR-79576)

5. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update. Maintenance is required.

The source of this advisory is available in the JSON file.

1. Overview

This update provides important stability fixes.

2. Bug Fixes

• Prometheus does not show network traffic for the storage interface if RDMA is enabled. (VSTOR-59380)

• A stability fix for the hypervisor. (VSTOR-76816)

• Reading erasure coding files over RDMA may get stuck on rare occasions. (VSTOR-78893)

• A metadata journal for erasure coding files may get corrupted on rare occasions. (VSTOR-79057)

• Unable to install the VirtIO network driver in Windows Server 2019 (German Edition). (VSTOR-79143)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. Maintenance is required.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability and performance improvements.

2. Bug Fixes

• Performance improvements in the Cinder service in huge clusters. (VSTOR-77435, VSTOR-77436)

• Prevented installation of packages that were not downloaded completely. (VSTOR-78255)

• Improved upgrade eligibility checks. (VSTOR-78366, VSTOR-78633)

• Improved stability of an upgrade to 6.0. (VSTOR-78650, VSTOR-78916, VSTOR-78935, VSTOR-78950, VSTOR-79056, VSTOR-79058)

• A metadata journal for erasure coding files may get corrupted on rare occasions. (VSTOR-79057)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. Maintenance is required.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides an upgrade of the Linux distribution, kernel, and toolset packages. This release also contains a range of new features that cover storage performance, object storage, as well as monitoring and alerts. Additionally, this release delivers stability improvements and addresses issues found in previous releases.

2. New Features

• [Operating system upgrade] Rebase to Linux kernel 5.14. Virtuozzo Hybrid Infrastructure now runs on Linux kernel 5.14 with newer distribution tools and packages.

• [Operating system upgrade] Updated hardware support. With the new kernel version, the product becomes compatible with all modern hardware platforms, adapters, and drivers.

• [Operating system upgrade] Enhanced security. The upgrade includes all security updates and resolutions of security issues for major vulnerabilities found by the Linux community.

• [Compute service] Significantly increased the speed of VM live migration.

• [Object storage] Compatibility with Simple Notification Service (SNS) messaging. Now, the object storage service can be configured to send notifications and event data to a remote AMQP, Kafka, or generic HTTP server.

• [Alerts and monitoring] Reworked compute service monitoring. The Grafana dashboards for the compute services have been reworked to monitor service degradation.

• [Core storage] Erasure coding performance boost. Improved performance of the erasure coding algorithm by disabling the default offload to a separate thread. Additionally, this improvement offers higher performance for Intel CPUs that use the Advanced Vector Extensions 512-bit (AVX-512) instruction set automatically.

3. Important Notes

• To be able to update your cluster without service downtime, your hardware must be supported. Virtuozzo Hybrid Infrastructure with the new kernel works on the same hardware that is recommended for Red Hat Enterprise Linux. Ensure that the hardware you are using or going to use has the required certification for Red Hat Enterprise Linux 9.

• Starting from this release, Virtuozzo Hybrid Infrastructure introduces a limit of 150 snapshots per volume, to prevent issues with virtual machines (VSTOR-73972). If you exceed this limit, the upgrade eligibility check shows the problem ‘Maximum snapshots count per volume is 150.’ To proceed with the upgrade, you need to delete extra snapshots.

• If you are using an SSH client for Windows, the SSH connection to hardware nodes may fail with the error ‘Server refused public-key signature despite accepting key!’ after an upgrade to version 6.0. In this case, please try updating your SSH client.

4. Bug Fixes

• The validation error for adding nodes to the compute cluster contains no details. (VSTOR-46205)

• A cluster update fails when the shaman service has been suspended twice with the same token. (VSTOR-49249)

• Cannot detach or delete volumes in the reserved state. (VSTOR-58104)

• A disk is shown as releasing in the admin panel after a forced cancel of the release task in the command-line interface. (VSTOR-59834)

• The OpenStack command ‘server list’ does not show flavor information. (VSTOR-59878)

• Reworked the ‘OpenStack service API is down’ alert and added missing services, such as Glance, to the ‘Compute service status’ Grafana dashboard. (VSTOR-61525)

• Fixed a false-positive alert that appears when the journal size exceeds the recommended value. (VSTOR-61840)

• Reworked the ‘Image uploading’ permission so that self-service users can delete images. (VSTOR-64248)

• Deleting high availability router ports should be prohibited. (VSTOR-65144)

• Fixed the false-positive alert ‘S3 Gateway service has high cancel request rate.’ (VSTOR-67027)

• For security reasons, newly created Kubernetes worker groups now use an internal IP address instead of a floating IP address. Existing worker groups need to be recreated to apply this fix. (VSTOR-67925)

• A crash may occur in the iSCSI kernel module. (VSTOR-68776)

• The error message for deleting an RBAC policy is unclear. (VSTOR-69748)

• Improved error messages for volume snapshot creation and resize when backup export is in progress. (VSTOR-69852, VSTOR-72447)

• The RabbitMQ DNS records are not cleaned up after removing a node from the high availability configuration. (VSTOR-70432)

• Backup storage geo-replication may not work as expected. (VSTOR-70531)

• After assigning the NFS traffic type to a network, the NFS service is not accessible on ports 111 and 892. (VSTOR-70629)

• The Backup Gateway service may get stuck during a shutdown. (VSTOR-70897)

• Kubernetes labels do not support values in quotes. (VSTOR-73315)

• There is no alert for database backup issues if high availability is configured and the database is corrupted. (VSTOR-73448)

• A load balancer may get stuck in the pending state after a disaster during an automatic failover. (VSTOR-74138)

• Open vSwitch can reset the Octavia interface MTU to a bridge minimum value, which may lead to different load balancer issues. (VSTOR-74224)

• In some cases, the network connectivity issues alert may be missing. (VSTOR-74569)

• The ‘Assign floating IP address’ dialog may show an incorrect list of virtual machines and load balancers. (VSTOR-74959)

• The command output for ‘vinfra service compute floatingip show’ does not show server name and ID. (VSTOR-74963)

• Cannot change the storage policy of a CD/DVD volume in the management panel during a VM creation. (VSTOR-76042)

• After renaming a domain, cannot create a VM in the self-service panel. (VSTOR-76913)

5. Known Issues

• During the update, you may receive false-positive alerts. Please wait until the update installation is complete, as the raised alerts will be cleared automatically. (VSTOR-67373)

• It is possible to use SMR and standard disks in the same tier. (VSTOR-67544)

• Changing the compute and high availability configuration is prohibited in a partially upgraded cluster. If you want to perform this operation, please plan it before or after the upgrade. (VSTOR-75839)

• VM live migration is not possible from a node with version 6.0 to a node with version 5.4. (VSTOR-75277)

• A virtual machine with Windows Server does not boot if Hyper-V is installed on it. (VSTOR-77901)

6. Installing the Update

You can upgrade Virtuozzo Hybrid Infrastructure 5.4 to 6.0 in the SETTINGS > UPDATES section of the admin panel. A reboot is required to obtain this update. Note that this release is rolled out gradually to different locations, not to all at once.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability and performance improvements.

2. Bug Fixes

• Cannot download updates if some incompatible legacy packages are installed. (VSTOR-77889)

• Nginx cannot start after an update due to a legacy certificate format. (VSTOR-77910)

• Performance improvement for VM live migration. (VSTOR-75705)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update. Maintenance is not required.

The source of this advisory is available in the JSON file.

1. Overview

This update provides security, stability, and performance improvements.

2. Bug Fixes

• A security fix for CVE-2023-23583 in microcode. (VSTOR-77769)

• Unable to remove a volume with a specific ‘updated_at’ value. (VSTOR-74652)

• When libvirt is unavailable, its help processes should be properly terminated. (VSTOR-76882)

• Fixed a false-positive result of the hardware compatibility check. (VSTOR-77014)

• Fixed an update issue related to modifying a hostname. (VSTOR-77015)

• Performance improvements in the Cinder, Neutron, and Nova services in huge clusters. (VSTOR-77269, VSTOR-77432)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update. Maintenance is not required.

The source of this advisory is available in the JSON file.

1. Overview

This update provides important stability, security, and performance improvements.

2. Bug Fixes

• Fixed a critical security vulnerability. (VSTOR-75357)

• Fixed a problem that may occur while closing files with erasure coding. (VSTOR-76306)

• Add the image.size metric to Ceilometer. (VSTOR-76257)

• Unable to connect to RabbitMQ by using rabbitmqctl because all of the required ports are already occupied. (VSTOR-76059)

• The check for updates can be run on a cluster that failed to upgrade. (VSTOR-75882)

• Fixed an issue with replication timeouts missed in 5.4 Update 4. (VSTOR-75840)

• Cannot cancel the update task for a rebooting node. (VSTOR-75553)

• The check for updates hangs after adding a new node. (VSTOR-72603)

• A load balancer may stop passing traffic through due to a race condition. (VSTOR-75027, VSTOR-75744)

• Stability and performance improvements. (VSTOR-76017, VSTOR-74132)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update. Maintenance is required.

The source of this advisory is available in the JSON file.

1. Overview

This update provides an important security fix.

2. Bug Fixes

• Fixed a critical security vulnerability. (VSTOR-75357)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update. Maintenance is required.

The source of this advisory is available in the JSON file.

1. Overview

This update provides important security and stability fixes.

2. Bug Fixes

• Fixed a critical security vulnerability. (VSTOR-75357)

• Fixed a problem that occurs while opening backup archives with erasure coding. (VSTOR-60071)

• The core storage crashed due to a single file with chunk metadata corruption. (VSTOR-58571)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides an important security fix.

2. Bug Fixes

• Fixed a critical security vulnerability. (VSTOR-75357)

3. Obtaining the Release

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides an important security fix.

2. Bug Fixes

• Fixed a critical security vulnerability. (VSTOR-75357)

3. Obtaining the Release

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides important stability fixes for the core storage, object storage, and compute services.

2. Bug Fixes

• Fixed the customization of S3 URLs with CNAME records. (VSTOR-74982)

• Fixed storage and metadata service issues related to incorrect permissions and database entries after node reinstallation. (VSTOR-75137, VSTOR-75225)

• The nova-compute service may not start on some nodes after an update to version 5.4 Update 4. (VSTOR-75528)

• Important stability improvements for the core storage and object storage services. (VSTOR-73499, VSTOR-74992)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update. Maintenance is required.

The new and updated packages are listed in the JSON file.

1. Overview

This update delivers a new feature for the compute service, performance optimization for the object storage, as well as stability, security, and performance improvements.

2. New Features

• [Compute service] Support for application credentials in the compute API. With application credentials (which are a secret key), external applications can access the OpenStack API without using password-based authentication.

3. Important Notes

• Starting from the next major release, Virtuozzo Hybrid Infrastructure will run on Linux kernel 5.x. To be able to update your cluster without service downtime, your hardware must be supported. Before the update, manually run the hardware compatibility check command-line tool, to ensure that your nodes have no unsupported hardware adapters.

• Starting from this release, external enterprise-grade NAS appliances can be attached to virtual machines as NFS shares and used in production environments.

4. Bug Fixes

• VMs with Windows Server 2019, Windows Server 2022, and Windows 10 fail to boot after installation of the security update KB5030214. (VSTOR-74916)

• High memory consumption by the monitoring service. (VSTOR-74655)

• During an update, a node may get stuck in the rebooting state. (VSTOR-74331)

• A virtual machine with an external PureStorage volume may experience issues after evacuation. (VSTOR-74223)

• The Nova API may stop working if all nodes in the HA configuration were replaced after a compute update failure. (VSTOR-73935)

• A VM creation fails if a project has no quota assigned to a single placement. (VSTOR-73880)

• Impossible to release an iSCSI target in the admin panel. (VSTOR-73687)

• Fixed a critical security vulnerability in a system package. (VSTOR-73243)

• Removed unnecessary alerts for VMs in the ERROR state. (VSTOR-72955)

• After a reboot, a node may drop all traffic due to Open vSwitch issues. (VSTOR-71760)

• Incomplete migration may fail with the error ‘Unable to update attachment. (Invalid volume: duplicate connectors detected on volume …)’ (VSTOR-71375)

• Infrastructure networks are not displayed when trying to create a physical compute network in a cluster with more than 100 nodes. (VSTOR-70804)

• After a node deployment, the following false-positive alert appears in the node details: ‘Some disks stop responding and degrade the cluster performance. The disks are isolated from the cluster I/O. To troubleshoot the problem, check the disk connectivity, S.M.A.R.T. status, and dmesg output on the node.’ (VSTOR-70760)

• After three consequent crashes, the shaman service moves to the suspended state and needs to be resumed manually once the problem is resolved. (VSTOR-70746)

• Fixed domain filtering in the admin panel. (VSTOR-70590)

• Monitoring data may be missing on dashboards in the admin panel. (VSTOR-69370)

• Important stability and performance improvements for the core storage and compute services. (VSTOR-73217, VSTOR-70706, VSTOR-70592, VSTOR-69798)

5. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update. Maintenance is required.

The new and updated packages are listed in the JSON file.

1. Overview

This update provides important fixes for the core storage and object storage services.

2. Bug Fixes

• After updating an expired license, some virtual machines continue to be stuck. (VSTOR-73165)

• The MDS service may get overloaded by clients. (VSTOR-72936)

• Fixed an issue with replication timeouts. (VSTOR-72151)

• Multipart file upload works for a bucket if it has a policy that restricts uploading files. (VSTOR-71624)

• Stability fixes for the object storage. (VSTOR-48167, VSTOR-70642)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update. Maintenance is required.

The new and updated packages are listed in the JSON file.

1. Overview

This update provides important security fixes.

2. Bug Fixes

• Fixes for three high-severity and six medium-severity security vulnerabilities. (VSTOR-71357)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update. Maintenance is not required.

The new and updated packages are listed in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a range of new features that cover core storage, the system configuration, updates, documentation, and the compute services. Additionally, this release delivers stability improvements and addresses issues found in previous releases.

2. New Features

• [Compute service] Support for a clean installation of Kubernetes version 1.25.

• [Core storage] Node recovery. Added the possibility to recover a system disk and stored data after a system disk failure by reinstalling Virtuozzo Hybrid Infrastructure from an ISO image.

• [Core storage] Improved memory consumption of the metadata service for large clusters. The metadata service has been optimized to reduce RAM usage in very large clusters by approximately 50% in some cases.

• [System configuration] Rollback to the previous version. In case of an unsuccessful upgrade to the latest version, you can roll back the configuration of the core and backup storage services to the previous working version.

• [Updates] Improved eligibility checks for updates. Added a hardware compatibility check for unsupported and unmaintained adapters. During an upgrade, the system now checks for any discrepancy with the hardware configuration.

• [Documentation] Expanded the Benchmarking and performance guide. Added more information about storage performance troubleshooting to the product documentation. The new sections explain how to configure clusters for specific use cases and troubleshoot performance issues, as well as identify performance limits for specific operations and limits affecting performance.

3. Important Notes

• Starting from the next major release, Virtuozzo Hybrid Infrastructure will run on Linux kernel 5.x. To be able to update your cluster without service downtime, your hardware must be supported. Before the update, manually run the hardware compatibility check command-line tool, to ensure that your nodes have no unsupported hardware adapters.

• Starting from this release, compute nodes will be automatically returned to operation after a reboot in case of a hardware node failure.

• Single-MDS clusters and management nodes with disabled high availability cannot be recovered. To avoid data loss, the primary management node can only be recovered during an upgrade to 6.0. Recovered nodes can only be updated to newer versions with the help of the technical support team.

• The configuration rollback is not possible for the object storage, file storage, and iSCSI services.

4. Bug Fixes

• A node with a replaced network interface card cannot connect to a cluster. (VSTOR-65772)

• Improved the chunks balancing logic. (VSTOR-65774)

• The S3 service drops requests that do not match the configured server name. (VSTOR-67214)

• A cluster update gets stuck due to duplicate compute endpoint entries in the database. (VSTOR-67420)

• Cannot manage a load balancer because the listener is stuck with the ‘PENDING_UPDATE’ status. (VSTOR-67456)

• Fixed sorting in alphabetical order for projects in the self-service panel. (VSTOR-67541)

• During a failover, the high availability IP address can be set on two nodes simultaneously for several minutes. (VSTOR-67610)

• The self-service panel does not allow connecting a virtual machine to a network that has the ‘access_as_shared’ permissions. (VSTOR-67924)

• After an MTU update, a connection through a floating IP address breaks. (VSTOR-68406)

• After being shelved, a virtual machine can have an incorrect ‘Active’ status. (VSTOR-68560)

• After a number of retries, Gnocchi redeployment is stuck for an infinite time instead of stopping and returning an error. (VSTOR-68976)

• The physical network tab does not show more than 40 domains and projects. (VSTOR-69050)

• For the S3 service, an incorrect error ‘500 Internal Server Error’ is returned instead of ‘400 Bad Request.’ (VSTOR-69105)

• The OpenStack Block Storage (Cinder) Volume agent is down on some nodes after an update. (VSTOR-69330)

• S3 geo-replication does not work with buckets if a bucket name has uppercase letters. (VSTOR-69471)

• Fixed the false-positive alert ‘Disk cache settings are not optimal’ and inability to assign disks in certain scenarios. (VSTOR-69762)

• Fixed the error ‘Volume <VOLUME_ID> is attached to unexpected servers’ that occurs when trying to migrate virtual machines live. (VSTOR-69773)

• An evacuation task is stuck in the running state while affecting other actions, like unfencing a node. (VSTOR-69821)

• For a load balancer, it is impossible to view usage statistics of its balancing pools. (VSTOR-69831)

• When using an e-mail to set an S3 quota for one user, a default quota is set. (VSTOR-70383)

• Important stability and performance improvements for S3, core storage, compute, and the admin panel. (VSTOR-59507, VSTOR-67164, VSTOR-68116, VSTOR-68981, VSTOR-69123, VSTOR-69164, VSTOR-69222, VSTOR-69463, VSTOR-69819, VSTOR-69884, VSTOR-70402)

5. Known Issues

• After a node deployment, the following false-positive alert appears in the node details: ‘Some disks stop responding and degrade the cluster performance. The disks are isolated from the cluster I/O. To troubleshoot the problem, check the disk connectivity, S.M.A.R.T. status, and dmesg output on the node.’ (VSTOR-70760)

• After three consequent crashes, the shaman service moves to the suspended state and needs to be resumed manually once the problem is resolved. (VSTOR-70746)

6. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The new and updated packages are listed in the JSON file.

1. Overview

This update provides important improvements for the core storage and compute services.

2. New Features

• [Core storage] Improved memory consumption of the metadata service for large clusters. (VSTOR-68478)

3. Bug Fixes

• The compute networking service may get stuck after an update to version 5.4 Update 2. (VSTOR-69329)

• Important stability improvements. (VSTOR-66925, VSTOR-68759, VSTOR-69819)

4. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The new and updated packages are listed in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a range of new features that cover the compute services, core and object storage, integrations, monitoring and alerts. Additionally, this release delivers stability improvements and addresses issues found in previous releases.

2. New Features

• [Compute service] Static routes management within a VPN. Now, static routes for remote subnets configured within a VPN connection are managed automatically.

• [Compute service] Improved PostgreSQL service performance. Added periodic checks and deletion of unused OpenStack objects.

• [Compute service] Support for external enterprise-grade NAS appliances. Added the possibility to emulate block storage devices in virtual machines by using NFS shares from remote NAS appliances. In this release, the external NFS storage support is an experimental feature, which is not intended for use in production environments.

• [Compute service] Support for an upgrade to Kubernetes version 1.24.

• [Compute service] Improvements in Kubernetes. Kubernetes version upgrades now avoid duplicate package upgrades.

• [Compute service] Setting passwords for virtual machines. Self-service users are able to set a password for the default administrator and use it to access specific virtual machines, instead of an SSH key.

• [Compute service] Project and quota management for domain administrators. Domain administrators can be allowed to manage projects and project quotas within the assigned domain in the self-service panel.

• [Compute service] New project and domain filters. Added project and domain filters for the compute service in the admin panel, to improve manageability of large compute clusters.

• [Core storage] Improved storage performance for sequential operations. With enabled checksumming, storage performance is improved for sequential write and read operations.

• [Object storage] CORS policies for S3 buckets. Users can manage cross-origin resource sharing (CORS) configurations by using S3-compatible API methods.

• [Integrations] Support for the vinfra CLI on third-party operating systems. It is possible to automate the remote configuration of Virtuozzo Hybrid Infrastructure clusters by using the vinfra command-line tool on third-party operating systems (macOS and Linux).

• [Monitoring and alerts]Improved cluster monitoring. Added an alert to warn system administrators when the management node high availability has four nodes, instead of three or five.

3. Important Notes

• Starting from the next major release, Virtuozzo Hybrid Infrastructure will run on Linux kernel 5.x. To be able to update your cluster without service downtime, your hardware must be supported. Virtuozzo Hybrid Infrastructure with the new kernel works on the same hardware that is recommended for Red Hat Enterprise Linux. Ensure that the hardware you are using or going to use has the required certification for Red Hat Enterprise Linux 9.

• During the update, you may receive false-positive alerts. Please wait until the update installation is complete, as the raised alerts will be cleared automatically.

4. Bug Fixes

• The NTP server inside virtual machines may not work properly with a floating IP address. (VSTOR-67919)

• Volumes with external PureStorage that are attached to virtual machines cannot be resized. (VSTOR-67791)

• Avoid unnecessary virtual IP reconfiguration when high availability is not changed. (VSTOR-67423)

• Unable to assign the metadata or storage role to a disk with an existing MBR partition. (VSTOR-67255)

• Object storage fails if volumes were created in a version earlier than 2.3. (VSTOR-67156)

• Fixed permissions for the Gnocchi directory on different cluster nodes. (VSTOR-66736)

• Added details to the log entry of a validation error that occurs during the compute cluster creation. (VSTOR-66563)

• Fixed IQN validation in the admin panel. (VSTOR-66519)

• Fixed a false-positive alert ‘Software RAID is not fully synced.’ (VSTOR-65508)

• A VPN may get stuck in the ‘pending_create’ state if the router HA ports were deleted. (VSTOR-63357)

• Remove the free licensed space value from the compute overview screen. (VSTOR-62270)

• The compute cluster deployment may get stuck in the ‘deploying’ state. (VSTOR-45919)

• Important stability and performance improvements. (VSTOR-67733, VSTOR-66925, VSTOR-66516, VSTOR-66299, VSTOR-66187, VSTOR-66051, VSTOR-60531)

5. Known Issues

• The false-positive alert ‘RabbitMQ node is down’ appears when the compute cluster is deployed and the management node high availability is disabled. (VSTOR-67365)

• A Kubernetes upgrade may not work if the DNS name of the compute API has been changed. (VSTOR-68064)

6. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The new and updated packages are listed in the JSON file.

1. Overview

This update provides a stability improvement for the update procedure.

2. Bug Fixes

• Improved stability of the update procedure. (VSTOR-68152)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The new and updated packages are listed in the JSON file.

1. Overview

This update provides a stability improvement for the core storage service.

2. Bug Fixes

• Improved stability of the core storage during an update by adding metadata versioning checks. (VSTOR-65751)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The new and updated packages are listed in the JSON file.

1. Overview

This update provides stability fixes for the compute service.

2. Bug Fixes

• If there is a network port with the address 0.0.0.0/0, a VM creation fails with the error ‘Failed to allocate the network(s), not rescheduling.’ (VSTOR-66686)

• Snapshot metrics per storage policy are missing. (VSTOR-67068)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The new and updated packages are listed in the JSON file.

1. Overview

This update provides new features, as well as stability fixes for the compute and core storage services.

2. New Features

• [Compute service] Configuring CPU features for virtual machines. Now, it is possible to enable or disable CPU feature flags for virtual machines, to avoid live migration compatibility issues across compute nodes, as well as to control nested virtualization.

• [Object storage] Support for S3 object expiration actions. Added the possibility to delete S3 objects by prefix. Deleting objects by tag is not available.

• [Updates] Hardware compatibility check. Before upgrading to the next major release, you can manually check your hardware for compatibility with the new Linux kernel.

3. Important Notes

• Starting from the next major release, Virtuozzo Hybrid Infrastructure will run on Linux kernel 5.x. To be able to update your cluster without service downtime, your hardware must be supported. Virtuozzo Hybrid Infrastructure with the new kernel works on the same hardware that is recommended for Red Hat Enterprise Linux. Ensure that the hardware you are using or going to use has the required certification for Red Hat Enterprise Linux 9.

• During the update, you may receive false-positive alerts. Please wait until the update installation is complete, as the raised alerts will be cleared automatically.

4. Bug Fixes

• A VM creation fails with the error ‘Unable to update the attachment.’ (VSTOR-62742)

• Some charts in the admin panel or Grafana dashboard may be empty. (VSTOR-65824)

• After a failed high availability reconfiguration, the compute cluster may be stuck in the reconfiguring state. (VSTOR-65587)

• VM firewall rules for ICMP are not validated in the management panels. (VSTOR-63334)

• Disables unnecessary analytics in Grafana. (VSTOR-63220)

• Fixes floating IP quota usage. (VSTOR-62996)

• Cluster operations in the admin panel and via vinfra may fail with the error ‘ValueError: ‘registering’ is not a valid State.’ (VSTOR-62984)

• Geo-replication does not proceed after all problems are resolved. (VSTOR-62572)

• Impossible to add a node to the compute cluster if it was configured with the ‘HostPassthrough’ CPU model. (VSTOR-60477)

• Stability fixes for the core storage, Backup Gateway, and compute services. (VSTOR-63249, VSTOR-63248, VSTOR-62831, VSTOR-62165, VSTOR-60887, VSTOR-62315)

5. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The new and updated packages are listed in the JSON file.

1. Overview

This update provides stability fixes for the compute, object storage, and core storage services.

2. Bug Fixes

• After an update from 5.2.x to 5.3.x, the object storage may not be started due to an invalid configuration file. (VSTOR-65934)

• Unable to manage a virtual machine after a failed migration. (VSTOR-63084)

• In some cases, resetting a state may not work. (VSTOR-63050, VSTOR-59007)

• A VM creation fails with the error ‘Unable to update the attachment.’ (VSTOR-62742)

• Fixes problems with snapshot deletion. (VSTOR-59846, VSTOR-59845, VSTOR-62744)

• Fixes Gnocchi metrics reporting in some scenarios. (VSTOR-63041)

• Stability issues for the storage and compute services. (VSTOR-66541, VSTOR-66013, VSTOR-65854, VSTOR-63398, VSTOR-63249, VSTOR-62165)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The new and updated packages are listed in the JSON file.

1. Overview

This update provides stability fixes for the compute and core storage services.

2. Bug Fixes

• Unable to manage a virtual machine after a failed migration. (VSTOR-63084)

• In some cases, resetting a state may not work. (VSTOR-63050, VSTOR-59007)

• Fixes Gnocchi metrics reporting in some scenarios. (VSTOR-63041)

• Stability fixes for the core storage. (VSTOR-66013, VSTOR-63249)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a range of new features that cover compute services, management node high availability, monitoring and alerts, and the user interface. Additionally, this release delivers stability improvements and addresses issues found in previous releases.

2. New Features

• [Compute service] MTU configuration for physical compute networks. System administrators have the possibility to adjust the MTU size of physical networks in the compute cluster.

• [Compute service] Manual fencing of compute nodes. Now, system administrators can manually fence compute nodes in the admin panel. By placing a node in the fenced state, you isolate it in the compute cluster and halt VM scheduling on this node. This is useful in case of node maintenance or if you want to have dedicated controller nodes without workloads.

• [Compute service] Ability to define the default storage policy. When creating the compute cluster, system administrators can now define parameters for the default storage policy, including the redundancy scheme.

• [Management node high availability] Management node high availability (HA) with five nodes. Now, it is possible to expand the HA configuration of the management node, up to five nodes. With a five-node HA configuration, the cluster can tolerate a simultaneous failure of two management nodes.

• [Monitoring and alerts] Improved compute service monitoring. Added dashboards and alerts for the compute service, to help system administrators to monitor and check the service state.

• [User interface] Enhanced initial disk configuration. The new screens allow bulk disk management and show warnings against unrecommended disk configurations. Additionally, when adding nodes to the storage cluster, you can reuse the disk configuration of existing cluster nodes.

• [User interface] New NFS screens. Improved user experience with NFS storage. The screens have been redesigned on the new framework, to make the user interface more consistent.

3. Important Notes

• Starting from the next major release, Virtuozzo Hybrid Infrastructure will run on Linux kernel 5.x. To be able to update your cluster without service downtime, your hardware must be supported. Virtuozzo Hybrid Infrastructure with the new kernel works on the same hardware that is recommended for Red Hat Enterprise Linux. Ensure that the hardware you are using or going to use has the required certification for Red Hat Enterprise Linux 9.

• In this release, Windows 7 becomes deprecated and is no longer supported as a guest operating system.

• During the update, you may receive false-positive alerts. Please wait until the update installation is complete, as the raised alerts will be cleared automatically.

4. Bug Fixes

• Fixes a memory leak in the S3 Gateway service. (VSTOR-52989)

• Communication between VMs is lost while the Neutron OVS agent is restarting. (VSTOR-58698)

• Unable to update a cluster due to parallel execution of two alert handlers. (VSTOR-59236)

• Unable to delete snapshots because of an expired Keystone token. (VSTOR-59845)

• Cannot delete large snapshots because the deletion process runs out in 20 minutes. (VSTOR-59846)

• An error occurs during an upgrade because the S3 package should be updated together with other backend packages. (VSTOR-60488)

• Cannot attach a volume because the number of already attached volumes is incorrect. (VSTOR-60799)

• kube-proxy cannot update connections to outdated services. (VSTOR-61357)

• Failed to upload a VHD image if the target OS drivers in OpenStack are missing or incorrect. (VSTOR-61387)

• Reaching the QueuePool size limit of the Neutron database causes connection timeouts. (VSTOR-61396)

• Cannot create a volume snapshot because the VM is in the error state. (VSTOR-61533)

• An incorrect disk temperature value is reported for specific disk models. (VSTOR-61721)

• Unable to change the IP address on an OpenvSwitch VLAN interface that is used for the compute service. (VSTOR-61912)

• An incorrectly provided NoVNC link by OpenStack causes problems with API integrations. (VSTOR-62328)

• Cannot assign any role to a disk if a CS journal on one of the nodes is unmounted. (VSTOR-62595)

• Cannot change or remove a placement for a virtual machine. (VSTOR-62669)

5. Known Issues

• The node maintenance mode does not evacuate resources as expected. (VSTOR-47350)

• Snapshot creation can take too much time. (VSTOR-48293)

• A Kubernetes node group cannot be removed if its volumes are associated with a deleted VM. (VSTOR-49875)

• Virtual machines may have connectivity issues in a VXLAN network, due to an incorrectly processed port update notification. (VSTOR-50039)

• Unable to change a VM flavor because the volume attachment cannot be found. (VSTOR-55325)

• The uplink for a newly added node loses the gateway entry after a network configuration. (VSTOR-57933)

• A volume is stuck in the detaching or error state because its cloning process has not been completed. (VSTOR-58965)

• A node may go offline because its memory cache limit does not match the VCMMD cache settings. (VSTOR-59718)

• A cluster update fails because the NFS service is enabled and running after an offline NFS node release. (VSTOR-60766)

• A node update fails due to a Gnocchi ploop space error. (VSTOR-60783)

• vinfra does not show volumes attached to a deleted VM. (VSTOR-61002)

• A VM migration may fail because the snapshot creation and deletion shares the same instance lock. (VSTOR-61552)

• A volume fails to expand due to an RPC sync timeout. (VSTOR-61692)

• The compute reconfiguration may get stuck after a node replacement in the HA configuration due to an outdated hostname record. (VSTOR-61703)

6. Installing the Update

You can upgrade Virtuozzo Hybrid Infrastructure 5.3 to 5.4 in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The new and updated packages are listed in the JSON file.

1. Overview

This update enables a new scenario for VPN as a service and provides important stability fixes.

2. New Features

• [Compute service] Simultaneous connectivity through a VPN and floating IP address. Now, it is possible to allow simultaneous connectivity through a VPN tunnel and floating IP addresses, by adding static routes to a virtual router for remote subnets used by a VPN connection.

3. Bug Fixes

• Stability issues for the storage and Backup Gateway services. (VSTOR-60216, VSTOR-61366)

4. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides new features for security, monitoring, and the compute service, as well as bug fixes and improvements.

2. New Features

• [Security] Data-in-transit encryption. To protect networks against eavesdropping attacks and traffic hijacking, Virtuozzo Hybrid Infrastructure supports data-in-transit encryption between cluster nodes. Data transmitted over a network is encrypted by using the AES-128 standard.

• [Compute service] Added support for Oracle Linux 7 as a guest operating system.

• [Monitoring] Added a set of metrics for monitoring backup storage migration.

• [Monitoring] Added metrics and alerts for monitoring backup storage certificates.

3. Bug Fixes

• It is impossible to start a cluster update after an eligibility check failure. (VSTOR-60452)

• A stability fix for Windows 2016/2019 virtual machines on specific CPUs. (VSTOR-60459)

• Fixes the false-positive alerts ‘Docker service is down,’ ‘Node is offline,’ and ‘Master metadata service changes too often’ that appear during an update. (VSTOR-60448)

• Added dashboards and metrics for the load balancer and Kubernetes API status. (VSTOR-60387)

• The Neutron, Cinder, and Nova dashboards may show ‘No data.’ (VSTOR-59696)

• Reconfiguration of the compute cluster during an update should be prohibited, to avoid possible issues. (VSTOR-59751)

• Fixes autodetection of the image type while uploading images via vinfra. (VSTOR-59617)

• If the object storage is deleted, the critical alert ‘Object storage has failed’ should not be raised. (VSTOR-59562)

• Fixes the false-positive alert ‘Volume mismatch’ for detached ISO volumes. (VSTOR-59433)

• Cannot manage a virtual machine due to temporary snapshot leftovers after live migration. (VSTOR-48706)

• An error message is not displayed when a node release from the compute cluster conflicts with another operation. (VSTOR-60304)

• Important stability and performance improvements. (VSTOR-51731, VSTOR-59728, VSTOR-59315, VSTOR-54550, VSTOR-56757, VSTOR-59985, VSTOR-60626, VSTOR-60551, VSTOR-60529, VSTOR-60315, VSTOR-60134, VSTOR-59933, VSTOR-59646)

4. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides important stability fixes.

2. Bug Fixes

• Some compute alerts may not be raised. (VSTOR-59696)

• Stability fixes for the core storage. (VSTOR-59714, VSTOR-60216)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a range of new features that cover Kubernetes as a Service, storage performance, security, monitoring and alerts, and the user interface. Additionally, this release delivers stability improvements and addresses issues found in previous releases.

2. New Features

• [Compute service] Kubernetes advanced mode. Added support for Kubernetes cluster autoscaling, integrated monitoring, and ability to specify labels to manage Kubernetes features. Autoscaling allows you to automatically scale Kubernetes worker groups up and down, depending on a cluster load. By using labels, you can, for example, disable SELinux for a new Kubernetes cluster.

• [Compute service] Creating Kubernetes clusters under a service user. Starting from this version, Kubernetes clusters will be created by using a special service user. This means that any project user will be able to manage all Kubernetes clusters within the assigned project.

• [Compute service] Support for a clean installation of Kubernetes version 1.24. The new version can be used to create Kubernetes clusters.

• [Compute service] Configurable scheduling of virtual machines. Extended the scheduler parameters that are available for configuration, thus enabling a more granular control over compute workload distribution. Now, you can choose between at least two distribution modes for virtual machines: to spread them evenly across all compute nodes or to consolidate them on nodes as much as possible.

• [Compute service] OpenStack Xena. Starting from this release, the compute services are rebased to the OpenStack Xena version.

• [Core storage] NVMe and SSD performance boost with replication data redundancy. By configuring multiple chunk servers per NVMe and SSD storage drive, you can improve storage performance and scaling to a high number of clients. The performance increase is only possible when using redundancy by replication.

• [Object storage] Support for the UploadPartCopy S3 API action. Added the possibility to upload parts by copying data from an existing object as a data source.

• [Monitoring and alerts] Grafana dashboards for the compute services. The new dashboards show the state of the compute services and compute resource allocation, namely vCPUs, RAM, storage policies, and floating IP addresses, for all projects or filtered per domain/project.

• [Security] Improved security for backup and object storage. The backup and object storage services now work under restricted accounts that have access only to service data, configuration files, and logs.

• [Security] Disabled vulnerable TLS protocol versions. Connections to the admin and self-service panels, as well as other services with the API, can only be established with TLS protocol versions 1.2 and 1.3. Using versions 1.0 and 1.1 is no longer available.

• [User interface] Management of locked users. In the command-line interface, it is now possible to list and manage user accounts that have been locked after a number of successive failed login attempts.

3. Important Notes

• Starting from the next major release, Virtuozzo Hybrid Infrastructure will run on Linux kernel 5.x. To be able to update your cluster without service downtime, your hardware must be supported. Virtuozzo Hybrid Infrastructure with the new kernel works on the same hardware that is recommended for Red Hat Enterprise Linux. Ensure that the hardware you are using or going to use has the required certification for Red Hat Enterprise Linux 9.

• Windows 7 as a guest operating system will be deprecated in future releases.

• Disk auto replacement is not supported for NVMe and SSD devices with multiple chunk services.

• During the update, you may receive false-positive alerts. Please wait until the update installation is complete, as the raised alerts will be cleared automatically.

• Do not perform any cluster configuration tasks in the admin panel or command-line interface during the update, as this will lead to an update failure and cluster downtime.

4. Bug Fixes

• The Kubernetes service is not restarted if its Podman container is active. (VSTOR-50283)

• The redundancy mode of the default storage policy is set incorrectly. (VSTOR-51023)

• A Kubernetes cluster stops working after switching to a service user. (VSTOR-52250)

• An S3 bucket size is set incorrectly after a successful upload. (VSTOR-54208)

• Space per service is reported incorrectly. (VSTOR-54460)

• The self-service panel does not show a newly added node group in Kubernetes cluster properties. (VSTOR-54884)

• Changes for the network endpoint are not properly applied. (VSTOR-55574)

• Multiple false-positive alerts appear for a network failure. (VSTOR-56169)

• The list of images is not loaded in the mobile version of the Safari browser. (VSTOR-56527)

• Unable to reach a virtual machine via its public network interface after it was migrated to another node. (VSTOR-57185)

• The compute service sets different MTU sizes while creating compute networks. (VSTOR-57190)

• When the compute cluster fails to be deployed due to a timeout, it does not have the error state. (VSTOR-57534)

• The Kubernetes service goes down if an IP address is missing on a certain node. (VSTOR-57734)

5. Known Issues

• When the networking service experiences issues connecting to the messaging queue, it leaks memory. (VSTOR-34737)

• Prometheus does not show network traffic for the storage interface if RDMA is enabled. (VSTOR-59380)

• After detaching a volume, it cannot be attached to another virtual machine because it is still shown in the previous VM configuration. (VSTOR-41107)

• An error is not displayed in the self-service panel if the compute cluster does not have enough resources to create a Kubernetes cluster. (VSTOR-43174)

• The default storage policy is not selected by default. (VSTOR-45826)

• Snapshot creation can take too much time. (VSTOR-48293)

• A Kubernetes node group cannot be removed if its volumes are associated with a deleted VM. (VSTOR-49143)

• Unable to start a virtual machine when the “VM public” traffic type is removed and re-added to the infrastructure network. (VSTOR-54261)

• Unable to change a VM flavor because the volume attachment cannot be found. (VSTOR-55325)

• A Kubernetes worker group cannot be resized due to a task timeout. (VSTOR-55353)

• A RAM overload occurs due to a huge amount of messages in the messaging queue. (VSTOR-55677)

• The uplink for a newly added node loses the gateway entry after a network configuration. (VSTOR-57933)

• A connectivity failure occurs due to a missing default gateway after a node deletion. (VSTOR-57978)

6. Installing the Update

You can upgrade Virtuozzo Hybrid Infrastructure 5.2 to 5.3 in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The new and updated packages are listed in the JSON file.

1. Overview

This update provides full support for Authorization Code Flow, as well as bug fixes and improvements.

2. New Features

• [Security] Improved OpenID authorization. After being available in the experimental mode in earlier releases, Authorization Code Flow is now fully supported.

3. Important Notes

• In this release, we have removed recommendations to disable the write cache. If you previously disabled the write cache as was suggested by the alert, please reset your settings to their defaults.

• During the update, you may receive false-positive alerts. Please wait until the update installation is complete, as the raised alerts will be cleared automatically.

4. Bug Fixes

• It is impossible to set the disk role to “Unassigned” while joining a node to the cluster. (VSTOR-57337)

• Unable to add an iSCSI target with multiple portals to a cluster node. (VSTOR-57187)

• Improved a network connectivity alert. (VSTOR-56759)

• PureStorage iSCSI volumes have only one path instead of multiple paths. (VSTOR-56270)

• Erasure coding files have huge journals. (VSTOR-55235)

• Operations with volumes may fail with a timeout in the case of more than one million volumes. (VSTOR-54327)

• Increased the limit for open object storage files from 1024 to 10000. (VSTOR-51510)

• Fixed S3 geo-replication if one of the clusters’ hostname has capital letters. (VSTOR-50781)

• The Docker service stops unexpectedly after a vstorage-mount crash. (VSTOR-46936)

• Stability and performance improvements. (VSTOR-51540, VSTOR-57276, VSTOR-56722, VSTOR-56486, VSTOR-56430, VSTOR-56370)

5. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides important fixes for the compute service.

2. Bug Fixes

• If a virtual machine is connected to a VLAN-based physical network, the VM may have no network connectivity after its migration due to a missing ARP announcement. (VSTOR-56942)

• Fixes false-positive alerts for the compute cluster. (VSTOR-56792, VSTOR-56789, VSTOR-56639, VSTOR-56625)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a range of new features that enhance compute services, the cluster management and upgrade process, monitoring and alerts, the user interface, and the documentation. Additionally, this release delivers stability improvements and addresses issues found in previous releases.

2. New Features

• [Compute service] Pure Storage support for compute volumes. Now, the compute service supports integration with Pure Storage, which allows automated provisioning and management of virtual machine volumes on top of Pure Storage through the compute service and compute API.

• [Compute service] Improved virtual machine high availability. If a compute node fails, the high availability mechanism now persistently iterates attempts to recover affected virtual machines until all of them are rebuilt on healthy nodes.

• [Compute service] Support for an upgrade to Kubernetes version 1.23. Kubernetes clusters with version 1.22 can now be upgraded to version 1.23.

• [Cluster management] Ability to place multiple nodes in the maintenance mode. Improved cluster operability by allowing the ability to place more nodes in the maintenance mode, one at a time. The cluster can tolerate multiple nodes in maintenance simultaneously as long as the other cluster nodes have enough resources to accommodate evacuated workloads.

• [Updates] Rebootless patch updates. Thanks to the new granular maintenance mode and update for services, most future patch updates will not require a system reboot. The update impact depends on the changes that a new version introduces and can be one of the following: reboot required, maintenance required, or no impact.

• [Monitoring and alerts] Compute service monitoring. Added a set of metrics and alerts for the compute service. The new alerts cover the unavailability of services, configuration inconsistencies, as well as resource shortage per cluster, node, and project.

• [Monitoring and alerts] Virtual machine history. Now, you can examine a VM history in the event log, which contains all of the VM management operations performed by users in the user or command-line interface.

• [Monitoring and alerts] iSCSI alert for failed volumes. Added a new alert for failed volumes, which is raised when the automatic recovery of the block storage services does not work.

• [User interface] New screens for management node and security settings. Streamlined user experience with management node and security settings. The screens have been redesigned on the new framework and moved to the system settings.

• [Documentation] Performance benchmark guidelines for S3, iSCSI, and NFS services. Standardized approaches to the product performance validation, to help partners and customers benchmark their productional cluster deployments.

3. Bug Fixes

• No troubleshooting details are shown in the admin panel for the alert “No connectivity with node.” (VSTOR-42865)

• Unable to change network access for projects that have a shared network connected to virtual routers. (VSTOR-44159)

• The Docker service stops unexpectedly after a vstorage-mount crash. (VSTOR-46936)

• Reverting to snapshots is only available for disks attached to stopped VMs. (VSTOR-49851)

• No custom chain in IPv6 tables as a part of the default configuration. (VSTOR-51878)

• An update can be started while the previous update task is still being canceled. (VSTOR-51985)

• Added validation for executing kolla-ansible with the correct permission. (VSTOR-52895)

• Not all IP addresses per interface are shown on the router interfaces screen. (VSTOR-53634)

• A healthy load balancer with a floating IP address may occasionally return errors. (VSTOR-54171)

• Unable to create a Kubernetes cluster in a public network that has both IPv4 and IPv6 subnets configured. (VSTOR-54586)

• The metric interval for Prometheus and Grafana is set incorrectly. (VSTOR-54729)

• Changed the “Compute” translation in Japanese. (VSTOR-54909)

• Unable to create more than 250 snapshots per volume. (VSTOR-55098)

• A volume snapshot cannot be removed if it has been deleted via virsh. (VSTOR-55359)

• The compute health manager is not disabled during a cluster upgrade. (VSTOR-55516)

4. Known Issues

• When the networking service experiences issues connecting to the messaging queue, it leaks memory. (VSTOR-34737)

• After detaching a volume, it cannot be attached to another virtual machine because it is still shown in the previous VM configuration. (VSTOR-41107)

• The default storage policy is not selected by default. (VSTOR-45826)

• A virtual machine loses connectivity with the public network due to the non-processed IP rule for its floating IP address. (VSTOR-49875)

• Virtual machines may have connectivity issues in a VXLAN network due to an incorrectly processed port update notification. (VSTOR-50039)

• OpenStack cloud provider services do not work after changing the Kubernetes cluster owner’s role. (VSTOR-52250)

• Unable to start a virtual machine when the “VM public” traffic type is removed and re-added to the infrastructure network. (VSTOR-54261)

• The node maintenance mode does not evacuate resources as expected. (VSTOR-47350)

• Snapshot creation can take too much time. (VSTOR-48293)

• The object storage CLI does not work as expected with the volume key parameter. (VSTOR-48297)

• A Kubernetes node group cannot be removed if its volumes are associated with a deleted VM. (VSTOR-49143)

• An S3 bucket size is calculated incorrectly. (VSTOR-54208)

5. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides bug fixes and improvements.

2. Bug Fixes

• The network orchestration service does not restart after an update. (VSTOR-54473)

• Fixes the root cause of the alert “Cluster had blocked or slow replication.” (VSTOR-54265)

• Fixes the configuration of Kerberos authentication. (VSTOR-54066)

• Only one IP address per interface is shown for a router. (VSTOR-54029, VSTOR-53625)

• Fixes cold migration for virtual machines with UEFI boot. (VSTOR-53706)

• Backup storage geo-replication fails for small files with the error “the size of replica file is greater than push.sync_offset on master.” (VSTOR-53702)

• Cannot create a Kubernetes cluster in a public network with both IPv4 and IPv6 subnets. (VSTOR-53524)

• Unable to download data from an S3 bucket without refreshing the page. (VSTOR-53501)

• Fixes a sporadic failure to download the configuration file of Backup Gateway geo-replication. (VSTOR-53729)

• Compute cluster redeployment fails with the error “Cannot use external network as it has an OVS VLAN interface assigned on node.” (VSTOR-53054)

• After the update to version 5.1, network interface names inside Ubuntu guests may be changed. (VSTOR-52747)

• The load balancer metrics are missing in Prometheus. (VSTOR-51773)

• Under certain circumstances, volume detachment may fail. (VSTOR-50309)

• A stability fix for Backup Gateway on top of object storage. (VSTOR-54496)

• Cannot redeploy Backup Gateway on top of NFS or object storage due to an incorrect initial configuration. (VSTOR-54300)

• Stability and performance improvements. (VSTOR-54216, VSTOR-54186, VSTOR-54001, VSTOR-53873, VSTOR-53653, VSTOR-53574, VSTOR-53003)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a wide range of new features that enhance service providers’ interoperability and help to expand their services. The improvements cover compute services, security, core storage, and the user interface. Additionally, this release delivers stability improvements and addresses issues found in previous releases.

2. New Features

• [Compute service] Support for an upgrade to Kubernetes version 1.22. Kubernetes clusters with version 1.21 can now be upgraded to version 1.22.

• [Compute service] Support for a clean installation of Kubernetes version 1.23. The new version can be used to create Kubernetes clusters.

• [Compute service] Highly available load balancers for Kubernetes clusters. Now, the system will automatically create highly available load balancers for the Kubernetes API and applications (external load balancers). High availability for load balancers is configured for the Kubernetes service via the command-line interface. The separate load balancer for etcd has been removed.

• [Compute service] Ability to use load balancer flavors for Kubernetes applications. Self-service users can select the load balancer flavor in a Kubernetes deployment file (external load balancer). It is also possible to select the load balancer size according to your application needs. System administrators can create multiple load balancer flavors by using the OpenStack command-line interface.

• [Compute service] Added an option to boot virtual machines in the UEFI mode. Virtual machines can now be booted in the UEFI mode. For virtual machines created from ISO images, UEFI boot is enabled during the VM creation. For virtual machines deployed from templates, UEFI boot is enabled during the template upload.

• [Compute service] IPv6 support for load balancers. Added support for IPv6 addresses for load balancers that are created to operate within physical networks.

• [Compute service] Configurable default quotas for new projects. The default project quotas for load balancers, Kubernetes clusters, and placements can now be configured via the command-line interface. The default quotas are applied when creating a project via the OpenStack API.

• [Security] Improved OpenID authorization. Now, Authorization Code Flow is available in the experimental mode.

• [Security] Improved and simplified management and troubleshooting for Kubernetes clusters. A system administrator can run commands inside a Kubernetes virtual machine from the compute node this VM resides on. Users with different roles and access to a specific project can download a Kubernetes configuration file: project members and domain administrators can download the file in the self-service panel, while system administrators can do it via the command-line interface.

• [User interface] New object storage screens. Improved user experience with object storage. The screens have been redesigned on the new framework to make the user interface more consistent.

• [User interface] Copying of important information to clipboard. Added the possibility to easily copy important text information, such as emails and IP addresses, from the admin panel to other applications.

• [Installer] Requirements for quantity of drives. Removed the mandatory requirement to have at least two drives, for system and storage types, in the expert mode. To continue the installation, you will need only one drive for booting.

• [Backup storage] Ability to add multiple backup storage registrations.

3. Important Notes

• Kubernetes version 1.23 is available only for new deployments. An in-place update from version 1.22 will be available in the next release.

• Kubernetes version 1.21 will be deprecated in future releases. Use the currently supported version 1.23 to plan your containerized environments.

• Kubernetes version 1.20 is deprecated. Update to the currently supported version 1.21.

• Object storage integration with Acronis Notary is no longer available.

• To improve security, the default TLS version accepted by backup storage is set to 1.2.

4. Bug Fixes

• An invalid VNC IP address is set for a virtual machine after its migration. (VSTOR-50829)

• Load balancer metrics are missing. (VSTOR-51773)

• Fixed the soft anti-affinity filter for shelved virtual machines. (VSTOR-52611)

• Fixed an issue in the VLAN traffic routing. (VSTOR-52547)

• Failed to install the Kubernetes add-on service because of the missing environment variables. (VSTOR-30850)

• Unable to delete large volume snapshots. (VSTOR-41372)

• The backend services fail to start if a node interface with the management virtual IP address is reassigned to another network. (VSTOR-44604)

• The compute cluster fails after adding nodes with newer versions to the high availability configuration. (VSTOR-46583)

• After deleting a virtual machine, its volume stays attached. (VSTOR-48099)

• When a node enters maintenance, virtual machines that failed to be migrated are skipped. (VSTOR-48295)

• Fixed a problem with an OVS bridge when Linux VLANs are used. (VSTOR-51685)

• A minor update for quota configuration in the admin panel. (VSTOR-52623)

• Storage space usage is wrongly displayed in the self-service panel. (VSTOR-50814)

• Cannot start NFS shares and create new ones. (VSTOR-52820)

• Important security fixes. (VSTOR-53595, VSTOR-54722, VSTOR-53723)

5. Known Issues

• When the networking service experiences issues connecting to the messaging queue, it leaks memory. (VSTOR-34737)

• After detaching a volume, it cannot be attached to another virtual machine because it is still shown in the previous VM configuration. (VSTOR-41107)

• The default storage policy is not selected by default. (VSTOR-45826)

• The Docker service stops unexpectedly after a storage-mount crash. (VSTOR-46936)

• The node maintenance mode does not evacuate resources as expected. (VSTOR-47350)

• Snapshot creation can take too long. (VSTOR-48293)

• The object storage CLI does not work as expected with the volume key parameter. (VSTOR-48297)

• A Kubernetes node group cannot be removed if its volumes are associated with a deleted VM. (VSTOR-49143)

• A virtual machine loses connectivity with the public network due to the non-processed IP rule for its floating IP address. (VSTOR-49875)

• The compute service has a wrong unicast rule for the remote port. (VSTOR-50039)

• Cannot configure high availability in the admin panel after a failed node replacement in the HA configuration. (VSTOR-50148)

• The compute service stops working after changing Kubernetes owner roles. (VSTOR-52250)

6. Installing the Update

You can upgrade Virtuozzo Hybrid Infrastructure 5.0 to 5.1 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.

1. Overview

This update provides important security fixes.

2. Bug Fixes

• A security fix for CVE-2022-1552 in PostgreSQL. (VSTOR-53595)

• A security fix for CVE-2018-25032 in zlib. (VSTOR-54722)

• A security fix for CVE-2022-1271 in gzip. (VSTOR-53723)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides important security fixes.

2. Bug Fixes

• A security fix for CVE-2022-1552 in PostgreSQL. (VSTOR-53595)

• A security fix for CVE-2018-25032 in zlib. (VSTOR-54722)

• A security fix for CVE-2022-1271 in gzip. (VSTOR-53723)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability and performance fixes.

2. Bug Fixes

• Stability fixes for object storage. (VSTOR-51857, VSTOR-52213)

• A performance fix for iSCSI. (VSTOR-52492)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The new and updated packages are listed in the JSON file.

1. Overview

This update provides security and stability fixes.

2. Bug Fixes

• A security fix for CVE-2022-0378. (VSTOR-51927)

• Fixed a connectivity issue when an Open vSwitch bridge is recreated for VLAN physical networks. (VSTOR-51506)

• Entering maintenance may get stuck if a node that enters this mode hosts suspended virtual machines. (VSTOR-51357)

• A cluster update fails due to old cached data if a newer update is available. (VSTOR-49593)

• Creating object storage may fail after the previous unsuccessful creation. (VSTOR-51143)

• Critical stability fixes for the core storage. (VSTOR-51858, VSTOR-51604)

3. 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 new and updated packages are listed in the JSON file.

1. Overview

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.

1. Overview

This hotfix update provides important fixes for the storage, Backup Gateway, and object storage services.

2. Bug Fixes

• Invalid JSON data is returned for the S3 Usage Object. (VSTOR-50690)

• Different storage services may not restart due to a deadlock in the signal handler. (VSTOR-50626)

• A stability fix for object storage. (VSTOR-50968)

3. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a wide range of new features that enhance service providers’ interoperability and help expand their services. The improvements cover compute services, object storage, security, and monitoring. Additionally, this release delivers stability improvements and addresses issues found in previous releases.

2. New Features

• [Compute service] VPN as a service for self-service users. Highly available IPsec VPN with a simplified and automated deployment is now available as a service in the self-service panel.

• [Compute service] Capacity-based QoS policies for virtual machine volumes. Introduced per-GB QoS policies that allow system administrators to manually configure IOPS and throughput for compute volumes depending on their size. In this release, per-GB QoS policies are available only in the command-line interface.

• [Compute service] Support for Kubernetes version 1.22. The new version can be used to create Kubernetes clusters.

• [Compute service] Placement improvements:

  • Placements for flavors in the admin panel. System administrators can now assign placements to flavors in the admin panel.

  • Flavors filtering by placement. When creating virtual machines in the self-service and admin panels, users can easily select flavors with required placements by using the new filter.

• [Object storage] S3 cross-region replication (CRR) support. Now S3 users can leverage Amazon S3-compatible CRR API, to copy objects asynchronously across buckets stored in different clusters and public cloud providers.

• [Security] Ability to integrate with external identity providers. System administrators can configure user authentication to the admin and self-service panels through external identity providers that support the OpenID Connect protocol (for example, Active Directory Federation Services). Federated users are automatically mapped to local domain groups based on their identity provider attributes. The set of actions available to federated users is defined by the roles assigned to their domain groups.

• [User management] User groups support. Now, it is possible to add users to domain groups, for simplified permission management and project assignment.

• [Monitoring and alerting] Update process monitoring. Added metrics and alerts for the update process, to help system administrators to track the update status remotely and to update multiple clusters to the latest version in time.

• [Monitoring and alerting] Additional alerts for cluster monitoring. More alerts are now available in the admin panel via the built-in Prometheus and Alertmanager monitoring toolkit. The new alerts cover object storage, core storage, and infrastructure networking. Moreover, you can configure Alertmanager to send notifications via external systems, such as PagerDuty.

3. Important Notes

• S3 geo-replication and CRR are incompatible. S3 users cannot use CRR if geo-replication has already been enabled between clusters in the admin panel.

• If you have configured GPU passthrough for compute nodes that do not have the management node role in version 4.7, repeat the instructions from the section “Enabling PCI passthrough and vGPU support” in the Administrator Guide.

• Kubernetes version 1.22 is available only for new deployments. An in-place update from version 1.21 will be available in the next release.

• Kubernetes version 1.20 will be deprecated in future releases. Use the currently supported version 1.22 to plan your containerized environments.

• Kubernetes version 1.19 is deprecated. Update to the currently supported version 1.20.

4. Bug Fixes

• A virtual machine with an SR-IOV network port cannot boot if multiple SR-IOV network interfaces of a compute node are attached to the same network. (VSTOR-49303)

• A virtual machine with the SNAT configuration lost its internet connection after the node with an active virtual router was rebooted. (VSTOR-48939)

• A renewal of load balancer certificates leads to an infinite ‘Configuring’ status. (VSTOR-48536)

• The IPv6 firewall rule ACCEPT for port 22 accidentally appeared in ip6tables. (VSTOR-47986)

• A VM migration failed due to an incorrect block device mapping in the database. (VSTOR-47868)

• Fixed the false-positive alert “Time not synced.” (VSTOR-47426)

• An alert is raised for an unavailable unassigned disk. (VSTOR-47320)

• No ability to change the health checker URL of a balancing pool. (VSTOR-46942)

• Incorrect physical space usage is shown in the admin panel. (VSTOR-46845)

• A volume is locked by its snapshot operation. (VSTOR-46261)

5. Known Issues

• An error is not displayed in the self-service panel if the compute cluster does not have enough resources to create a Kubernetes cluster. (VSTOR-43174)

• Failed to migrate a virtual machine during a compute cluster upgrade. (VSTOR-45662)

• After detaching a volume, it cannot be attached to another virtual machine because it is still shown in the previous VM configuration. (VSTOR-41107)

• When the networking service experiences issues connecting to the messaging queue, it leaks memory. (VSTOR-34737)

• Unable to delete large volume snapshots. (VSTOR-41372)

• Cannot start a virtual machine after an incomplete migration. (VSTOR-43837)

• The compute cluster fails after adding nodes with newer versions to the high availability configuration. (VSTOR-46583)

• After a high availability failover, the task to reconfigure the compute cluster may not start. (VSTOR-43841)

• An SSD disk is not recognized if it is managed by specific disk controllers. (VSTOR-36155)

• The node maintenance mode does not evacuate resources as expected. (VSTOR-47350)

• When a node enters maintenance, virtual machines that failed to be migrated are skipped. (VSTOR-48295)

• A virtual machine with an ejected PCI-device fails to live migrate. (VSTOR-47907)

• Snapshot creation can take too long. (VSTOR-48293)

• After deleting a virtual machine, its volume stays attached. (VSTOR-48099)

• The default storage policy is not selected by default. (VSTOR-45826)

6. Installing the Update

You can upgrade Virtuozzo Hybrid Infrastructure 4.7 to 5.0 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.

1. Overview

This update synchronizes the MDS state, which can be unsynchronized due to previous issues, and provides important fixes for the FUSE, object storage, and compute services.

2. Bug Fixes

• Synchronize the MDS state during an upgrade. (VSTOR-49963)

• Fix the upgrade error “30s timeout elapsed while waiting for a response from the shaman master instance.” (VSTOR-50181)

• A stability fix for FUSE. (VSTOR-49913)

• Stability fixes for object storage. (VSTOR-49865, VSTOR-49709)

• Fix the maintenance mode pre-check for a VM evacuation. (VSTOR-49714)

3. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required.

The source of this advisory is available in the JSON file.

1. Overview

This update provides a stability fix for the metadata service.

2. Bug Fixes

• A stability fix for the metadata service. (VSTOR-49572)

3. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required.

The source of this advisory is available in the JSON file.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• Cannot deploy the compute cluster with a flat physical network if the untagged network interface has VLAN interfaces. (VSTOR-49253)

• A vGPU may disconnect from a virtual machine after the VM shutdown and start. (VSTOR-49207)

• The VNC console may not open if there are many running virtual machines. (VSTOR-49169)

• An update may fail due to the shaman timeout after re-electing the master MDS service. (VSTOR-49166)

• Stability and performance improvements. (VSTOR-49066, VSTOR-46992, VSTOR-48877)

3. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required.

The source of this advisory is available in the JSON file.

1. Overview

This update provides bug fixes for the upgrade procedure with the deployed compute cluster.

2. Bug Fixes

• Entering maintenance fails due to VM migration errors. (VSTOR-48639, VSTOR-45993)

3. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required.

The source of this advisory is available in the JSON file.

1. Overview

This update provides new features, as well as bug fixes and improvements.

2. New Features

• [Compute service] Support for virtual GPU devices inside virtual machines. In this release, we support only NVIDIA GPU cards.

• [Object storage] Added new metrics for advanced monitoring to integrated Prometheus: S3 bucket size and S3 user space consumption.

3. Bug Fixes

• Fixed the false-positive alert “MN backup does not exist.” (VSTOR-48360)

• After a power failure of all nodes in the high availability cluster, the virtual IP address may be unset. (VSTOR-48337)

• Creating a VLAN interface over another VLAN interface should be disabled. (VSTOR-48287)

• Cannot promote the secondary backup storage to primary in a geo-replication configuration in the admin panel. (VSTOR-48269)

• A storage policy may not be applied to compute volumes. (VSTOR-48051)

• In some cases, backups may consume additional storage space because archive garbage is not collected. (VSTOR-48012)

• After an update from version 4.6 to 4.7, some actions may fail with the error “Failed to verify the account server API version.” (VSTOR-47782)

• Fixed high availability for load balancers. (VSTOR-47760)

• Fixed the false-positive alert “A CS service has too big journal” when the storage service is located on an HDD drive. (VSTOR-47723)

• If an S3 cluster is misconfigured, the I/O activity charts in the admin panel may have gaps due to a slow metric collection. (VSTOR-47651)

• Incorrect usage is reported for a system disk in case of software RAID1. (VSTOR-47346)

• Backup Gateway accepts revoked certificates. (VSTOR-47253)

• Failed to migrate a virtual machine if its disk has a snapshot with checkpoints. (VSTOR-47273)

• Cannot create a project in the admin panel if a storage policy name includes a colon. (VSTOR-47242)

• Incorrect eligibility checks were performed for an update that does not require a reboot. (VSTOR-47128)

• Fixed a problem with the configuration of Intel SR-IOV network adapters for PCI passthrough. (VSTOR-48460)

• Stability and performance improvements. (VSTOR-48333, VSTOR-48178, VSTOR-47765, VSTOR-47752, VSTOR-47497, VSTOR-47411, VSTOR-47220)

4. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required.

The source of this advisory is available in the JSON file.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a wide range of new features that enhance service providers’ interoperability and help expand their services. The improvements cover compute services, object storage, core storage, monitoring, high availability for the management node, updates, and the user interface. Additionally, this release delivers stability improvements and addresses issues found in previous releases.

2. New Features

• [Compute service] Online resize of virtual machines. It is now possible to scale up a running virtual machine by adding more CPU and RAM resources to it with no downtime. CPU and RAM hot plug is configured for self-service users per domain.

• [Compute service] Ability to attach a virtual CD-ROM to a virtual machine. By mounting an ISO image to a virtual machine as a virtual CD-ROM, users can install additional software or restore a guest operating system.

• [Compute service] Rescue mode for Windows and Linux virtual machines from an ISO image. As a part of the rescue mode, you can boot any virtual machine from a recovery CD-ROM or a bootable ISO image.

• [Compute service] IPv6 support for virtual machines. Virtual machines can now be assigned IPv6 addresses. IPv6 subnets are available only for physical compute networks. In this release, IPv6 addresses are not supported for load balancers and Kubernetes clusters.

• [Compute service] PCI passthrough to virtual machines. You can accelerate a virtual machine by attaching a host PCI device to it. The following PCI devices are supported: a physical GPU card, an HBA adapter, and a virtual/physical function of an SR-IOV capable network card.

• [Compute service] Support for Kubernetes versions 1.20 and 1.21. Added the full support of Kubernetes versions 1.20 and 1.21 for deploying and upgrading Kubernetes clusters.

• [Compute service] Support for the baseline AMD EPYC CPU model. The baseline EPYC CPU model can be set for compute cluster. Management of the CPU model is available only in the command-line interface.

• [Compute service] Renewal of Kubernetes cluster certificates. Added the possibility to renew Kubernetes cluster CA certificates when they expire. Certificate renewal is available only in the command-line interface.

• [Compute service] Outgoing traffic usage statistics. Gathering statistics about outgoing traffic usage for metering and billing purposes.

• [Object storage] Storage usage limit. It is now possible to set a quota on S3 storage usage per bucket or per user. In this release, limiting S3 storage usage is available only via API.

• [Core storage] Improved disk troubleshooting and management. Improved user experience with disks, to provide better visibility of a storage cluster configuration, including storage service settings, caching, and checksumming. Additionally, the diagnostic information provided about disk failures helps to detect hardware issues faster.

• [Monitoring] Cluster interconnectivity check. Introduced an automatic, periodic check of network connectivity between cluster nodes, to provides information and raises alerts in real time in case of network issues.

• [High availability of the management node] Management node backup in a highly available configuration. The management node database is now automatically backed up in a cluster with high availability enabled. Such a backup brings additional protection for a highly available configuration and can be restored in case of issues with the management node database by using the Virtuozzo Support service.

• [Updates] Accelerated cluster updates. Updates to newer versions are performed faster thanks to the optimization of a kernel update process and a quicker node reboot during an update.

• [User interface] Notification center. Improved user experience with the admin and self-service panels by aggregating events that happened during a user session in the notification center.

3. Important Notes

• Kubernetes version 1.18 is deprecated. Update to the currently supported version 1.19.

• Kubernetes version 1.19 will be deprecated in future releases. Use the latest supported versions 1.20 and 1.21 to plan your containerized environments.

4. Bug Fixes

• The S3 gateway service fails under certain circumstances. (VSTOR-46822)

• Unable to delete two load balancers at a time. (VSTOR-43299)

• Unable to delete a user when CHAP is disabled for a target group. (VSTOR-45836)

• A VLAN interface automatically converts to an OVS bridge on a node added to a cluster where other nodes’ interfaces have access to the same VLAN. (VSTOR-46020)

• The DHCP agent may stop functioning. (VSTOR-44282)

• Unable to delete a snapshot if the previous snapshot is missing. (VSTOR-44146)

• Failed to start a virtual machine after an incorrect migration rollback. (VSTOR-45239)

• A floating IP address becomes unavailable after changing the external network for a virtual router. (VSTOR-45294)

• Cannot create a virtual machine with two network interfaces if one of the networks has IP management disabled. (VSTOR-45823)

• The metric endpoint works too slow for a load balancer with many pools and members. (VSTOR-44011)

• Unable to create a Kubernetes cluster if a placement is not specified. (VSTOR-44915)

• Cannot start a virtual machine after it crashed during the migration. (VSTOR-45247)

• Unable to delete a Kubernetes cluster if a network interface is attached to its worker node with an assigned security group. (VSTOR-44945)

5. Known Issues

• No error is displayed in the self-service panel if the compute cluster does not have enough resources to create a Kubernetes cluster. (VSTOR-43174)

• Cannot create a Kubernetes cluster in a network without the DHCP server. (VSTOR-38799)

• Failed to migrate a virtual machine during a compute cluster upgrade. (VSTOR-45662)

• After detaching a volume, it cannot be attached to another virtual machine because it is still shown in the previous VM configuration. (VSTOR-41107)

• An error message is not shown after a failed VM live migration. (VSTOR-39553)

• When the networking service experiences issues connecting to the messaging queue, it leaks memory. (VSTOR-34737)

• Unable to delete large volume snapshots. (VSTOR-41372)

• Cannot start a virtual machine after an incomplete migration. (VSTOR-43837)

• The compute cluster fails after adding nodes with newer versions to the high availability configuration. (VSTOR-46583)

• After a high availability failover, the task to reconfigure the compute cluster may not start. (VSTOR-43841)

• An SSD disk is not recognized if it is managed by specific disk controllers. (VSTOR-36155)

6. Installing the Update

You can upgrade Virtuozzo Hybrid Infrastructure 4.6 to 4.7 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.

1. Overview

This update provides bug fixes and improvements.

2. Bug Fixes

• Incorrect storage usage values are reported. (VSTOR-45618)

• Some users cannot access S3 via the user panel. (VSTOR-45724)

• Detection of slow disks works inside virtual environments. (VSTOR-44252)

• The “default” storage policy should be selected for new volumes by default. (VSTOR-45841)

• Cannot create a load balancer if the amphora image is assigned a placement or all compute nodes are in placements. (VSTOR-45372)

• The ‘kubectl port-forward’ command does not work without the socat binary. (VSTOR-45506)

• Stability and performance improvements. (VSTOR-44462, VSTOR-44969, VSTOR-45323, VSTOR-45808, VSTOR-45884, VSTOR-45923)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The source of this advisory is available in the JSON file.

1. Overview

This update provides new features, as well as bug fixes and improvements.

2. New Features

• Update of Kubernetes versions. You can manually initiate a Kubernetes cluster update to a newer version when it becomes available.

• Creating virtIO disks for virtual machines. To boost I/O performance of virtual machines, you can configure their boot disks to use the virtIO bus. This configuration is available only in the command-line interface.

• Node selection during an update. It is now possible to update cluster nodes in a particular order, for example, to reduce maintenance windows for hosted services.

• Additional maintenance mode options. Now, you can configure maintenance mode options for nodes during an update. Namely, you can decide how to live migrate virtual machines when a node enters the maintenance mode.

3. Bug Fixes

• The MDS service may be unstable under a high load condition. (VSTOR-45315)

• A deadlock is possible between atomic and non-atomic commands in the iSCSI kernel module. (VSTOR-43126)

• The “Disk write cache is enabled” alert does not disappear after disabling disk write cache. (VSTOR-45236)

• Stale Open vSwitch flows may break a VM network after a live migration. (VSTOR-45194)

• Failed to move a network with the “OSTOR private” traffic type from one interface to another. (VSTOR-45077)

• Failed to update to version 4.6 if a network has no assigned traffic types. (VSTOR-44870)

• Cannot failover a highly available load balancer if both its amphora VMs are in the error state. (VSTOR-44768)

• Some I/O operations may hang in a storage cluster with erasure coding. (VSTOR-45111)

• A backup may fail with the error “[Archive Server]: storage request timeout.” (VSTOR-44747)

• Detection of slow disks works inside virtual environments. (VSTOR-44252)

• It is possible to select a routed network during a VM creation in the self-service panel. (VSTOR-44138)

• A VM has no network after the network reconfiguration. (VSTOR-43815)

• Invalid quota usage is shown in the vinfra command output. (VSTOR-43648)

• Stability and performance improvements. (VSTOR-44912, VSTOR-44747, VSTOR-44704, VSTOR-44484, VSTOR-44325, VSTOR-44094)

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 JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2021-039.json.

1. Overview

This update provides bug fixes and improvements.

2. Bug Fixes

• With backup storage geo-replication, promotion to the primary cluster fails with the error: “name ‘payload’ is not defined.” (VSTOR-44043)

• A deadlock is possible between atomic and non-atomic commands in the iSCSI kernel module. (VSTOR-43126)

• It is not possible to open some files in the storage. (VSTOR-44388)

• Stale Open vSwitch flows may break a VM network after a live migration. (VSTOR-45194)

• Complete multipart upload requests might fail for uploads with more than 9900 parts. (VSTOR-44677)

• A backup may fail with the error “[Archive Server]: storage request timeout.” (VSTOR-44747)

• Stability and performance improvements. (VSTOR-44128, VSTOR-44346, VSTOR-44912, VSTOR-42858, VSTOR-44998, VSTOR-45373, VSTOR-39689, VSTOR-44484, VSTOR-44704, VSTOR-41892, VSTOR-43142, VSTOR-43747, VSTOR-43756, VSTOR-43838, VSTOR-44007)

3. 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 JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2021-038.json.

1. Overview

This update provides stability fixes for the storage, Backup Gateway and object storage services.

2. Bug Fixes

• A stability fix for the storage service. (VSTOR-44694)

• A stability fix for the Backup Gateway service. (VSTOR-44859)

• Complete multipart upload requests might fail for uploads with more than 9900 parts. (VSTOR-44677)

• abgw-setting.service is in the failed state. (VSTOR-44601)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update. However, if you experience the VSTOR-44694 issue, reboot upgraded nodes manually, one at a time.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2021-035.json.

1. Overview

This update provides stability fixes for the storage services.

2. Bug Fixes

• It is not possible to open some files in the storage. (VSTOR-44388)

• A stability improvement for the storage service. (VSTOR-44346)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update. If, however, you experience the issue described in VSTOR-44388, reboot upgraded nodes manually, one at a time.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2021-033.json.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a wide range of new features that enhance service providers’ operability. The improvements cover compute services, object storage, monitoring, security, localization, and the user interface. Additionally, this release delivers stability improvements and addresses the issues found in previous releases.

2. New Features

• [Compute] Placement improvements:

  • Soft mode for placements. The new mode allows you to schedule a virtual machine on a node that is assigned at least the same placements as the virtual machine. Together with the hard mode, this mode increases flexibility of placing virtual machines on compute nodes.

  • Placements for flavors. Now, placements can be assigned not only to images, but also to flavors. Image placements allow you to distribute virtual machines according to image properties, such as a guest operating system. Placements assigned to flavors, in their turn, help to distribute virtual machines according to hardware capabilities, such as a high-frequency CPU model. In this release, you can assign a placement to a flavor in the command-line interface.

• [Compute] Support for Kubernetes version 1.19. The new version can be used to create and manage Kubernetes clusters.

• [Compute] Online extension of virtual machine volumes. Volume extension is enabled for running virtual machines.

• [Compute] Soft anti-affinity policy for placing Kubernetes instances. Instances with Kubernetes services will be distributed across different nodes in the compute cluster by default. If there are not enough compute nodes, some instances can be placed on the same node.

• [Compute] Multiple IP addresses per VM network interface. Now, it is possible to set multiple IP addresses for a virtual machine’s network interface.

• [Compute] Custom branding per domain. Personal branding theme, which is displayed in the self-service panel, can be configured for each domain separately.

• [Object storage] Object storage classes. It is now possible to use up to four different storage classes for applications with specific performance and redundancy requirements. In this release, management of storage classes is available only in the command-line interface.

• [Object storage] Object storage stability improvements. The integrity of object storage metadata is ensured by automatic built-in metadata backups.

• [Object storage] Object storage accounts. Each S3 user can now have multiple accounts, which are isolated containers for S3 user buckers with defined usage limits.

• [Monitoring and alerting] Advanced core and object storage monitoring. Added more metrics and alerts for core and object storage to the integrated Prometheus monitoring system, to monitor storage parameters centrally, as well as detect and fix issues faster.

• [Security] Embedded firewall rules for outbound connections. Configurable outbound firewall rules help to secure your nodes and ensure that they can reach only allowed external resources. In this release, management of outbound firewall rules is available only in the command-line interface.

• [User interface] New screens for node disks and network interfaces. Improved user experience with disks and network interfaces of infrastructure nodes. Introduced new properties for disks and network interfaces. Added two new dashboards for disks, to display current usage and read/write latency.

• [Updates] Improved update speed. In future releases, large clusters can be updated up to three times faster due to enhanced maintenance mode for storage components and more efficient virtual machine migration.

• [Localization] Turkish language localization for the admin and self-service panels.

3. Important Notes

• Kubernetes version 1.15 is deprecated. Use the currently supported version 1.19 to plan your containerized environments.

• Kubernetes version 1.18 will be deprecated in future releases. Use the currently supported version 1.19 to plan your containerized environments.

• For object storage, the minimum TLS protocol version is changed to TLS 1.2, to comply with PCI DSS requirements.

4. Bug Fixes

• Unable to release a cluster node due to a conflicting task. (VSTOR-43708)

• An incorrect confirmation message is displayed when releasing a node from the S3 cluster. (VSTOR-43528)

• A Kubernetes cluster might have a coreDNS deployment with 0 replicas. (VSTOR-43267)

• Cannot create a security group for load balancers while deploying a Kubernetes cluster. (VSTOR-43204)

• Unable to remove a VM volume in the reserved or attaching state. (VSTOR-43154)

• An OVS bridge is created on a new compute node when the “VM public” traffic type is assigned to its VLAN interface. (VSTOR-43088)

• Prometheus is started on every cluster node. (VSTOR-42712)

• Connectivity checks fail with bond interfaces. (VSTOR-41925)

• A network interface with no IP address can be assigned the “VM backups” traffic type. (VSTOR-40922)

• Proxied requests between certain nodes fail with a timeout. (VSTOR-40334)

• A VMDK image is not converted to the QCOW2 format while uploading in the admin panel. (VSTOR-39535)

• Change the policy for Kubernetes and load balancer virtual machines in the HA mode from anti-affinity to soft anti-affinity. (VSTOR-30671)

• Improvements for management node HA. (VSTOR-43646, VSTOR-43178, VSTOR-42564)

• Update improvements. (VSTOR-43180, VSTOR-38763)

5. Known Issues

• No error is displayed in the self-service panel if the compute cluster has not enough resources to create a Kubernetes cluster. (VSTOR-43174)

• An error message is not shown after a failed VM live migration. (VSTOR-39553)

• Unable to delete large volume snapshots. (VSTOR-41372)

• An SSD disk is not recognized if it is managed by specific disk controllers. (VSTOR-36155)

• Cannot cancel a file upload in the user interface of an S3 bucket. (VSTOR-22390)

6. Installing the Update

You can upgrade Virtuozzo Hybrid Infrastructure 4.5 to 4.6 in the SETTINGS > UPDATE section. 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 JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2021-029.json.

1. Overview

This update provides fixes for the storage and compute services.

2. Bug Fixes

• Load balancer members are not displayed in the self-service panel. (VSTOR-43250)

• A Kubernetes VM’s system disk may be out of space due to Podman logs. (VSTOR-43236)

• Increase a limit for remote console ports. (VSTOR-41499)

• A stability improvement for the storage service. (VSTOR-43393)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section. A reboot is not required to complete the upgrade if you are upgrading from build 4.5.0-289. If you have an earlier version, upgraded nodes will be automatically rebooted, 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 JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2021-024.json.

1. Overview

This update provides fixes for the admin and self-service panels.

2. Bug Fixes

• Unable to add a network interface to an existing VM in the self-service panel. (VSTOR-42074)

• Added a message about disabling security groups for a VM network interface. (VSTOR-42954)

• A system administrator cannot edit spoofing protection settings for a project in a non-default domain. (VSTOR-42688)

3. Installing the Update

You can install the update in the SETTINGS > UPDATE section. A reboot is not required to complete the upgrade if you are upgrading from build 4.5.0-289. If you have an earlier version, upgraded nodes will be automatically rebooted, 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 JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2021-019.json.

1. Overview

This update provides stability fixes for the Backup Gateway, block storage, storage and compute services.

2. Bug Fixes

• Fixes for Gnocchi-related issues after an HA event. (VSTOR-41817, VSTOR-41874)

• Stability and performance improvements. (VSTOR-42372, VSTOR-42297, VSTOR-42009, VSTOR-41982, VSTOR-41706, VSTOR-40814)

3. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to complete the upgrade if you are upgrading from the build 4.5.0-289. If you have an earlier version, upgraded nodes will be automatically rebooted, 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 JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2021-018.json.

1. Overview

This update provides a new feature, as well as bug fixes and improvements.

2. New Features

• Extended the cipher configuration possibilities for Backup Gateway. (VSTOR-38415)

3. Bug Fixes

• Forcing an update may fail after the first attempt due to the already updated certificate management layout. (VSTOR-41271)

• Fixed IQN validation. (VSTOR-41577)

• The object storage services may not work in the SPLIT state. (VSTOR-41403)

• Increased the number of VNC ports per node from 100 to 180. (VSTOR-41204)

• Fixed the Backup Gateway re-registration procedure. (VSTOR-41047)

• Incorrect ownership of the Gnocchi directory. (VSTOR-40983)

• Non-standard characters in a file name may lead to problems with Backup Gateway data stored in Azure. (VSTOR-39824)

• Stability and performance improvements. (VSTOR-41578, VSTOR-41112, VSTOR-40914, VSTOR-41758, VSTOR-41661, VSTOR-41615, VSTOR-41482, VSTOR-41421, VSTOR-41104)

4. Installing the Update

You can install the update in the SETTINGS > UPDATE section. A reboot is not required to complete the upgrade if you are upgrading from the build 4.5.0-289. If you have an earlier version, upgraded nodes will be automatically rebooted, 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 JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2021-016.json.

1. Overview

This update provides stability fixes for storage services.

2. Bug Fixes

• Detaching a LUN from an SCST target may lead to soft lockup under certain circumstances. (VSTOR-41460)

• Stability improvements for the storage service. (VSTOR-41301, VSTOR-41172, VSTOR-41272)

3. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is required to complete the update. Updated 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 JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2021-013.json.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a wide range of new features that enhance the end-user experience and service providers’ interoperability. The improvements cover compute services, networking, storage core, monitoring, and the administrative user interface. Additionally, this release delivers stability improvements and addresses the issues found in previous releases.

2. New Features

• [Compute] Allowing domain administrators to manage projects. Domain administrators can now manage projects within the assigned domain. With this permission, domain administrators can perform operations with projects by using the OpenStack command-line tool.

• [Compute] Support for Kubernetes version 1.18. Kubernetes version 1.15 is no longer available in the self-service panel. Now, all management operations with Kubernetes clusters are supported for version 1.18.

• [Compute] Volume size statistics per storage policy. Usage statistics for volumes can be aggregated per storage policy.

• [Compute] Memory overcommitment. RAM overcommitment enables provisioning virtual machines with more RAM than the amount of physical RAM available on all compute nodes. The RAM overcommitment ratio is set for the entire compute cluster. This feature improves compute cluster efficiency for hybrid cloud disaster recovery.

• [Compute] Persistent SSL certificate. A custom SSL certificate used for secure communication with a highly available cluster will not be overwritten after changing the high availability configuration.

• [Compute] New balancing protocol for load balancers. Added support for the UDP protocol for load balancers in the self-service panel.

• [Compute] Security groups support. Cloud administrators can control incoming and outgoing traffic to virtual machines by assigning virtual machines to security groups. A security group is a set of firewall rules that are applied to virtual network adapters.

• [Networking] Inbound firewall rules for nodes. Cluster administrators are now able to filter incoming traffic on cluster nodes by using fully customizable access rules. Configuring inbound firewall rules help prevent access from untrusted sources to the cluster. The rules applied on a specific network or traffic type can limit incoming traffic from single IP addresses and subnet ranges.

• [Storage core] Fencing of slow and pre-failed storage disks. Storage disks with low performance are now automatically detected and marked as slow. Slow disks are fenced from the cluster I/O, to avoid degrading cluster performance. After receiving an alert, cluster administrators can troubleshoot the hardware problem or replace the slow disk before its failure.

• [Monitoring and alerting] Fine-grained logging for virtual machines. Added more details to the system log. Now, it contains full log messages and audit log entries of operations with virtual machines.

• [UI] Node status online detection. Improved the internal mechanism to determine node availability. Nodes are now displayed in the admin panel in their current state without any delay. When a node status changes, an alert is generated and stored in the alert log.

• [Other enhancements] Worker groups support for Kubernetes cluster. Added Kubernetes worker groups that enable creating multiple worker nodes with different number of CPUs and amount of RAM for a single Kubernetes cluster. Workers with different flavors help meet system requirements of applications running in Kubernetes clusters.

3. Important Notes

• Kubernetes version 1.15 will be deprecated in future releases. Use the currently supported version 1.18 to plan your containerized environments.

• Fibre Channel bus adapters are no longer supported. We are discontinuing support of Fibre Channel as an option while creating iSCSI target groups.

• Legacy iSCSI targets (created in 2.4 and earlier versions) are deprecated. We are discontinuing support for TGTD-based iSCSI targets. Such targets are marked in the admin panel as legacy because they do not support the ALUA mode and their LUNs are not highly available. To enable high availability for them, detach a volume from an older target group and attach it to a newly created one.

• Erasure coding redundancy change. Changing the redundancy scheme is only possible for backup storage. If you have ever changed the encoding scheme for your backup storage cluster with the help of the technical support team, re-apply your redundancy settings in version 4.5 to ensure that all data was encoded.

4. Bug Fixes

• [Updates] Failed to complete an upgrade from version 3.5.5 due to an unsafe PostgreSQL restart. (VSTOR-39354)

• [Updates] A software update task may block recovering of other tasks. (VSTOR-39344)

• [Updates] Validation fails while upgrading a high availability cluster from version 4.0.0-734. (VSTOR-37858)

• [Compute service] Fixed an issue when the load balancer service runs using WSGI application. (VSTOR-37514)

• [Compute service] Failed to convert a VMDK image to the QCOW2 format while uploading via the admin panel. (VSTOR-39535)

• [Compute service] The load balancer service uses public endpoints instead of the internal ones. (VSTOR-37396)

• [Compute service] noVNC 1.1.0 does not provide a token in a request to websockify. (VSTOR-37855)

• [Compute service] The networking service crashed unexpectedly because the libvirt domain was running on a wrong node. (VSTOR-40363)

• [Compute service] The billing metering service upgrade fails if ‘gnocchi-storage-config’ is empty. (VSTOR-38060)

• [Compute service] PostgreSQL fails when the root partition has insufficient free space. (VSTOR-37898)

• [Compute service] Due to stale allocations, resource providers cannot be deleted. (VSTOR-37844)

• [Compute service] The billing metering service creates a large number of small files on the storage, thus affecting the MDS performance. (VSTOR-39003)

• [Compute service] The orchestration service uses a public keystone endpoint for internal communications. (VSTOR-37793)

• [Compute service] Trial license keys for six months and one year are reported as invalid. (VSTOR-37289)

• [Compute service] The number of subscriptions in the Redis server may become too large. (VSTOR-37487)

• [Compute service] The compute creation wizard does not check availability for load balancer and Kubernetes repositories. (VSTOR-33894)

• [Compute service] Load balancer creation fails if a VM without an IP address is added to the member list. (VSTOR-39489)

• [Compute service] The block storage service stops sending lock heartbeats after any connection issue. (VSTOR-37608)

• [Compute service] Cannot change the IP configuration of OVS bridge interfaces. (VSTOR-37399)

• [User interface] Impossible to resize more columns in the table components. (VSTOR-31985)

• [User interface] The management node does not return a clear backup status if high availability is enabled. (VSTOR-32254)

• [Installer] In the installation wizard, it is not possible to turn on the network time if it was turned off on the previous step. (VSTOR-30581)

• [Monitoring and alerting] During detection of a node availability, an incorrect schedule interval is used to calculate expiration date. (VSTOR-33502)

5. Known Issues

• The deployment of compute add-on services fails due to unset environment variables. (VSTOR-30850)

• A Kubernetes cluster cannot be created on a physical network without DHCP. (VSTOR-38799)

• The built-in keystone authorization does not work in Kubernetes. (VSTOR-32458)

• The soft anti-affinity policy for Kubernetes and load balancers VMs is used in the high availability mode. (VSTOR-30671)

• A placement cannot be selected after VM creation. (VSTOR-40292)

• An unclear error message in shown in the admin panel during compute cluster creation. (VSTOR-33893)

• No error message is shown when a live migration fails. (VSTOR-39553)

• An SSD disk is not recognized if it is managed by specific disk controllers. (VSTOR-36155)

• An automatic update during node installation can break checking for updates. (VSTOR-38763)

• An SNMP trap is not sent when a network interface is down. (VSTOR-32192)

6. Installing the Update

You can upgrade Virtuozzo Hybrid Infrastructure 4.0 to 4.5 in the SETTINGS > UPDATE section. 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 JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2021-007.json.

1. Overview

This update provides a security fix.

2. Bug Fixes

• Fix for a vulnerability in sudo known as CVE-2021-3156. (VSTOR-40614)

3. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2021-005.json.

1. Overview

This update provides fixes for the Backup Gateway and compute services.

2. Bug Fixes

• A stability fix for Backup Gateway. (VSTOR-39857)

• Fix incorrect MTU on a flat network when different MTUs set on interfaces in the same network. (VSTOR-38770)

• Fix data collection after a graceful reboot of the current management node. (VSTOR-40118)

• Fix a compute networking issue when a floating IP gateway port has a public IP address. (VSTOR-40256)

3. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2021-003.json.

1. Overview

This update provides a new feature, as well as bug fixes and improvements.

2. New Features

• Network QoS policies support. (VSTOR-34627)

3. Bug Fixes

• A non-admin user is unable to create volumes from the command line. (VSTOR-38583)

• Enabled geo-replication on Backup Gateway with an S3 backend may result in a deadlock. (VSTOR-38785)

• The database replication alert is not cleared after the problem is gone. (VSTOR-38458)

• Cannot create a load balancer with an IP address from the allocation pool. (VSTOR-38330)

• Dashboards have empty data if an S3 node is offline. (VSTOR-38281)

• Setting a DNS name for the compute API may not work if the compute cluster was deployed on an older version of the product. (VSTOR-38242)

• Geo-replication stopped working unexpectedly. (VSTOR-38233)

• Unable to update to version 4.0 if a network with the “VM public” traffic type is not accessible from cluster nodes. (VSTOR-38217)

• A retry of the last node update to version 4.0 fails with the error: “Missing 1 required positional argument: ‘resume_required’”. (VSTOR-38091)

• A retry of an update to version 4.0 fails with the error: “NoneType object is not iterable.” (VSTOR-38016)

• A floating IP is not reachable when multiple routers are used for one network. (VSTOR-38006)

• A project list is not shown on the “Edit network access” screen in the Firefox browser. (VSTOR-37964)

• A remote console does not work if requested directly by using the Openstack commands. (VSTOR-36520)

• After a failed attempt to remove an old snapshot, the VM storage size is shown as zero and the VM is marked as failed in the admin panel. (VSTOR-37728)

• Open vSwitch bridge interfaces cannot be edited or deleted, even if they are no longer used in compute networking. (VSTOR-37632)

• After trying to manage load balancers via the admin panel or vinfra, the “Gateway Timeout” error appears due to stuck or long previous requests. (VSTOR-37619)

• The admin panel does not accept a license with an unlimited expiration date. (VSTOR-37436)

4. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-073.json.

1. Overview

This update provides bug fixes and improvements.

2. Bug Fixes

• The stat command may report wrong size for files with erasure coding. (VSTOR-38028)

• Editing an NFS export could set a wrong SecType and prevent the export from being mounted. (VSTOR-37868)

• Stability improvements for the storage service. (VSTOR-38102, VSTOR-37639, VSTOR-37478)

3. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-065.json.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure provides a wide range of new features that enhance the end-user experience and service providers’ interoperability. The improvements cover networking, storage core, appliance, object storage, monitoring, performance charts, and localization. Additionally, this release delivers stability improvements and addresses the issues found in previous releases.

2. New Features

• [Compute] Rescue mode for virtual machines. Rescue mode provides a mechanism to access the virtual machine’s boot volume in case the virtual machine experiences boot problems.

• [Compute] Distributed virtual router. The virtual routing architecture has been changed from centric to distributed (across all compute nodes).

• [Compute] QoS policies for virtual machine volumes. The storage policy has been extended with additional parameters that define the IOPS and bandwidth limits of virtual machine volumes.

• [Compute] Paging for compute and common objects in the admin panel. Improved the admin panel performance for large numbers of virtual machines.

• [Compute] VLAN-based network management for virtual machines. Simplified the process of creating VLAN-based networks for virtual machines.

• [Compute] More supported guest operating systems. Added support for Debian 10, CentOS 8, and Ubuntu 20.04.x.

• [Integration] CloudBlue Connect. Service providers can now integrate with the CloudBlue Connect billing and provisioning system. Integration supports both the flat and pay-as-you-Go billing models.

• [Networking] Exclusive traffic type reassignment and cluster IP address change. It is now possible to change the configuration of exclusive traffic types or IP addresses in the cluster. This is needed when the node IP address has changed but network topology remains the same, or if the network subnet has changed. It is also possible now to reassign a service traffic type when a customer wants to relocate a service to another network (for example, move the “Storage” traffic type to a dedicated network).

• [Core storage] Node locations as failure domains. A failure domain defines a scope (a location) within which services may go down together. Now nodes can be assigned to specific locations: rooms, rows, and racks. Locations provide redundancy among failure domains. This gives an additional, flexible way to service providers to utilize the available hardware more efficiently while delivering high availability.

• [Core storage] Improved latency and performance. Kernel and networking optimizations.

  • Erasure coding is now available for running virtual machines.

  • Erasure coding self-healing now has less impact on performance.

  • The storage networking subsystem has been improved for lower I/O latencies and CPU consumption.

  • RDMA performance and stability have been improved. RDMA is now a production-ready feature.

• [Object storage] S3 geo-replication improvements.

  • Improved security for geo-replication (bucket ACLs).

  • User-level and bucket-level customization of S3 geo-replication.

• [Object storage] S3 bucket access log. Now the records of requests to a bucket can be provided and stored in another bucket. In addition, end users can now enable the access log via Amazon S3 API and get detailed information about the objects in their buckets.

• [Monitoring and alerting] A dashboard for S3 performance and statistics charts. You can now monitor:

  • Services, including S3 GW, NS, OS services availability, rate of operational requests, bandwidth, as well as GET and PUT latencies.

  • Geo-replication, including service availability, error rates, replication backlog, queue depth, and bandwidth.

• [Monitoring and alerting] Dashboard for performance and statistics charts for NFS. You can now monitor the availability of NFS servers and services, usage, shares, exports, latency, IOPS, and bandwidth.

• [Localization] Chinese localization for the admin panel and documentation.

• [Localization] Japanese localization for the admin panel and documentation.

• [Other enhancements] Disabled pNFS. pNFS is now disabled by default and cannot be enabled for any forthcoming use cases.

3. Bug Fixes

• [Compute networking] After virtual router creation, the internal IP address goes down. (VSTOR-33859)

• [Compute service] The docker service has no log rotation. (VSTOR-32173)

• [Compute service] Floating IPs and virtual routers are not available after removing nodes from the compute cluster. (VSTOR-30506)

• [Compute service] The dashboard service may get stuck in a restart loop. (VSTOR-32120)

• [Compute service] Storage space usage in a project is calculated incorrectly for volumes with snapshots after their storage policy has been changed. (VSTOR-34054)

• [Compute service] Kubernetes cluster creation hangs if it cannot access the public Docker hub. (VSTOR-32238)

• [Compute service] The noVNC console sends duplicate keystrokes to Windows virtual machines. (VSTOR-30975)

• [Compute service] Unable to remove a load balancer while in the “deployment_failed” state. (VSTOR-35034)

• [Compute service] Cannot deploy the compute cluster after reassigning the “Internal management” traffic type. (VSTOR-33202)

• [Compute service] Load balancers are in the “error” state after the update to version 3.5.1. (VSTOR-32237)

• [Core storage] The archive server client crashes during reconnection. (VSTOR-33017)

• [Core storage] Links between a frontend chunk object and an internal journal file system object may be broken. (VSTOR-33577)

• [Core storage] Avoid unnecessary reconfiguration of allocated disks. (VSTOR-31951)

• [Core storage] Storage services deployed on the same disk generate an exception in logs. (VSTOR-32782)

• [Core storage] The same disk can be assigned twice in two parallel bulk assign tasks. (VSTOR-33012)

• [Core storage] After assigning roles to a node disk during the cluster creation and reassigning them afterwards, the node may appear as “Failed.” (VSTOR-30931)

• [Admin panel high availability] An unnoticed failure to replicate the management node database may cause the compute metadata loss. (VSTOR-34723)

• [Backup storage] The Backup Gateway geo-replication command breaks compatibility. (VSTOR-34891)

• [Backup storage] The Backup Gateway utility does not correctly accept a password containing spaces from stdin. (VSTOR-32028)

• [Object storage] Unable to start replication of a bucket with a large number of objects. (VSTOR-27097)

• [Object storage] It is possible to remove the single node with the S3 configuration from the S3 cluster. (VSTOR-30376)

• [Object storage] The NFS remains active and running after the node has been released from an NFS cluster. (VSTOR-30622)

• [Updates] The upgrade from version 2.5 to 3.0 fails due to the installed GeoIP module. (VSTOR-31734)

• [Updates] Failed to download updates due to a newer version on the update server. (VSTOR-35014)

• [Updates] Under certain circumstances, downloading packages may fail. (VSTOR-33446)

• [Updates] After an update with enabled high availability, the admin panel may become unavailable. (VSTOR-26542)

• [Installer] During installation, the specified hostnames are converted to lowercase. (VSTOR-35352)

• [User interface] The problem report location is missing if there is no Internet connection. (VSTOR-34770)

• [User interface] Improve the text for the “Incorrect journaling settings” alert. (VSTOR-34387)

• [User interface] Email notifications sent via SMTP do not contain the cluster name. (VSTOR-32933)

• [User interface] Unable to interpret special symbols in passwords. (VSTOR-30216)

• [User interface] Several services are not configured to restart automatically. (VSTOR-20993)

• [User interface] The old product version is displayed after a successful update. (VSTOR-25662)

• [User interface] License capacity is shown as ”Total” in the physical space widget. (VSTOR-27237)

• [User interface] A 25 Gbit network card is reported as a 10 Gbit network card in the admin panel. (VSTOR-9422)

• [User interface] Redis stores superfluous failed task metadata. (VSTOR-36654)

• [User interface] NFS4 is not selected by default in the admin panel. (VSTOR-33809)

• [User interface] Network counters differ in the admin panel and inside a load balancer virtual machine. (VSTOR-32756)

• [User interface] There is no “Security” field validation when saving email settings. (VSTOR-14465)

• [User interface] Check boxes are too bright on very light displays. (VSTOR-6694)

4. Known Issues

• [Core storage] The chunk service fails during a journal resize. (VSTOR-30111)

• [Core storage] Global Catalog in Acronis Cyber Backup does not reclaim the last chunks of RAID6 files. (VSTOR-34465)

• [User interface] The management node does not return a clear backup status if high availability is enabled. (VSTOR-32254)

• [User interface] The admin panel does not update the node status while the backend is busy. (VSTOR-35443)

• [User interface] Placements associated with images are displayed in the virtual machine creation wizard. (VSTOR-35900)

• [Installer] In the installation wizard, it is not possible to turn on the network time if it was turned off on the previous step. (VSTOR-30581)

5. Installing the Update

You can upgrade Virtuozzo Hybrid Infrastructure 3.5 to 4.0 in the SETTINGS > UPDATE section. 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 may be unavailable on cluster configurations without the redundancy of services or data.

IMPORTANT: During the upgrade, custom public endpoints for the OpenStack API that use domain names instead of IP addresses will be replaced with the default values. This can lead to OpenStack API unavailability if these endpoints are used to connect third-party software or to manage the infrastructure. To make the endpoint configuration persistent after the upgrade, follow the instructions in Setting a DNS name for the compute API.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-063.json.

1. Overview

This update provides bug fixes and improvements.

2. Bug Fixes

• Optimize the schedule of periodic tasks to minimize the number of false-positive “Node is offline” alerts. (VSTOR-36967)

• Under certain circumstances, load balancers may fail to create. (VSTOR-35658)

3. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-062.json.

1. Overview

This update provides a new feature as well as improvements and bug fixes.

2. New Features

• Support for Ubuntu 20.04 as a guest operating system.

3. Bug Fixes

• After failed VM evacuations, resource allocations are duplicated. (VSTOR-34750)

• An update to a new major release may fail with the error “Updates to multiple product versions are available.” (VSTOR-30767)

• Stability and performance improvements. (VSTOR-35234, VSTOR-35001, VSTOR-34970, VSTOR-34836, VSTOR-34660, VSTOR-34636, VSTOR-34463, VSTOR-34322)

4. Installing the Update

Update 5 becomes available only after Update 4 is installed (Update 4 installation is mandatory and cannot be skipped). You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-052.json.

1. Overview

This update provides a fix for the 3.0 to 3.5 upgrade procedure.

2. Bug Fixes

• Upgrade from version 3.0 to 3.5 may fail in some cases due to the absence of an internal product file. (VSTOR-34105)

3. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required.

The JSON file with the source of this advisory is available at https://docs.virtuozzo.com/vza/VZA-2020-047.json.

1. Overview

This update provides a new feature as well as bug fixes and improvements.

2. New Features

• Virtuozzo Infrastructure Platform has been renamed to Virtuozzo Hybrid Infrastructure. The change affects versions 3.5 and newer.

3. Bug Fixes

• Nodes may be shown as offline in admin panel after releasing a failed CS disk. (VSTOR-33730)

• False positive “Node is offline” alerts may appear. (VSTOR-33712)

• The update from version 3.0 to 3.5 may fail due to incorrect file permissions. (VSTOR-33672)

• With Nagios installed, the update from version 3.0 to 3.5 may fail due to a package conflict. (VSTOR-33634)

• A bond interface in the 802.3ad mode created during the installation does not start after boot. (VSTOR-31645)

• After VM migration, there can be no ARP announcement. (VSTOR-33727)

• Stability and performance improvements. (VSTOR-30676, VSTOR-33824, VSTOR-33775, VSTOR-33774, VSTOR-33756, VSTOR-33525, VSTOR-33471, VSTOR-33257, VSTOR-33236, VSTOR-33151, VSTOR-32992, VSTOR-32969, VSTOR-32968, VSTOR-32332)

4. Installing the Update

You can install the update in the SETTINGS > UPDATE section of the admin panel. A reboot is not required.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-041.json.

1. Overview

This update provides a stability fix for the metadata service.

2. Bug Fixes

• Unreadable files may be created when using erasure coding during the upgrade from version 3.0 to 3.5. (VSTOR-32856)

3. Installing the Update

The update fixes the upgrade procedure from version 3.0 to 3.5. The issue is mitigated by upgrading to this hotfix. Installing this hotfix on clusters already running version 3.5 has no effect. If your cluster is running version 3.5 and you experience this issue, please contact the technical support.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-039.json.

1. Overview

This update provides bug fixes and improvements.

2. Bug Fixes

• Assigning tier 0 to a cache disk makes no effect. The disk does not receive the “journal_tier” parameter and can be used by storage disks of other tiers. (VSTOR-33034)

• S3 cluster creation fails with a timeout, because of a wrong DNS resolution from the admin panel. (VSTOR-33032)

• An update fails when a node cannot enter the maintenance mode, because its CS has an incorrect state. (VSTOR-32910)

• A drive is shown as “Failed” after an update to version 3.5.2 in Microsoft Azure. (VSTOR-32867)

• The Kubernetes cluster cannot be deployed if its VM is attached to a network without configured nameservers. (VSTOR-32767)

• The update from version 3.0.5 to 3.5.2 fails with a one-hour timeout. (VSTOR-32451)

• Kubernetes cluster creation fails after choosing a storage policy not added to project quotas. (VSTOR-31845)

• After assigning roles to a node disk during the cluster creation and reassigning them afterwards, the node may appear as “Failed”. (VSTOR-31053)

• Stability and performance improvements. (VSTOR-32517, VSTOR-32433, VSTOR-32423, VSTOR-29406, VSTOR-32970, VSTOR-32997)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-033.json.

1. Overview

This update provides a stability fix for the metadata service.

2. Bug Fixes

• Unreadable files may be created when using erasure coding during the upgrade from version 3.0 to 3.5. (VSTOR-32856)

3. Installing the Update

The update fixes the upgrade procedure from version 3.0 to 3.5. The issue is mitigated by upgrading to this hotfix. Installing this hotfix on clusters already running version 3.5 has no effect. If your cluster is running version 3.5 and you experience this issue, please contact the technical support.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-030.json.

1. Overview

This update provides a stability fix for the metadata service.

2. Bug Fixes

• The metadata service may restart after the upgrade from version 3.0 to 3.5. (VSTOR-30452)

3. Installing the Update

The update fixes the upgrade procedure from version 3.0 to 3.5. The issue is mitigated by upgrading to this hotfix. Installing this hotfix on clusters already running version 3.5 has no effect. If your cluster is running version 3.5 and you experience this issue, please contact the technical support.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-027.json.

1. Overview

This update provides new features as well as bug fixes and improvements.

2. New Features

• AMD EPYC CPU support.

• Possibility to customize the self-service panel title.

3. Bug Fixes

• Update from version 3.5.0 to 3.5.1 may get stuck in the “Updating” status. (VSTOR-31884, VSTOR-31885)

• The root partition on Kubernetes master nodes is not resized to the specified volume size. (VSTOR-31860)

• Kubernetes cluster creation may fail with “Failed to download Kubeconfig” error. (VSTOR-31670)

• Unable to update 3.5 clusters in Microsoft Azure (also affects clusters that have little space on the boot partition). (VSTOR-31218)

• Empty graphs after update from version 3.0.5 to 3.5.1. (VSTOR-31204)

• Cannot create a management node backup if tier 0 has no assigned disks. (VSTOR-31023)

• Failed to exit the maintenance mode because the window is blocked by a spinner. (VSTOR-32297)

• Impossible to bring down a bonded interface with a VLAN assigned to it. (VSTOR-31854)

• Wrong timezone of a new Kubernetes cluster. (VSTOR-31786)

• Stability and performance improvements. (VSTOR-31032, VSTOR-31650, VSTOR-31653, VSTOR-31874, VSTOR-32036, VSTOR-32108, VSTOR-32223)

4. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-022.json.

1. Overview

This update provides an important bug fix for Backup Gateway.

2. Bug Fixes

• Backup Gateway may be unstable. (VSTOR-31604)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-018.json.

1. Overview

This update provides a new feature as well as fixes and improvements.

2. New Features

• Localized the admin and self-service panels into Chinese and Japanese.

3. Bug Fixes

• Unable to release node from cluster: ‘Unable to send message to any node in ABGW cluster’. (VSTOR-30003)

• No read/write data on dashboards if multipath is configured. (VSTOR-30135)

• Automatically restart abgw.service after the ‘Promote to primary cluster’ operation. (VSTOR-30179)

• NFS service may be in the ‘INACTIVE’ state. (VSTOR-30353)

• iSCSI LUNs can disconnect for short periods of time. (VSTOR-30459)

• Compute bridge interfaces can be missing after upgrade to version 3.5 from certain builds. (VSTOR-30535)

• yum gets unfinished transactions if docker container cannot be stopped forcibly. (VSTOR-30540)

• Backend may not connect to agent after upgrade to version 3.5 due to incorrect CN in client.crt. (VSTOR-30555)

• vstorage-nfs.service remains active and running after the node has been released from an NFS cluster. (VSTOR-30622)

• Unable to create a VM with a specified static IP on a public interface from the self-service panel. (VSTOR-31026)

• No reason for VM build failure shown if fixed IP address is already in use. (VSTOR-31088)

• Logging in to S3 console can fail with a ‘Network failure’ error when connecting via HTTP instead of HTTPS. (VSTOR-32214)

• Stability and performance improvements. (VSTOR-17040, VSTOR-27200, VSTOR-27947, VSTOR-27947, VSTOR-28109, VSTOR-28109, VSTOR-29108, VSTOR-29359, VSTOR-29392, VSTOR-29393, VSTOR-29745, VSTOR-29841, VSTOR-29888, VSTOR-29924, VSTOR-29938, VSTOR-29952, VSTOR-29973, VSTOR-29988, VSTOR-29995, VSTOR-30083, VSTOR-30104, VSTOR-30106, VSTOR-30549, VSTOR-30575, VSTOR-30599, VSTOR-30887)

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 update. Updated nodes will be rebooted automatically, one at a time. During the reboot, the storage service might be unavailable on cluster configurations without the redundancy of services or data.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-017.json.

1. Overview

This update enables upgrade to Virtuozzo Infrastructure Platform 3.5 and provides important system fixes.

2. Bug Fixes

• Several stability and performance improvements. (TTASK-31595, VSTOR-30463, VSTOR-30887)

3. Installing the Update

Update 5 will become available only after Update 4 is installed (Update 4 installation is mandatory and cannot be skipped). You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update. To get the update if you already have a previous Update 5 build installed, either wait up to a day until the next periodic check for updates or trigger the check manually with the ‘vinfra software-updates check-for-updates –wait’ command.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-015.json.

1. Overview

This update provides stability fixes for the upgrade procedure to version 3.5.

2. Bug Fixes

• ‘Service disabled’ error after updating to version 3.5 under certain circumstances if management high availability is configured. (VSTOR-30561)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-009.json.

1. Overview

This update provides stability fixes for the upgrade procedure.

2. Bug Fixes

• MDS could crash after the upgrade to version 3.5. (VSTOR-30463)

• Nodes could be marked as offline in the admin panel after a failed upgrade. (VSTOR-30541)

3. Installing the Update

You can update Virtuozzo Hybrid Infrastructure in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-008.json.

1. Overview

In this release, Virtuozzo Hybrid Infrastructure offers a wide range of new features that enhance the experience of users working with compute virtualization and software-defined networking functionalities. Additionally, the update delivers stability improvements and addresses bugs found in previous releases.

2. New Features

• Kubernetes as a service. With Kubernetes as a service, end users can easily deploy ready-to-use Kubernetes clusters with pre-integrated persistent storage and load balancing for their containerized applications in production. This feature is available in the self-service panel.

• Load balancing as a service. Load balancing as a service simplifies and automates load balancer deployment in highly available high-load cloud infrastructures. Load balancing is also enabled automatically for Kubernetes as a service. This feature is available in the self-service panel.

• VM placement rules. Placements allow administrators to group compute nodes by traits and place virtual machines on required nodes. Placements are offered as an additional service to end users in the self-service panel. There are several use cases when this feature is essential:

  • Efficient per-host licensing management (Windows Server or SQL Server licensing).

  • Placing VMs according to hardware features they require.

  • Placing tenants on dedicated nodes.

• Maintenance mode. Enables field technicians to perform maintenance operations on physical nodes while keeping workloads online. When a node enters the maintenance mode, the platform attempts to migrate running workloads to other nodes with available resources.

• Non-disruptive rolling updates. Cluster updates or upgrades that require node reboots can now be performed without workload downtime.

• Automatic storage role assignment for replacement disks. It is now possible to automatically assign the storage role to replacement disks. When an administrator replaces a storage drive, it is formatted, assigned the storage role, and added to the cluster. This feature is disabled by default.

• Other enhancements:

  • New erasure coding schemas for small clusters: 1+1 and 3+1. They offer redundancy against the failure of a single node.

  • Compute resources usage metering per project.

  • Grafana performance and statistics charts for the block storage service.

  • Signature Version 4 support by the S3 service.

  • Object locking API support by the S3 service.

  • Signed URLs support by the S3 service.

  • vinfra commands for the Backup Gateway service.

  • Support for migration from VMware with virt-v2v.

  • Backup Gateway presets for Cloudian and Wasabi.

  • User interface localized into German, Brazil Portuguese, and Spanish.

3. Bug Fixes

• [Core Storage] Storage cluster names must not exceed 50 characters. (VSTOR-17902)

• [Core Storage] Improved RAM consumption and memory management for nodes with more than 100 drives. (VSTOR-23586)

• [Block Storage] The Active/Optimized path is normally chosen by the initiator (Explicit ALUA). If the initiator cannot do so (either does not support it or times out), the path is chosen by the storage itself (Implicit ALUA). (VSTOR-25145)

• [Compute Service] No information shown in Overview while a node is being added to an existing compute cluster. (VSTOR-15978)

• [Compute Networking] It is now possible to create bond and VLAN connections on network interfaces with the “VM public” traffic type. (VSTOR-6664)

• [High Availability for the Admin Panel] In some cases, a node could be treated as offline for a while after the HA cluster had been created. (VSTOR-16823)

• [High Availability for the Admin Panel] It is impossible to add a node to the HA cluster if one of the nodes included in HA cluster is offline. (VSTOR-10950, VSTOR-16716, VSTOR-17690)

• [High Availability for the Admin Panel] Improved retention policy for admin panel backups: one per day for the last week, one per week for the last 45 days. (VSTOR-26560)

• [High Availability for the Admin Panel] Improved management node HA for a faster reaction to disasters. (VSTOR-21012)

• [High Availability for the Admin Panel] Other high availability improvements. (VSTOR-10950, VSTOR-16716, VSTOR-17690, VSTOR-18730, VSTOR-21170)

• [Monitoring and Alerting] Physical space on the storage dashboard and compute overview might differ, because the compute overview also takes into account licensed space. (VSTOR-17297)

• [Networking] Networks renamed to a predefined network name (e.g., “Private” or “Public”) cannot be renamed again. (VSTOR-20281)

• [Networking] The maximum transmission unit (MTU) value set for network bonds cannot be modified from the admin panel. (VSTOR-22388)

• [Networking] DHCP settings do not apply to virtual machine’s second interface. (VSTOR-25575)

• [Object Storage] Support multiple object deletion in the S3 service. (VSTOR-27176)

• [Updates] Monitoring of storage services may get stuck in some cases during the update. (VSTOR-26431)

• [User Interface] Used space on software RAID volumes is incorrectly reported in the admin panel. (VSTOR-23861)

• [User Interface] ED25519 SSH keys are not supported. (VSTOR-26405)

• [User Interface] Trusted S3 self-signed certificate does not work for specified domain names but only for subdomains. (VSTOR-23790)

4. Known Issues

• [Compute Service] There is no “crashed” state for virtual machines in the admin panel. Such VMs are displayed as “Paused” in CLI and as “ACTIVE” in the admin panel. (VSTOR-18054)

• [Compute Service] When two nodes are powered off at once, VMs from the second node are not evacuated. (VSTOR-21316)

• [Compute Service] [VM] Shelve: There is no message about insufficient resources when the user clicks “Unshelve”. (VSTOR-20652)

• [Core Storage] Unable to release a disk with the role “MDS+cache” even if there is another disk with the same role on the same node. You need to release and re-join the node to free the unnecessary “MDS+cache” disk. (VSTOR-11567)

• [Monitoring and Alerting] Cannot reset zoom on disk performance charts. (VSTOR-13622)

• [Object Storage] The ostor-s3-admin list-all-buckets command reports wrong bucket sizes. (VSTOR-27096)

• [User Interface] Unable to hide the progress bar window while uploading an ISO image to VM images. (VSTOR-19970)

• [User Interface] Admin panel shows wrong statistics for the logical space used by VMs. (VSTOR-19699)

• [Virtual Machine Migration] There is no ‘Cancel migration’ operation when migrating virtual machines in the user interface and ‘vinfra’ command line interface. (VSTOR-19733, VSTOR-14487)

• [Virtual Machine Migration] No error thrown on a failed attempt to migrate a VM. (VSTOR-18053)

5. Obtaining the Release

You can upgrade Virtuozzo Infrastructure Platform 3.0 to Virtuozzo Hybrid Infrastructure 3.5 in the SETTINGS > UPDATE section. 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 JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-005.json.

1. Overview

This update enables upgrade to Virtuozzo Infrastructure Platform 3.5 and provides important system fixes.

2. Bug Fixes

• Several stability and performance improvements. (VSTOR-28132, VSTOR-29361)

3. Installing the Update

Update 5 will become available only after Update 4 is installed (Update 4 installation is mandatory and cannot be skipped). You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2020-004.json.

1. Overview

This update provides bug fixes and improvements.

2. Bug Fixes

• [Update] Storage config files could be overwritten during the update. (VSTOR-26618, VSTOR-27446)

• [Storage] CS removal could get stuck in the “failed release” state. (VSTOR-26621)

• [S3] Could not delete big files on slow S3 storage. (VSTOR-26764, VSTOR-26832)

• [WebCP] Disks could temporarily get the “failed” status in the admin panel. (VSTOR-26922)

• [WebCP] Could not destroy the high availability cluster from the admin panel as a regular administrator. The default superadmin could still do it. (VSTOR-27077)

• [iSCSI] ESXi could mark iSCSI connection OFFLINE and reconnect to target infinitely. (VSTOR-27956)

• Stability and performance improvements. (VSTOR-26811, VSTOR-26998, VSTOR-27045, VSTOR-27062, VSTOR-27456, VSTOR-27507, VSTOR-27558, VSTOR-27575)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-087.json.

1. Overview

This update provides a stability fix.

2. Bug Fixes

• [ABGW] Fixes ABGW context leak. (VSTOR-27309)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-083.json.

1. Overview

This update provides upgrade procedure improvements.

2. Bug Fixes

• Upgrade procedure improvements. (VSTOR-26450, VSTOR-26658, VSTOR-27059, VSTOR-27094, VSTOR-27154)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-082.json.

1. Overview

This update provides fixes and improvements.

2. Bug Fixes

• [SNMP] snmpd.conf should not be replaced after the update. (VSTOR-25522)

• [S3] Uploading a binary file could fail in some cases. (VSTOR-25600)

• [WebCP] Added support for ED25519 SSH keys. (VSTOR-26405)

• [Compute] Image registry could be outdated on some nodes in the high availability cluster. (VSTOR-26407)

• Stability and performance improvements. (VSTOR-25008, VSTOR-25237, VSTOR-25425, VSTOR-25441, VSTOR-25795, VSTOR-26471, VSTOR-26497, VSTOR-26290, VSTOR-26535)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-075.json.

1. Overview

This update provides an improvement for the iSCSI upgrade procedure.

2. Bug Fixes

• [Upgrade] Improvement in the iSCSI upgrade procedure. (VSTOR-26254)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-072.json.

1. Overview

This update provides a new feature as well as fixes and improvements.

2. New Features

• Localized the admin and self-service panels into Spanish, Portugese and German.

3. Bug Fixes

• [Update] Decreased the free space required on the “/boot” partition from 200 MB to 150 MB. (VSTOR-26019)

• [Admin panel] Management node backup would fail if anaconda-ks.cfg was missing. (VSTOR-26041)

• Stability and performance improvements. (VSTOR-22134, VSTOR-25246, VSTOR-25553, VSTOR-25638, VSTOR-25684, VSTOR-25847, VSTOR-25885, VSTOR-26203, VSTOR-26211)

4. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-071.json.

1. Overview

This update provides fixes and improvements.

2. Bug Fixes

• [Upgrade] Improvements in iSCSI targets migration during upgrade. (VSTOR-22386, VSTOR-24775, VSTOR-25752)

• [Upgrade] Improved upgrade speed. (VSTOR-25072)

• [Upgrade] Unable to download upgrade as a user with the Administrator role (the default superadmin is not affected). (VSTOR-25784)

• [Upgrade] Added eligibility check for free space on boot and root partitions. (VSTOR-26018)

• [ABGW] ABGW could stop servicing connections even though it was running. (VSTOR-23107)

• [ABGW, Storage] Increased response timeout for MDS connections. (VSTOR-24831)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-070.json.

1. Overview

This update provides stability fixes.

2. Bug Fixes

• [ABGW] Acronis Backup Gateway could reject Acronis Backup Advanced certificates. (VSTOR-25491)

• [S3] NS services could fail to start. (VSTOR-25625)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-062.json.

1. Overview

This update provides a new feature as well as stability and usability fixes.

2. New Features

• Metering for compute resources per domain/project.

3. Bug Fixes

• Wrong details were reported for software RAID partitions. (VSTOR-23861)

• Log rotation could lead to agent restart. (VSTOR-24687)

• Network configuration was not rolled back after bond creation failure. (VSTOR-24814)

• Compute SSL certificate was not changed after enabling HA. (VSTOR-24917)

• Using snmpwalk on VSTORAGE-MIB objects could result in error “No Such Object available.” (VSTOR-25286)

• Stability and performance improvements. (VSTOR-18431, VSTOR-19269, VSTOR-20126, VSTOR-21378, VSTOR-22219, VSTOR-23219, VSTOR-23477, VSTOR-23598, VSTOR-23599, VSTOR-23614, VSTOR-23796, VSTOR-23796, VSTOR-23797, VSTOR-24258, VSTOR-24306, VSTOR-24383, VSTOR-24532, VSTOR-24548, VSTOR-24575, VSTOR-24575, VSTOR-24598, VSTOR-24682, VSTOR-24713, VSTOR-24741, VSTOR-24745, VSTOR-24781, VSTOR-24783, VSTOR-24814, VSTOR-24831, VSTOR-24861, VSTOR-24873, VSTOR-24889, VSTOR-24904, VSTOR-24909, VSTOR-24911, VSTOR-24943, VSTOR-24973, VSTOR-25010, VSTOR-25075, VSTOR-25197, VSTOR-25239, VSTOR-25267, VSTOR-25267)

4. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is required to complete the update if your cluster is running iSCSI services. Updated nodes need to be rebooted manually, one at a time. During the reboot, the storage service might be unavailable on cluster configurations without the redundancy of services or data.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-061.json.

1. Overview

This update introduces a stability fix.

2. Bug Fixes

• UI could remain locked if an update from previous versions of Virtuozzo Infrastructure Platform 2.5 failed. (VSTOR-24786)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-056.json.

1. Overview

In this release, Virtuozzo Infrastructure Platform offers a wide range of new features that enhance the experience of users working with compute virtualization and software-defined networking functionalities. Additionally, the update delivers stability improvements and addresses bugs found in previous releases.

2. New Features

• [Compute Virtualization] Self-service panel. A separate, completely customizable interface allows end customers to manage their own compute resources.

• [Compute Virtualization] Tenant management. Service providers can now manage the projects and resource quotas of their end customers in the admin panel. Quotas for the following resources are supported: vCPUs, RAM, storage for volumes and snapshots (per storage policy), floating IP addresses.

• [Compute Virtualization] Application-consistent snapshots. Ability to create snapshots of virtual machine volumes compatible with Linux and Windows deployments.

• [Compute Virtualization] Virtual routers. Service providers can now configure flexible virtual networking environments. Includes support for virtual routers, Source Network Address Translation (SNAT) and static routing.

• [Compute Virtualization] Floating IP addresses. Self-service panel users can now expose their virtual machines on public networks.

• [Compute Virtualization] SSH keys. Self-service panel users can now enable secure access to their virtual machines.

• [Compute Virtualization] High availability for virtual machines. Automatic workload restoration in case of node failure.

• [Compute Virtualization] Initial customization of virtual machines. Initial guest OS customization with cloud-init scripts is now available when creating virtual machines.

• [Compute Virtualization] More guest operating systems. Added support for Microsoft Windows Server 2019 and Red Hat Enterprise Linux 8.

• [Compute Virtualization] Advanced memory management. Improved performance thanks to dynamic balancing of virtual machines between NUMA nodes on the host.

• [Compute Virtualization] Virtual machine shelving. End customers using the self-service panel can release vCPU/RAM resources in their projects. Virtuozzo partners can free up reserved vCPUs/RAM on their hosts.

• [Storage] Persistent reservations for iSCSI. Full functionality is enabled for Microsoft Hyper-V, VMware ESXi and Linux initiators.

• [Installer] Improved installer. The installation program has been overhauled for a better user experience.

• [UI and UX] Improved navigation for the compute service and settings.

• Other enhancements. Better overall stability and performance.

3. Bug Fixes

• In some cases, the DHCP address is not obtained by a virtual machine from a network that is not assigned to the adapter. (VSTOR-16839)

• “Network has undefined speed” alert is displayed for network interfaces with unplugged links. (VSTOR-17286)

• Need to manually clean browser cache and cookies after destroying the compute cluster. Otherwise the newly created compute cluster will have empty compute dashboard. (VSTOR-17752)

• User cannot release the master management node from the high availability configuration. (VSTOR-17852, VSTOR-18259)

• Unable to release a node from the compute cluster if it is included in the management node high availability configuration. Release the node from the management node high availability cluster first before releasing it from the compute cluster. (VSTOR-18299)

• Resetting network services might result in node reboot. (VSTOR-19962)

• Chunk service (CS) journals are not resized to fit caching SSD drive size and might be implicitly placed on the same disk with the CS itself. (VSTOR-20209)

• Caching the value of free space on the management node might lead to unsuccessful software update. (VSTOR-20279)

• Self-signed certificates for S3 are not valid for Google Chrome. (VSTOR-21670)

• After node reboot, the state of the target portal groups may be lost, preventing access to some of the LUNs. (VSTOR-22386)

• Network names shorter than three characters are not valid. (VSTOR-22389)

• Sometimes valid target names are not usable when creating iSCSI targets. (VSTOR-22407)

• Errors in chunk services alert collector might result in loss of results on subsequent alert collectors. (VSTOR-22891)

• iSCSI target daemon does not provide Prometheus support. (VSTOR-23545)

• Redis lock might not be deleted automatically, leading to inability to login to the backend. (VSTOR-24064)

4. Known Issues

• 25 Gbit network cards are shown as 10 Gbit ones in the admin panel. (VSTOR-9422)

• It is impossible to add a node to the HA cluster if one of the nodes included in HA cluster is offline. (VSTOR-10950, VSTOR-16716, VSTOR-17690)

• It is not possible to release a disk with the role “MDS+cache” on a node even if there is another disk with the “MDS+cache” role on the same node. You need to release and re-join the node to free the unnecessary “MDS+cache” disk. (VSTOR-11567)

• It is not possible to cancel virtual machine migration. (VSTOR-12379)

• In some cases, node failure may cause I/O to hang or cluster performance to degrade on iWARP cards. (VSTOR-12872)

• Cannot reset zoom on disk performance graphs. (VSTOR-13622)

• Need to manually refresh page after admin panel HA creation. (VSTOR-14800)

• Need to manually refresh page after flavor creation to update list of flavors on Compute > Flavors. (VSTOR-15252)

• No information shown in Overview while a node is being added to an existing compute cluster. (VSTOR-15978)

• In some cases, a node could be treated as “offline” for a while after creating the HA cluster. (VSTOR-16823)

• Physical space on the storage dashboard and compute overview might differ, because the compute overview also takes into account licensed space. (VSTOR-17297)

• Storage clusters with names over 50 characters are not created correctly and fail. Storage cluster names must not exceed 50 characters. (VSTOR-17902)

• The admin panel allows migrating a virtual machine with a public NIC to a node that is not connected to the underlying public network. (VSTOR-17921)

• No error thrown on attempt to migrate a virtual machine to a node with insufficient RAM or a different CPU compared to the source node. The virtual machine shuts down and then starts again on the same node. (VSTOR-18053)

• There is no “crashed” state for virtual machines in the admin panel. Such VMs are displayed as “Paused” in CLI and as “ACTIVE” in the admin panel. (VSTOR-18054)

• No error message thrown when creating NFS cluster on a node without the “NFS” traffic type. (VSTOR-18068)

• Unable to change Compute Private/Compute API roles from a private to public network after deploying the compute cluster. (VSTOR-18491)

• If only one network, “Private”, is used in a cluster, need to uncheck “Admin panel” from the “Public” network before creating management panel HA. (VSTOR-18730, VSTOR-21170)

• Admin panel shows wrong statistics for the logical space used by VMs. (VSTOR-19699)

• It is not possible to hide the progress bar window while uploading an ISO image to the VM images. (VSTOR-19970)

• The maximum transmission unit (MTU) value set for network bonds cannot be modified from the admin panel. (VSTOR-22388)

• Used space on software RAIDs is incorrectly reported in the admin panel. (VSTOR-23861)

• Attempting to download selected files from the S3 bucket opens them in new browser tabs instead. Affects files of certain types, including PDF, JPG and PNG. (VSTOR-24244)

5. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is required to complete the update. Updated nodes will be rebooted automatically, one at a time. During the reboot, the storage service might be unavailable on cluster configurations without the redundancy of services or data.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-055.json.

1. Overview

This update enables upgrade to the new major version 3.0 and provides important system fixes.

2. Bug Fixes

• Journald could get stuck, waiting endlessly for “–verify” to complete and stalling services in an unresponsive state. (VSTOR-23308)

• Under certain circumstances, update from the admin panel could fail if systemd was being updated. (VSTOR-23898)

• Increase heartbeat expiration grace period to 10 seconds for shaman. (VSTOR-24144)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is not required to obtain this update.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-054.json.

1. Overview

This update mitigates the Microarchitectural Store Buffer Data (MDS) vulnerability and provides a performance bug fix.

2. Security Fixes

• [Important] The Microarchitectural Store Buffer Data (MDS) is a series of hardware vulnerabilities which allow speculative execution attacks on Intel processors. A malicious application or guest virtual machine can use this flaw to gain access to data stored in internal CPU buffers, bypassing security restrictions. For more details, visit the Virtuozzo Blog. (VSTOR-23200)

3. Bug Fixes

• Performance improvement comparing to previous updates. (VSTOR-22963)

4. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is required to complete the update. Updated nodes will be rebooted automatically, one at a time. During the reboot, the storage service might be unavailable on cluster configurations without the redundancy of services or data.

5. References

• https://access.redhat.com/security/vulnerabilities/mds

• https://www.virtuozzo.com/blog-review/details/blog/view/virtuozzo-guidance-on-the-microarchitectural-store-buffer-data-mds-vulnerability.html

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-041.json.

1. Overview

This update provides stability and usability fixes.

2. Bug Fixes

• Command-line tools improvements. (VSTOR-9712, VSTOR-21601)

• Fixed possible crash of vstorage-target-monitor on shutdown. (VSTOR-21059)

• Automatic replication could stall in case some replicas were dirty while others were offline. (VSTOR-21075)

• Fixed recovery of SSL connections after network errors. (VSTOR-21899)

• Fixed a memory leak in MDS. (VSTOR-22074)

• Fixed possible incorrect behaviour during failover. (VSTOR-22635)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot may or may not be required, depending on your product version and build:

• No reboot is required to update from Update 5 (build 1639).

• A manual reboot is required to update from Update 3 or 4 (builds 1601-1617).

• Automatic reboot will be performed on each node in succession to update from older versions (build 1600 and earlier).

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-034.json.

1. Overview

This update provides a new feature as well as stability and usability fixes.

2. New Features

• S3: Added support for GET Bucket V2 API.

3. Bug Fixes

• The same data path ID was assigned to VLAN interfaces in OVS bridges. (VSTOR-20558)

• Unable to update storage license. (VSTOR-20913)

• Under certain circumstances, accounting of S3 space usage was incorrect. (VSTOR-21089)

• Improved performance of requests to obtain information about CSes. (VSTOR-21354)

• High availability logs could occupy a lot of space. (VSTOR-21462)

• The xcopy operation did not work correctly when moving VMs between different datastore tiers placed on the same iSCSI target. (VSTOR-21518)

• Some graphs could be empty or not shown in the monitoring dashboard after a node crash. (VSTOR-21603)

• The automatic reporting tool could leave reports in ‘/var/tmp/report.tar.gz’. (VSTOR-21624)

• Custom firewall rules could disappear after a restart of the iptables service. (VSTOR-21674)

• Stability and performance improvements. (VSTOR-5197, VSTOR-18477, VSTOR-18658, VSTOR-20087, VSTOR-20304, VSTOR-20333, VSTOR-20757, VSTOR-21023, VSTOR-21089, VSTOR-21155, VSTOR-21199, VSTOR-21418, VSTOR-21493, VSTOR-21718, VSTOR-21730, VSTOR-21783, VSTOR-21812, VSTOR-21835, VSTOR-21844)

4. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is required to complete the update if your cluster is running iSCSI services. Updated nodes need to be rebooted manually, one at a time. During the reboot, the storage service might be unavailable on cluster configurations without the redundancy of services or data.

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-025.json.

1. Overview

This update provides stability and usability fixes.

2. Bug Fixes

• Blink button in the admin panel was not working in some cases. (VSTOR-14144, VSTOR-20526)

• Unable to create network bonds. (VSTOR-20197)

• Disk replacement occasionally does not allow to assign disk and fails with ‘service_params’. (VSTOR-20232)

• Bringing up network interfaces from the admin panel may result in an error. (VSTOR-20239)

• Other stability and performance improvements. (VSTOR-19284, VSTOR-19410, VSTOR-20370)

3. Installing the Update

Install the update by running ‘yum update’.

The JSON file is available at https://docs.virtuozzo.com/vza/VZA-2019-022.json.

1. Overview

This update provides stability and usability fixes.

2. Bug Fixes

• With erasure coding, write operations are blocked after two or more nodes fail, even if the cluster has enough disks available. (VSTOR-19098)

• Unable to list buckets via CLI after bucket removal via API. (VSTOR-19326)

• vstorage-mount may occasionally hang with the message “task fuse-evloop:2710 blocked”. (VSTOR-19620)

• vstorage-target-monitor may occasionally fail with the error message “concurrent map writes”. (VSTOR-20626)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is required to complete the update. Updated nodes will be rebooted automatically, one at a time. During the reboot, the storage service might be unavailable on cluster configurations without the redundancy of services or data.

The JSON file is available at https://docs.virtuozzo.com/vza/VZA-2019-020.json.

1. Overview

This update provides a stability and usability fix.

2. Bug Fixes

• Some storage cluster archives may become unavailable after upgrade to version 2.5. (VSTOR-20151)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is required to complete the update. Updated nodes will be rebooted automatically, one at a time. During the reboot, the storage service might be unavailable on cluster configurations without the redundancy of services or data.

The JSON file is available at https://docs.virtuozzo.com/vza/VZA-2019-019.json.

1. Overview

This update provides stability and usability fixes.

2. Bug Fixes

• Improved automatic firewall rules configuration. (VSTOR-19695, VSTOR-19857)

3. Installing the Update

You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is required to complete the update. Updated nodes will be rebooted automatically, one at a time. During the reboot, the storage service might be unavailable on cluster configurations without the redundancy of services or data.

The JSON file is available at https://docs.virtuozzo.com/vza/VZA-2019-018.json.

1. Overview

This product is formerly known as Virtuozzo Storage. With this release, Virtuozzo Infrastructure Platform offers a wide range of new features for compute virtualization and software-defined networking, as well as enhancements and stability improvements. It also addresses issues found in the previous releases.

2. New Features

• Compute virtualization. Run virtual machines on Virtuozzo Infrastructure Platform nodes in the hyper-converged mode (storage and compute on same node) or the traditional way (storage and compute on separate nodes). Virtual machine management: run, resize, migrate, and open console to virtual machines. Private software-defined networking for virtual machines (VXLAN). Storage policies for virtual machines. Easy-to-use data redundancy options for virtual machine volumes. Easy to configure high availability for compute service and virtual machines. Supported guest operation systems: CentOS 6, CentOS 7, RHEL 6, RHEL 7, Debian 9, Ubuntu 16.04, Ubuntu 18.04, Windows 7, Windows 8.1, Windows 10, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019. Full Windows guest support with automatic installation of paravirtualization drivers (virtio) during installation from ISO.

• iSCSI targets get better performance and high availability via multi-path. The new iSCSI target subsystem and high availability engine reduce downtime by 2-4 times during node failures, making them barely noticeable for end-user applications. The subsystem uses Asymmetric Logical Unit Access (ALUA) in the Active-Passive mode.

• Fibre Channel support. Export block storage over Fibre Channel. Check Installation guide for the list of supported cards.

• RoCE and Infiniband RDMA support. Up to 25% better I/O latency and lower CPU utilization on InfiniBand, RoCE (RDMA over Converged Ethernet) and iWARP (Internet Wide-area RDMA Protocol).

• New comprehensive monitoring: Built-in monitoring with pre-configured Prometheus and Grafana. Grafana dashboards for nodes, disks, network, latency, performance, storage services. New charts with tooltips in the admin panel, including I/O latency charts, new physical and logical space charts. Zoomable charts on dashboards: from 30 minutes to 1 week. Virtual machines performance monitoring: CPU, RAM, disks and networking.

• Performance improvements for all-flash configurations. Get more IOPS with multi-threaded I/O on all-flash clusters. New fast-path approach in the core of Virtuozzo Infrastructure Platform reduces latency and implements fast multi-threaded I/O handling in Linux kernel.

• New comprehensive command-line tool. Support for more operations. Unified output for all commands: as a text table, in JSON, and in XML.

• Built-in ReadyKernel eliminates system update downtime. Based on the kpatch technology, ReadyKernel is live patching of a running Linux kernel to apply kernel hotfixes and CVEs in seconds.

• New infrastructure networking. Simplifies cluster-wide traffic and firewall configuration. Traffic types are easily assigned to cluster networks on a single screen which minimizes chances of misconfiguration. Also, new traffic types for Compute service and SNMP are added.

• UI and UX improvements: New navigation menu. New controls and fresh UI. Ability to send problem reports. Improved admin panel performance when listing resources of nodes with more than 250 local disks and 100 network interfaces.

• Single repository for all components. Easy and integrated cluster updates from the unified RPM repository.

• Other enhancements: New high availability engine significantly improves cluster reaction time to node failure for all services. New internal cluster DNS service that improves cluster services discovery. Better overall stability and performance.

3. Bug Fixes

• Improved S3 cluster creation. Automatic high availability management for object storage configuration service. (VSTOR-2948, VSTOR-8883)

• Persistent iSCSI Portal is used during configuration. (VSTOR-18256)

4. Known Issues

• High availability for iSCSI/FC does not work for iSCSI initiator in Windows 7, Windows 10 due to the lack of Active-Active mode and persistent reservations. (VSTOR-5621, VSTOR-18121)

• It is impossible to add a node to the management node high availability cluster if one of the nodes included in the management node high availability configuration is offline. The user needs to remove all nodes from the management node high availability cluster and recreate it from scratch. (VSTOR-10950, VSTOR-16716, VSTOR-17690)

• It is not possible to release the “MDS + cache” disk role without releasing all the corresponding disks to the cache or whole node release. (VSTOR-11567)

• It is not possible to cancel an ongoing migration. (VSTOR-12379)

• SPLA license may stop working with an error “bad request”, if the local time is set to a past value. (VSTOR-12495)

• In some cases, I/O may hang or cluster performance may degrade on iWARP cards in case of a node failure. (VSTOR-12872)

• The chart zoom on disk performance graphs on node screen can’t be reset to the initial state. (VSTOR-13622)

• S.M.A.R.T. alerts for system disks are not shown in the panel. (VSTOR-13811)

• Need to manually refresh admin panel web page after creating the management node high availability configuration. (VSTOR-14800)

• Need to manually refresh browser page after flavor creation. (VSTOR-15252)

• Compute overview may not work during adding/releasing nodes in the compute cluster. (VSTOR-15978)

• No “System + Metadata” disk role in the advanced mode during storage cluster creation or joining nodes to a storage cluster. (VSTOR-16523)

• It is not possible to scale down virtual machine RAM, if the compute cluster has no free memory. (VSTOR-16644)

• In some cases, a node could be treated as “offline” for a while after creating the management node high availability configuration. (VSTOR-16823)

• The DHCP address might not be obtained by a virtual machine from a network that not assigned to the adapter. (VSTOR-16839)

• “Network has undefined speed” alert is displayed for network interface with unplugged link. (VSTOR-17286)

• The storage dashboard and the compute overview may report different physical space values, because the compute overview also takes into account licensed space. (VSTOR-17297)

• Need to manually clean browser cache and cookies after destroying the compute cluster. Otherwise the newly created compute cluster will have empty compute dashboard. (VSTOR-17752)

• User cannot release the master management node from the management node high availability configuration. (VSTOR-17852, VSTOR-18259)

• Storage cluster name must be shorter than 50 characters. (VSTOR-17902)

• The admin panel does not prevent migration of a virtual machine with a public NIC to a node that is not connected to an underlying public network. (VSTOR-17921)

• It is not possible to use VLANs in virtual machines in the ‘private’ backnet. (VSTOR-17943)

• No error on attempt to migrate a virtual machine to a node with no free RAM. (VSTOR-18053)

• There is no “crashed” state for virtual machines. Such virtual machines are displayed as “ACTIVE” even though they are not operational anymore. (VSTOR-18054)

• Virtual Machine live migration to a node with a different CPU may fail without an error message. (VSTOR-18061)

• No error message when creating NFS cluster on a node without the ‘NFS’ traffic type. (VSTOR-18068)

• Installation from ISO is possible only with a US keyboard. This may result in issues with installations via IPMI with non-US locales. (VSTOR-18277)

• Unable to release a node from the compute cluster if it’s included in the management node high availability configuration. Release the node from the management node high availability first before releasing it from the compute cluster. (VSTOR-18299)

• User is unable to reassign the “Compute private” and “Compute API” traffic types to other networks after the compute cluster has been deployed. (VSTOR-18491)

• If only one, “Private”, network is used in a cluster, the user must unassign the “Admin panel” traffic type from the “Public” network before Management node high availability creation on top of only one (“Private”) network. (VSTOR-18730)

• In some cases it is needed to add “vstoradmin” user to “vstorage-user” group manually (“usermod -a -G vstorage-users vstoradmin; systemctl restart vstorage-ui-backend”) after adding new node to Management node high availability. (VSTOR-19274)

The JSON file is available at https://docs.virtuozzo.com/vza/VZA-2019-017.json.

1. Overview

The cumulative Virtuozzo ReadyKernel patch was updated with security and stability fixes. The patch applies to the Virtuozzo Infrastructure Platform kernel 3.10.0-862.20.2.vz7.73.24 (2.5).

2. Security Fixes

• [Moderate] A flaw was found in the implementation of ebtables in the Linux kernel. A local attacker in a container could exploit it to consume large amounts of memory, eventually causing denial of service on the host. (PSBM-90803)

3. Bug Fixes

• Kernel crash (access out of bounds) in SyS_mincore(). (PSBM-90329)

4. Installing the Update

Download, install, and immediately apply the patch to the current kernel by running ‘readykernel update’.

5. References

• https://readykernel.com/patch/Virtuozzo-7/readykernel-patch-73.24-70.0-1.vl7/

The JSON file with the list of new and updated packages is available at https://docs.virtuozzo.com/vza/VZA-2019-002.json.