## Virtuozzo Infrastructure 7.4 (7.4.0-97) ### Overview This update provides stability fixes. ### Fixed issues - [VSTOR-57933] The default gateway over a VLAN could be lost when a bond interface was brought up. - [VSTOR-99864] Restarting the management panel could leave background tasks stuck because their locks were cleared while the task executor kept running. - [VSTOR-102226] Listing network interfaces could take more than 10 seconds on nodes with many VLANs, slowing network pages and tasks in the admin panel. - [VSTOR-103803] Live migration could time out for a VM with a backup NBD backing chain. - [VSTOR-106312] Neutron port checking could consume all CPU resources on a node in clusters with thousands of ports, stalling the OVS agent and forcing a full resynchronization. - [VSTOR-109145, VSTOR-139340] Stability fixes for the object storage service. - [VSTOR-126027] An OVS bridge brought down and back up from the admin panel could remain down, leaving the physical interface detached. - [VSTOR-129100, VSTOR-142136] Stability fixes for the file storage metadata service. - [VSTOR-134183, VSTOR-143632] Rolling compute updates could skip management-only nodes, leaving them on previous container images and the message broker cluster in a mixed-version state. - [VSTOR-134282] Management HA virtual IPs could not be configured when a network had multiple interfaces on a node. - [VSTOR-135180, VSTOR-136328] Unicast traffic on VLAN and flat networks could be flooded to unrelated VMs on the same network. - [VSTOR-135296, VSTOR-144832] The S3 gateway could leak memory when checking multipart uploads. - [VSTOR-135626, VSTOR-143108] Unmounting the storage could hang when a storage node became unreachable, leaving dependent services such as libvirtd stuck. - [VSTOR-135713] A stability fix for the storage command-line tools. - [VSTOR-135862] A VM could hang during shutdown while closing its network backend. - [VSTOR-135949, VSTOR-137444, VSTOR-145141] Kubernetes cluster configuration requests could fail with a gateway timeout during an update. - [VSTOR-136567] The NFS service could abort when two client mounts created a file with the same name at the same time. - [VSTOR-137322] Cluster usage reports could omit CPU cores from storage-only nodes, resulting in incomplete pay-as-you-go usage reporting. - [VSTOR-137383] An HA-protected VM could remain down after evacuation was interrupted during rebuild, while being reported as active with no running domain. - [VSTOR-137637] A recoverable metadata error during background housekeeping could abort all S3 gateways in the cluster, causing a cluster-wide S3 outage. - [VSTOR-138621] Creating a load balancer with a TERMINATED_HTTPS listener could fail during a partial cluster update because the certificate container was rejected. - [VSTOR-139716, VSTOR-144850] Listing compute volumes could fail with an internal error when the service project name was not unique across domains. - [VSTOR-140456] The monitoring auto-updater could overwrite the product version in /etc/hci-release with a newer build than the cluster was actually running. - [VSTOR-141192] The update eligibility check did not flag nodes with an NVIDIA driver older than 595.58.03, the minimum version supported by version 8.0. - [VSTOR-141311] The installer could create an undersized swap partition on nodes with very large amounts of RAM. - [VSTOR-141465] A stability fix for the backup gateway key-value store. - [VSTOR-141615] A kernel stability fix for the storage client after a connection abort. - [VSTOR-141623, VSTOR-142631, VSTOR-143844] After an account was migrated, a gateway node with a warm proxy map and redirection enabled could crash or deny access to the account. - [VSTOR-141752] The product version reported to guests could remain at the previous version after an update until the compute service was restarted. - [VSTOR-142022] Volume image metadata could be missing from backup and volume export snapshots, causing volumes restored to a new VM to lose properties of the original volume. - [VSTOR-142182, VSTOR-142185, VSTOR-142187] Problem reports could be missing cluster-wide data if collection exceeded its time limit or failed on an individual item. - [VSTOR-142183, VSTOR-143671, VSTOR-143771] Problem report archives and JSON files could be read before they were completely written, resulting in truncated files. - [VSTOR-142184] Collected node data could be deleted before being packed into a problem report because the stale-file threshold matched the collection cycle. - [VSTOR-142238] The NVIDIA driver version was shown with a trailing space in the admin panel. - [VSTOR-142291] The backup gateway could miss updates to account information files when detecting changes by modification time. - [VSTOR-142363] A stale storage mount point directory could remain on a node after a software update. - [VSTOR-142375] The backup gateway could not unmount its NFS storage while the storage mount point was being switched. - [VSTOR-142663] A VM with a finalized volume could fail to start after unshelving or evacuation because a stale NBD backing store was written back to its configuration. - [VSTOR-143208] The management API could remain unavailable for several minutes longer than expected while a node rebooted during an update because the database connection pooler did not stop promptly. - [VSTOR-143382] Putting a node into maintenance could fail with an insufficient resources error even if its VMs had already been migrated to other nodes. - [VSTOR-143462] A numeric disk serial number could be replaced with an invalid value in a cluster report, making the report invalid JSON. - [VSTOR-143531] UEFI Windows guests using Microsoft 2023 Secure Boot certificates could fail to boot after migration because the certificates were missing from the firmware variable templates. - [VSTOR-143534] The Windows guest tools VirtIO storage driver could complete an incorrect request under heavy I/O, causing guest crashes and data corruption. - [VSTOR-143590] Backup progress notifications could exceed the message size limit and fail to publish for backups with many chunks. - [VSTOR-143592] Guest I/O could fail after live migration of a VM with an online-resized volume, causing the guest file system to become read-only. - [VSTOR-143595] Creating a storage cluster could take several minutes longer than necessary because an internal task continued waiting for a lock that had already been released. - [VSTOR-143694] The node agent could fail to register after installation. - [VSTOR-143906] The default replication priority boost could overload the network on clusters with fast NVMe drives. - [VSTOR-144012] Proxying between nodes could stop working after the proxy certificate was rotated and remain unavailable until the service was restarted. - [VSTOR-144178, VSTOR-144183] Added a command-line tool for importing an existing StoreOnce datastore into the backup gateway. - [VSTOR-144828] An S3 upload lock that could not be retired could cause the gateway to consume all CPU and eventually run out of memory. - [VSTOR-144831] The S3 gateway upload-lock sweep period could not be configured independently because it used the complete-request sweep setting. - [VSTOR-145189] A stability fix for the storage client mount. - [VSTOR-145327] A false-positive port check warning could appear after the Neutron OVS agent was updated. - [VSTOR-145461] The VM console in the admin panel could show an error after its connection was closed. - [VSTOR-145462] The login and account recovery pages in the admin panel could fail to preload their stylesheets. - [VSTOR-146060] A software update could unnecessarily stop VMs with a virtual TPM because their TPM process was incorrectly treated as outdated. - [VSTOR-146684] The update eligibility check could fail after the monitoring auto-updater installed a telemetry collector newer than the management backend. ------------------------------------------------------ ## Virtuozzo Infrastructure 7.4 (7.4.0-80) ### Overview This update provides stability and security fixes. ### Fixed issues - [VSTOR-140619] A security fix for CVE-2026-64531. - [VSTOR-140678] A security fix for CVE-2026-64561. - [VSTOR-87519] Storage version bumping could remain disabled until the end of a cluster update, delaying operations such as an SPLA license upgrade. - [VSTOR-125431] The compute service container could remain stopped on a node after a failed cluster update. - [VSTOR-126182] Maintenance could be stopped while a cluster update was running, allowing nodes to be rebooted unexpectedly. - [VSTOR-128648] The admin panel could fail to load with HTTP 500 on secondary high availability nodes after an update. - [VSTOR-131556] A node already in maintenance before a cluster update could have its compute service re-enabled after the update, allowing VMs to migrate to it. - [VSTOR-140023] Deleting an S3 bucket with a very large number of objects could be extremely slow; a delete-by-prefix operation is now available. - [VSTOR-140223] NFSv4 directory metadata operations could intermittently return a remote I/O error immediately after directory creation, disrupting Kubernetes workloads on NFS shares. - [VSTOR-140228] Workload reports now include the product name and version of applications discovered on Windows VMs. - [VSTOR-140445] The backup storage could repeatedly replay the same journal without advancing, stalling backup traffic. - [VSTOR-140477] Workload reports could retain data from the previous host after a VM was live migrated. - [VSTOR-140904] An empty conflict list could be shown in the UI when the update path included a version that could not be skipped. - [VSTOR-140988] Supported Kubernetes version limits were not defined for versions 7.3 and later, preventing update eligibility from being validated. - [VSTOR-141189] The message for a mandatory upgrade step did not specify which version to upgrade to first. ------------------------------------------------------ ## Virtuozzo Infrastructure 7.4 (7.4.0-75) ### Overview This update provides stability and security fixes. ### Fixed issues - [VSTOR-137729] A security fix for CVE-2026-43499. - [VSTOR-137957] Security fixes for CVE-2026-46242 and CVE-2026-43074. - [VSTOR-102068, VSTOR-102069, VSTOR-138302] Creating a VM in a server group could fail with "No valid host found" because a previously canceled or failed VM remained in the server group. - [VSTOR-120923] VPN could stop working when the StrongSwan process hung. - [VSTOR-127496] Cluster software updates could fail during the QEMU update step for a running virtual machine. - [VSTOR-132089] VM migration could allow selecting an unintended target project. - [VSTOR-135758, VSTOR-137845] A cluster update could fail when the required Leapp packages were missing after earlier upgrades or on non-management nodes. - [VSTOR-136316] Nodes in maintenance could be force-rebooted during an update when high availability resumed incorrectly. - [VSTOR-137061] Kubernetes CoreDNS could fail to watch EndpointSlices and log permission errors. - [VSTOR-137553] A load balancer pool member could be created with the VM's first IP instead of the secondary IP selected in the UI. - [VSTOR-137564, VSTOR-137769, VSTOR-138203, VSTOR-139197, VSTOR-139419, VSTOR-139498] Cluster reports could fail or be incomplete, including when traffic encryption was enabled. - [VSTOR-137775] Kubernetes API server certificates could be rejected by clients that enforce strict X.509 validation. - [VSTOR-137991] Backup gateway multi-source pull migration could leave some files empty. - [VSTOR-138440] Kubernetes cluster autoscaling could fail to scale up worker nodes. - [VSTOR-138466] Migration from VMware vCenter could fail when validating a source instance. - [VSTOR-138572] S3 requests could overload a single namespace service with repeated limit lookups. - [VSTOR-138675] Deleting a large S3 bucket could overload the namespace service, causing it to terminate. ------------------------------------------------------ ## Virtuozzo Infrastructure 7.4 ### Overview This release updates managed Kubernetes to version 1.35.3 and Fedora CoreOS to version 43, introduces API credentials for external automation workflows, and provides the updater patches and tooling required to upgrade the product to version 8.0. It also includes object storage performance improvements, virtual router reliability enhancements, and migration service improvements. ### What's new #### Compute service - Kubernetes updated to version 1.35.3. The Fedora CoreOS image used for managed Kubernetes clusters has also been updated to version 43.20260413. This returns managed Kubernetes to a version that is actively supported by the upstream project. #### Security - Users can now create API credentials (commonly known as API tokens) for external automation tools such as Terraform, Ansible, and CI/CD pipelines. API credentials are available to every user and can be managed in both the admin and self-service panels. #### Updates - Upgrade path to version 8.0. This release includes the updater patches and configuration updates required to perform an in-place upgrade to version 8.0. Hardware support policy has been clarified in relation to the RHEL 10 upstream rebase in version 8.0. A hardware compatibility checker tool is now available on GitHub to verify that your cluster hardware is supported before initiating the upgrade. ### Improvements - Improved propagation of virtual router and floating IP configuration changes. Virtual router state is now restored more reliably after a cluster outage. - Optimized performance when adding VMware sources containing hundreds of VMs and improved VM listing efficiency. Added support for migrating VMs located within VMware folders and nested subfolders. - Certain alerts now take node maintenance mode into account and will not trigger unnecessarily. ### Fixed issues - [VSTOR-109558] The admin panel could not update nodes added at an older patch level after the cluster was upgraded. - [VSTOR-120570] The storage agent could hang when accessing failed multipath devices, making nodes unmanageable. - [VSTOR-128013] Neutron L3 agent router processing could take too long in environments with many routers, causing routing outages. - [VSTOR-128885] HA destruction could be allowed on mixed-version clusters, leaving compute services in an inconsistent state. - [VSTOR-129518] The admin panel could remain slow or unresponsive when the backend was overloaded without restarting automatically. - [VSTOR-130654] Cluster update could fail while moving VMs to the storage mount point if a volume backup was still running for a VM disk. - [VSTOR-131130] Prometheus could run on all nodes after an update instead of only on management HA nodes. - [VSTOR-131185] A stability fix for the Intel ice network driver. - [VSTOR-131859] Self-service UI operations could hang when telemetry endpoints were unreachable. - [VSTOR-132221] Volume attachment updates could fail after a backup job failed on a removed compute node. - [VSTOR-133743] Public network ports could be blocked by loop protection during node reboot. - [VSTOR-134252] Revert to snapshot could be unavailable in the self-service panel for volumes on external storage. - [VSTOR-134259] Load balancer metrics collection could become extremely slow due to database bloat. - [VSTOR-134410] VM migration requests could return HTTP 500 when a migration was already in progress. - [VSTOR-134774] Validating a migration source cloud could time out when credential storage was accessed through an external address that was not available on the cluster network. - [VSTOR-134950] Security fixes for CVE-2026-35385, CVE-2026-35386, CVE-2026-35387, CVE-2026-35388, and CVE-2026-35414 in Kubernetes cluster VM templates. - [VSTOR-135357] Floating IP connectivity could stop working, making VMs and load balancers unreachable from outside the cluster. - [VSTOR-136219] Logging in through an identity provider (IdP) to another domain could display the wrong domain while keeping the previous session. - [VSTOR-137528] A security fix for CVE-2026-53359.