Resolved Issues in 5.2.0-SP6

  • Published on Feb 21, 2026
  • 7 minute(s) read
Prev Next

Install & Upgrade

  • ORION-216721: Updated cluster deployment routines to avoid a flow where the VAST Easy Install procedure could not be started anew after having failed on the first attempt to deploy the cluster.

  • ORION-216388: Resolved an issue that could cause a VAST Easy Install procedure to hang on clusters with InfiniBand internal networking because of inability to automatically start the OpenSM service after reboot.

  • ORION-216387: Updated handling of SuperMicro Genoa CBox serial numbers during cluster installation so that the number displayed as a CBox serial number in the VAST Easy Install discovery results matches the CBox product serial (the one returned using IPMI tools). Prior to this change, the box's chassis serial was displayed instead.

  • ORION-216386: Made updates to avoid showing the Prod mode for Call Home is not enabled. Are you sure you want to continue? warning when saving the parameters for VAST Easy Install.

  • ORION-210281: Resolved an issue due to which VMS version could be automatically promoted as a result of CNode activation even when there was no new version installed.

  • ORION-201844: Updated the wrong count of dnode ipmi ips error message displayed if you supply an incorrect number of DNode IPMI IPs during VAST Easy Install to correctly state the suggested number of IPs.

  • ORION-201373: Improved validation of IP addresses entered in the VAST Easy Install fields to prevent entry of duplicate IPs.

  • ORION-206577: Made updates to automatically enable OpenSM service upon completion of the VAST Easy Install procedure for clusters with InfiniBand internal networking.

DNode Replacement

  • ORION-204099: Updated the DNode replacement logic to ensure that it correctly determines the node to be replaced based on the node's IPv6 address.

Networking

  • ORION-206544: Updated OpenSM configuration validations to avoid raising a Wrong OpenSM configuration alert in case the configuration has been manually changed to one that is different from the default.

  • ORION-202586: Enhanced the logic that assigns the technician port IP during cluster networking configuration to block assignment of a technician IP that conflicts with the existing customer management network.

Element Store

  • ORION-204347: Resolved an issue that could cause an ESTORE CPOI_SCRUBBER deny list alert on the cluster.

  • ORION-193665: Enhanced handling of scenarios where a directory is being deleted by both the Trash Folder feature and the Lifecycle Rules feature at the same time, which could previously result in a ESTORE TREE_UNLINKER deny list alert.

Lifecycle Rules

  • ORION-201538: Updated the lifecycle rule functionality to delete empty directories only if they are expired per lifecycle rule enabled for the view. Prior to this change, empty directories that were created through NFS and SMB protocols on the view for which a lifecycle rule is enabled, could get deleted even when they were not expired.

NFS

  • ORION-211906: Made updates to ensure there is no performance degradation when processing some specific NFS workload types.

SMB

  • ORION-203797: Enhanced handling of group SIDs when using SMB native authentication to resolve an issue that could cause permission denied errors when trying to access an SMB share with share-levels ACLs enabled.

  • ORION-196448: Enhanced handling of historical SIDs to eliminate a flow that could result in a change of the group referenced in the share’s ACE upon migration of the user group from one Active Directory domain to another.

Access-Based Enumeration (ABE)

  • ORION-200613: Eliminated a flow where attempts by some users to disable Access-Based Enumeration (ABE) for a view could result in an UserDBResultCode.INVALID_ARGUMENT error.

VAST Catalog

  • ORION-201923: Resolved an issue that could cause a Please collect a bundle and three 30-mins hubbles: with row_id=<...> handle=<...>, and handle=<...> alert when the cluster has VAST Catalog enabled.

  • ORION-173787: Added a limitation on the number of filesystem snapshots that can be created per VAST Catalog protection policy. A maximum of 500 snapshots are allowed. The limitation helps eliminate a flow that could result in a reaching halt_writes splittability issue alert followed by the BIG_CATALOG deny list imposed on the cluster.

VAST Database

  • ORION-218771: Made updates to avoid a flow where the VAST Database table size and row count displayed in VAST Web UI (DataBase -> VAST Database -> choose a schema and display a table) could change while there were no table modifications made.

  • ORION-215317: Resolved an issue that could cause an error on an attempt to drop a VAST Database table that was used as a source for an existing semi-sorted projection and was subject to a quota or replication.

Data Protection

  • ORION-209151: Updated internal validations to prevent raising the S3 is not allowed on this tenant because the tenant contains protected paths error on an attempt to create an S3 bucket under a path protected with a local backup protection policy (used to take local snapshots).

