Resolved Issues in 5.3.2

ORION-268551: Resolved an issue where an attempt to deploy a large cluster could not proceed because of the memory allocation failed error during cluster activation.

ORION-268847: Resolved an issue that could cause an SCM layout calculation error when deploying an EBox containing Solidigm SBFPF2BV307T drives with the SCM section layout option set to Automatic in VAST Cluster Install.

ORION-267961: Enhanced support of IPv6 addressing during upgrades to eliminate a flow that could result in some of the upgraded DNodes being inaccessible after a VAST OS upgrade of a cluster configured with an IPv6 management interface.

ORION-266449: Updated cluster deployment routines to prevent the name '_build_ebox_hyperscale_conf' is not defined error that could occur when deploying an EBox.

ORION-259291: Resolved an issue due to which in some cases, if the Inband option was selected in Management network field of the VAST Cluster Install wizard, the CNodes could be configured as inband while the DNodes were configured as outband.

ORION-257696: Resolved an issue that could cause an Error in function "curl". Running async ssh cmd failed for host error during cluster deployment where IPv6 addressing was used.

ORION-238312: Enhanced upgrade routines to eliminate an issue that could cause an upgrade to fail due to the These hosts were not able to start the OpenSM service after upgrade, need to check the service and re-run error during CNode activation.

ORION-234951: Made updates to ensure that cluster networking configuration parameters supplied during cluster deployment, are not discarded when performing subsequent deployment tasks, such as adding a CBox.

ORION-258414: Resolved an issue where a DBox migration process could not complete due to the DTray matching query does not exist error occurring during the DBox add phase.

ORION-229222: Resolved an issue that could occur when replacing a Mavericks 1.0 DBox with a Mavericks 1.5 DBox, causing the DBox migration process to fail with the NOT_ENOUGH_AVAILABLE_TARGET_CAPACITY error.

ORION-270681: Made updates to ensure correct port assignments on HPE Genoa CNodes with two dual-port NICs.

ORION-247537: Made updates to prevent VMS from raising false internal NIC rate alarms on HPE IceLake nodes.

ORION-247501: Finetuned VAST DNS timeouts to ensure that if one of the configured VMS servers is not available (e.g. blocked by a firewall), the request will be able reach the next server without failing due to a timeout.

ORION-245757: Resolved an issue where a Cumulus switch could not be displayed in VAST Web UI following an upgrade of the switch firmware.

ORION-244838: Resolved an issue that prevented VMS from displaying information about NVIDIA Mellanox InfiniBand switch ports in the Infrastructure -> Switch Ports page.

ORION-265300: Made updates to prevent a flow where a severe HA event could result in some of the S3 bucket views being inaccessible through the S3 protocol.

ORION-254703: Enhanced tenant resolution logic to resolved an issue where the cluster occasionally returned access denied errors when users belonging to different tenants were using the same connection (S3 access keys).

ORION-263906: Made updates to ensure that if the configuration for a view to be created includes a setting to enable bucket logging, the logging starts immediately upon view creation.

ORION-260268: Made updates to resolve an issue that could occur with ongoing multi-part uploads started prior to an upgrade to VAST Cluster 5.3, causing the cluster to return S3 status InvalidRequest on a repeated attempt to abort such an MPU after the upgrade.

ORION-254660: Made updates to ensure that the audit log records for SMB requests against a non-default tenant configured to use SMB native authentication, contain non-empty LoginName, UID and SID field values.

ORION-266063: Improved Kafka connection management to resolve an issue that could cause a CNode container to restart with the request size=<...> api=1 is larger than max large buffer max=1400000, we shouldn't get here" error when processing Kafka workloads.

ORION-262169: Improve handling of SMB directory symlinks during asynchronous replication to resolve an issue that could cause an ESTORE REPLICATION_QUOTA_FIXER deny list alert on the replication destination cluster.

ORION-248028: Improved handling of the associations between replicated identity policies and users or groups to which the policies are to be attached, to prevent unexpected removal of the association in scenarios where the replication between the peers is stopped and then started again.

ORION-259831: Resolved an issue that could cause write-write conflict errors if an NDU is initiated at the time when there are VAST Database transactions that have been started but not completed yet.

ORION-259236: Made updates to ensure that user impersonation configured for an SMB share controlled with the NFS or Mixed Last Wins security flavor, is also effective for the subfolders within the SMB share top folder.

ORION-223630: Added support for longer Unicode LDAP DN strings (up to 1020 bytes).

ORION-264536: Resolved an issue that could cause VMS to intermittently restart with the Worker did not register heartbeat for 900 seconds error.

ORION-262422: Made updates to ensure that Data Flow analytics can be displayed as appropriate when callhome obfuscation is enabled on the cluster.

ORION-249956: Added an ability to export metrics that report S3 client and server error responses using VAST Prometheus Exporter.

ORION-249747: Added validations to ensure that a VMS manager user belonging to a certain tenant, is not allowed to manipulate views, quotas, view policies, virtual IP pools or QoS policies that are not associated with the tenant.

ORION-233805: Resolved an issue that caused the VMS to return the This field may not be blank error when adding an IPv6 address to host-based access rules in an existing view policy via VAST Web UI, although the newly configured restriction was put into effect as appropriate.

ORION-217665: Resolved an issue with NIC status alarm generation that could cause false cable disconnection alarms.

ORION-261655: Made updates to ensure that the BMC version column in the Infrastructure -> DNodes page displays complete version values for the DNodes.

ORION-249163: Updated the logic behind the SMB continuous availability field in view policy settings (Element Store -> View Policies -> choose to edit a view policy) so that it does not automatically change from Enabled to Disabled when the policy is reopened for editing.

ORION-246617: The field for setting the unit of measure for the Minimum object size and Maximum object size filters of a lifecycle rule (Element Store -> Lifecycle Rules -> choose to view or edit a rule) is now compatible with the VMS setting that stipulates use of base2 units.

ORION-271197: Added support for Solidigm SSDPF2NV153TZO SSDs in an EBox.

ORION-264357: Resolved an issue that could cause a CNode container to restart due to the ((new_chunk_size + INITIAL_BLOCK_OVERHEAD) >= (block_upgrade_ctx-<_io_buffer-<data_size())) (16302 >= 16253) Upgrade/downgrade function has run out of block capacity error.

ORION-256300: Made updates to prevent a flow that could trigger Sanmina DNode deactivation followed by temporary service disruption.

ORION-256301: Updated the logic responsible for handling SMB locks to resolve an issue that could cause CNode containers to restart with the waiting for a lock for too long (195000ms). aka- passed max compare and swap retries error when processing SMB workload.

ORION-254706: Resolved an issue where multiple CNode containers restarted due to the assertion failed: (!_value.is_nan()) error when processing a Spark query.

ORION-253097: Made updates to eliminate false slow boot-devices detected alerts on Ceres DNodes with Micron PCIe Gen4 boot drives.

ORION-242346: Made updates to ensure that replacement of a very large number of SSDs at the same time does not result in CNode containers being restarted due to the after deactivation of drive=<...> dbox=<...> will be at risk to have insufficient drives for mioc state and (load_successful) this might mean that system_format failed earlier <...> or that loading mioc failed due to unavailable dboxes/drives errors.

ORION-246724: Resolved an issue where support bundle collection from all of the CNodes could not be completed due to an internal timeout.