Product release: Virtuozzo Hybrid Infrastructure 3.5 Update 1 (3.5.1-43)

Issue date: 2020-02-28

Applies to: Virtuozzo Hybrid Infrastructure 3.5

Virtuozzo Advisory ID: VZA-2020-017

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