Virtuozzo Hybrid Infrastructure 6.3 Update 1.2 (6.3.1-121)

Issue date: 2025-04-28

Applies to: Virtuozzo Hybrid Infrastructure 6.3

Virtuozzo Advisory ID: VZA-2025-007

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.