Replication

  • ORION-218749: Resolved an issue where disconnection of both northbound ports on the source cluster's CNode could cause the S3 synchronous replication state to change to BECOMING_SOURCE_WAITING_FOR_PEER, with the replication stream not recovered as expected.

  • ORION-213476: Updated replication initial synchronization routines to resolve an issue that could cause multiple allocated 90% of mooktze buffers! top consumer is REPLICATION_INIT_NAME_CONTENT_LOOKUP_TREE and assertion failed: (success) Failed write locking an RWSpinlock for 100000 times- couldn't finalize the write lock alerts on the cluster.

  • ORION-210898: Introduced enhancements to prevent errors caused by timeouts when using replicating between clusters with a very large number of S3 users.

  • ORION-201912: Resolved an issue that could cause a NATIVE_REPLICATION deny list alert on multiple CNodes due to the assertion failed: (false) UDBTranslate::convert_vid_to_user_identity failed to translate vid=<...> error.

Authentication & Authorization

  • ORION-207742: Resolved an issue that could cause an unknown vsetting found: IGNORE_DISABLED_USERS error following an upgrade from VAST Cluster 5.0.

  • ORION-198357: Updated S3 replication routines to avoid overwriting an existing identity policy if it is identical to the replicated identity policy. This ensures that the policy ID remains the same, preventing failed to fetch s3 policies: list s3 identity policies error: ErrorCode.InternalError VMS errors that could be encountered following events such as cluster migration.

VMS

  • ORION-208184: Eliminated a false could not fetch next ip alarm that could be encountered when using VAST DNS with some specific workloads.

  • ORION-205162: Enhanced the way VMS reports link state changes to avoid false alarms.

  • ORION-203155: Made updates to prevent garbage at the end of the link width alarm message Unexpected width, actual link width is <...>.

  • ORION-194297: Resolved an issue that could in some cases result in a Data Flow page not presenting any data.

  • ORION-193437: Fine-tuned VMS worker and task management timeouts to avoid a flow that could cause VMS tasks to hang and, in some cases, could result in a VMS restart.

VAST Web UI

  • ORION-218749: Updated the logic behind the SMB allow and SMB disallow options in the Active Directory provider right-click menu (User Management -> Active Directory -> right-click an entry) so that the options become grayed out when the corresponding action cannot be performed.

  • ORION-217317: Updated the logic behind the Default POSIX modebits tab of the Update Policy dialog (Element Store -> View Policies -> choose to update a policy) to ensure that changes in the mode bits are saved and take effect as expected.

  • ORION-201828: Updated the tooltips for External Netmask and IPMI Netmask fields in VAST Easy Install and Configure Network dialogs to show a valid subnet mask.

VAST REST API

  • ORION-191918: Updated the logic behind the /iodata/ endpoint to properly return values for host, user, vip, vippool, cnode and view fields. Prior to this change, object IDs could be returned instead of actual values.

Platform & Control

  • ORION-214394: Added an alert that provides notification in case of SSD media errors.

  • ORION-214262: Resolved an issue that could cause multiple CNode containers to restart with the assertion failed: ((stack_size_left) > (0)) (-5184 > 0) Stack overflow! error.

  • ORION-211493: Resolved an issue that could cause an EBox upgrade to get stuck because of incorrect handling of isolated CPU settings.

  • ORION-211063: Resolved an issue that could cause multiple CNode containers to restart with the assertion failed: (pre_compression_encode == current_chunk->_dr_header->pre_compression_encode) error followed by a DATA_REWRITE deny list alert on an attempt to run data rewrite after having enabled similarity-based data reduction.

  • ORION-207363: Updated cluster HA routines to prevent a flow where deactivation of a DNode for a BMC firmware upgrade could cause temporary service disruption.

  • ORION-205410: Improved handling of IPMI command timeouts to avoid a flow that could result in a DNode container restart due to the BMC not responsive error.

  • ORION-204265: Resolved an issue that could cause a CNode container restart with the assertion failed: (acl_buf == nullptr) file=src/proto/common/allocated_acl.hpp:28 function=void *Proto::EncodedAceBuffer::alloc(uint32_t) silo=<...> error.

  • ORION-202803: Resolved an issue that could case a DNode container to restart with the spinlock lock takes too long: 1835, cannot kill locker silo error.

  • ORION-200149: Added a mechanism to prevent scenarios where a hardware issue could result in a mix of two internal metadata blocks during reactivation of a DTray, causing multiple deny lists and CNode container restarts.

  • ORION-199628: Updated BMC firmware validations to avoid raising the DNode BMC Version is not up to date alert when firmware version 11.17 is used on all DNodes.

  • ORION-199409: Resolved an issue where the leader node could not connect to the DNodes due to the Failed to read the CC register SPDK error.

  • ORION-198928: Resolved an issue where during recovery from drive failures, the CNode container restarted with the assertion failed: (!assert_empty) list is empty error, followed by a ESTORE MIGRATE deny list alert.

  • ORION-194336: Resolved an issue that could cause a CNode container restart with the killing pid=<...> at time=<...>: silo=<...> is stuck for <...> ms error.

  • ORION-182589: Fine-tuned internal timeouts to avoid a flow that could result in a CNode container restart due to a get_denylist_events operation timeout.

  • ORION-183745: Improved handling of CNode and DNode communication issues to prevent a scenario where following an IB switch reboot, all CNode containers restarted and DNode failures were encountered with the can't deactivate dnode: can reach DU error.

Related articles