Resolved Issues in 5.2.2-SP4

  • Updated on Jan 30, 2026
  • Published on Jan 26, 2026
  • 3 minute(s) read
Prev Next

Networking

  • ORION-268912: Resolved an issue where an attempt to modify EBox NTP settings by running a cluster networking reconfiguration task encountered multiple CNode container restarts with the assertion failed: ((!is_raided_layout_safe() || _rio_control->is_dnode_group_deactivate_allowed(dynamic_cast<DNode *>(node_arg)))) can't deactivate dnode=<...>: can reach DU error.

  • ORION-234305: Improved the routines responsible for representation of cluster's NICs in the VMS to prevent false-positive OBJECT_DELETED and OBJECT_CREATED alerts for the NICs.

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

  • ORION-217068: Resolved an issue where following a link state change from UP to DOWN, no notification email arrived although the event was reported by the VMS.

Encryption of Data at Rest

  • ORION-268265: Improved handling of an EKM flow that involved a deleted EKM master key to avoid potential CNode container restarts.

NFS

  • ORION-262208, ORION-256109: Enhanced handling of client atime when processing NFS3 SETATTR requests against WORM-enabled views to prevent the client from getting errors in scenarios where the client atime is sent shortly after file creation.

  • ORION-261965: Made updates to tenant resolution routines to resolve an issue where NFS clients encountered intermittent RPC Error Program Unavailable errors for NFS mount requests.

SMB

  • ORION-264823: Resolved an issue that could cause CNode containers to restart with the (next(index) == INVALID_INDEX) error during SMB request processing.

  • 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.

S3

  • ORION-260816: ORION-260816: Updated handling of VAST S3 rename operations so that the cluster rejects a request to rename a directory if the target directory already exists.

  • ORION-204296: Introduced updates to improve performance when processing S3 workloads.

Protocol Auditing

  • ORION-239532: Resolved an issue where an Invalid UTF8 sequence error occurred when trying to query the VAST audit log.

VAST Catalog

  • ORION-254370: Made updates related to how deletions are handled in VAST Catalog to resolve an issue that could cause an ESTORE BIG_CATALOG deny list alert on the cluster.

Replication

  • ORION-269010: Resolved an issue that could cause synchronous replication to get stuck in the Becoming Synchronous Replication state.

  • ORION-267043: Fine-tuned internal communications related to asynchronous replication to prevent a flow that could cause Connection to Remote Peer <...> is not healthy: Communication Error alerts on the source replication peer.

  • ORION-265913: Improved handling of replicated identity policies in NDUs to prevent a flow where existing policies could be discarded due to reaching the maximum allowed number of policies per identity during an upgrade.

  • 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-225188: Eliminated a replication-related flow that could cause VMS to restart due to an out-of-memory condition.

VMS

  • ORION-269081: Resolved an issue that could cause an Exceeding the max number of host-based rules for nfs. Limit per protocol is 2048 error while the actual number of the rules being less than the cluster limit.

  • ORION-264000: Made updates to ensure that the LED on/off capability in VMS switches the LEDs on or off as expected, with the Led Status column in VAST Web UI showing a correct status for the LEDs.

  • 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.

Platform & Control

  • ORION-260678: Resolved an issue that could cause incorrect CBox serial assignment on a newly added CNode following a CNode replacement procedure.

  • ORION-259500: Resolved an issue that could cause a CNode container to restart with the ((gen_guard) != (nullptr)) (0 != nullptr) attempted to add to the references cache without a generation guard error.

  • ORION-256997: Resolved an issue that could cause CNode containers to restart due to Fiber=<...> group=_MIGRATE had a suspension timeout errors.

  • ORION-236751: Resolved an issue that could cause a CNode container to restart with the ((_memory_client_counter) > (0)) (0 > 0) error when processing NFSv4.1 workload.

Related articles