Virtuozzo Hybrid Infrastructure 5.2 (5.2.0-135)¶
Issue date: 2022-08-15
Applies to: Virtuozzo Hybrid Infrastructure 5.2
Virtuozzo Advisory ID: VZA-2022-024
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)