Resolved Issues in 5.2.0-SP17

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

Resolved Issues in 5.2.0-SP17

Install & Upgrade

  • ORION-238980: Improved the way SAML SSO user records are handled in the VAST internal database during upgrades to eliminate a potential upgrade flow where VMS could not be started on any CNode due to a column "password_id" of relation "permissions_manager" contains null values error.

  • ORION-244564: Improved NDU routines so that running an extremely heavy S3 workload while the cluster is being upgraded to version 5.2 does not cause the upgrade to fail due to the assertion failed: (((int)eres) != ((int)EStoreRes::TIMEOUT)) (26 != 26) timeout when updating contained_count after we just waited for transaction to clear error.

Quality of Service (QoS)

  • ORION-244936: Made updates to prevent unexpected decrease of read performance after applying a QoS policy that imposes a minimum QoS.

Data Protection

  • ORION-233459: Resolved an issue that could, in some cases, cause VMS to report the protected path failover status with a significant delay.

VMS

  • ORION-241365: Enhanced VMS validations to ensure that the root directory (/) of the default tenant cannot be deleted by VMS users.

Platform & Control

  • ORION-243331: Enhanced handling of mtime updates on CNodes to eliminate a flow that could cause a non-synced clocks detected alert during an upgrade.

Related articles