Virtuozzo Hybrid Infrastructure 5.4 (5.4.0-133)¶
Issue date: 2023-02-14
Applies to: Virtuozzo Hybrid Infrastructure 5.4
Virtuozzo Advisory ID: VZA-2023-002
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)