Lucene search

K
virtuozzoVirtuozzoVZA-2024-013
HistoryMar 28, 2024 - 12:00 a.m.

Virtuozzo Hybrid Infrastructure 6.1 (6.1.0-238)

2024-03-2800:00:00
docs.virtuozzo.com
5
virtuozzo hybrid infrastructure
backup and restore
security improvements
stability
vulnerability fixes
compute services
object storage
iscsi volumes
ipsec rules
snapshot issues
email notification
load balancer
nfs container
cluster node
zabbix template
erasure coding.

AI Score

7.3

Confidence

Low

In this release, Virtuozzo Hybrid Infrastructure introduces a new serviceโ€”Backup and Restore as a Serviceโ€”as well as provides a range of new features that cover improvements in the compute services and object storage. Additionally, this release delivers stability and security improvements, and addresses issues found in previous releases.
Vulnerability id: VSTOR-59718
Introduced partially synchronous writes of memory cache limits to catch potential errors at an early stage.

Vulnerability id: VSTOR-61552
Creating a snapshot may get blocked by the process of deleting another snapshot.

Vulnerability id: VSTOR-61692
Increased the speed of volume resize operations.

Vulnerability id: VSTOR-66435
Fixed an issue with the IPsec bypass rules.

Vulnerability id: VSTOR-74476
Add recurrent tasks for handling snapshots that were not deleted completely.

Vulnerability id: VSTOR-74824
A snapshot is created incorrectly if the previous top snapshot was not removed completely.

Vulnerability id: VSTOR-75647, VSTOR-79808
Improvements in the email notification configuration.

Vulnerability id: VSTOR-75699
After a failed attempt to release a node from the backup storage, the retry is not requested until the node is back online.

Vulnerability id: VSTOR-76384
A cluster node crashed due to a race condition.

Vulnerability id: VSTOR-76628
Created a log record for a load balancer moving into the pending state.

Vulnerability id: VSTOR-76813
Live migration failed after aborting the blockcommit job.

Vulnerability id: VSTOR-77130
The chunk service in the direct_io mode fails on drives with 4k sectors.

Vulnerability id: VSTOR-77131
The admin panel shows the IP address for a domain if the DNS name is configured for the compute API.

Vulnerability id: VSTOR-78315
A storage policy name cannot be changed in the admin panel if it has a space at the end.

Vulnerability id: VSTOR-78479
NFS container archive validation may fail.

Vulnerability id: VSTOR-78664
A stability fix for the chunk service journal.

Vulnerability id: VSTOR-79332
Degradation of write speed to the backup storage with the Amazon S3 destination on high-speed connections.

Vulnerability id: VSTOR-79378
A virtual machine may get stuck in the shelving status.

Vulnerability id: VSTOR-79494
Fixed the filter value in the Neutron service log.

Vulnerability id: VSTOR-79909
A network interface may go offline after changes in its parameters.

Vulnerability id: VSTOR-79981
An inactive event loop in the S3 account control service.

Vulnerability id: VSTOR-80092
The S3 gateway crashes when trying to generate too many access keys.

Vulnerability id: VSTOR-80323
A stability improvement for the kernel updates.

Vulnerability id: VSTOR-80743
Irrelevant nodes are mentioned in the S3 service alerts.

Vulnerability id: VSTOR-81226
Improved the size calculation of erasure coding files.

Vulnerability id: VSTOR-81326
Some geo-replication metrics may drop below zero and cause an S3 service failure.

Vulnerability id: VSTOR-81343
Changing properties of an interface with VLANs results in the loss of dependent routes.

Vulnerability id: VSTOR-81530
Fixed an issue with incorrect trap names in the Zabbix template.

Vulnerability id: VSTOR-82493
Improved parsing options for commas in vinfra.

Vulnerability id: VSTOR-82506
Listing domain users fails if an admin user has locked IP addresses.

Vulnerability id: VSTOR-82639
Cluster total space increases after the chunk service restart.

Vulnerability id: VSTOR-82983
Fixed an incorrect subnet value in the documentation.

Vulnerability id: VSTOR-83102
iSCSI volumes may stop responding if moving to the Standby mode was not completed before setting the Active path.

AI Score

7.3

Confidence

Low