Resolved Issues in 5.3.0

ORION-184301: Updated the logic behind the CBox add wizard to ensure that the option to skip external NICs is honored as appropriate.

ORION-217557: Resolved an issue where during cluster networking configuration, incorrect IP addresses could be assigned to the management ports on a cluster where only IPv6 addressing was used.

ORION-203289: Improved port status checks to eliminate a flow where some hosts could encounter NFS connectivity issues following a switch replacement.

ORION-202575: Added a validation to ensure that IP addresses entered as arguments to the cluster networking configuration script (configure_network.py) do not include hyphens or dashes.

ORION-193428: Improved handling of SSL sockets to eliminate a flow where CNode containers could restart with the msg=release_ips or msg=assign_vips_from_bucket errors following modification of the CNodes' virtual IP pool.

ORION-234379: Improved lock management routines to resolve an issue that could cause multiple CNode containers to restart with the assertion failed: (did_lock) error.

ORION-196475: Introduced updates to ensure that upon deletion of a tenant, the EKM keys associated with the tenant get deleted from the EKM server.

ORION-216774: Resolved an issue that could cause incorrect setting of the directory owner for child directories of a parent that had no default ACL on views with the SMB and S3 protocols enabled and the Mixed Last Wins or SMB security flavor set.

ORION-204972: Made updates to prevent propagation of the SGID POSIX modebit to files/objects created in a directory that has the bit set, on a multi-protocol view controlled with the NFS security flavor.

ORION-205404: Resolved an issue where high read latency could be observed on one of the cluster's CNodes when processing a specific NFS workload.

ORION-187096: Resolved an issue that could occasionally cause NFS3ERR_STALE errors when attempting to mount an NFSv3 share after a seamless failover.

ORION-173200: Resolved an issue that could cause a permission error when attempting to access an SMB share if the user had only Traverse and List Folder permissions.

ORION-144020: Resolved an issue where after enabling use of Kerberos/NTLM authentication to authorize SMB users from non-trusting domains, a Windows client would let you add a new ACE only by searching for a specific user in the list of trusted forest users, instead of locating the user through the list of domains.

ORION-217661: Removed a restriction that caused VAST Cluster to reject zero-sized parts in a multipart upload with a 400 Bad Request error.

ORION-217396: Optimized processing of S3 listing requests to avoid increased read latency at the time when the cluster is busy handling multiple listing requests with a very large number of items.

ORION-213741: Resolved an issue where after toggling the Enable bucket logging option off, the feature state changed to Disabled for a short time and then went back to Enabled.

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

ORION-198606: Improved the logic used to wait for completion of an S3 multi-part upload so that it does not cause an IO is stuck - should close alert on the cluster.

ORION-182790: VAST Cluster now returns the UnresolvableGrantByEmailAddress S3 error code on attempts to put an object or bucket ACL based on a non-existing user email address. Prior to this change, the MalformedACLError error code was returned.

ORION-136153: Improved the way VAST Cluster handles multi-part uploads that include an extremely large number of objects to avoid performance degradation.

ORION-203287: Made updates to ensure VAST Cluster creates an audit log entry for an SMB CLOSE operation when the operation involves file deletion.

ORION-211566: Resolved an issue that could cause an error when trying to create a local protected path or a global snapshot clone on an S3 bucket view for which Write Once Read Many (WORM) was enabled.

ORION-204141: Added validations to prevent changing or deleting of replication peers on the replication destination cluster.

ORION-164710: Improved capacity estimations to prevent skewing in cases where local and remote capacity figures differ significantly and the remote capacity amounts to a significant portion of the overall capacity.

ORION-193259: Resolved an issue that could prevent creation of a VAST on Cloud (AWS) instance in a region different from the one used for Multi-Cluster Manager.

ORION-210990: Updated the tooltip for the Bind DN field in the Active Directory provider settings (User Management -> Active Directory -> choose to create or edit an Active Directory provider) so that it does not imply that the bind DN must be a superuser.

ORION-235592: Resolved an issue that could cause an error when attempting to establish an SSH connection through SSO to a cluster with a management virtual IP being an IPv6 address.

ORION-216977: Updated the message that VMS issues to report the beginning of a bulk permission update to state that the second path in the message is a subpath on the view: Bulk permission update on tenant <tenant>, view <view path> subpath / started.

ORION-206747: Updated the filter in the Replicated column in the Identity Policies page (User Management -> Identity Policies) to filter entries by the Replicated status as appropriate.

ORION-205879: Updated the Encryption Group field in tenant settings (Element Store -> Tenants -> choose to view or edit a tenant) to display the currently assigned encryption group. Prior to this change, the group was not shown, although it was displayed when viewing the tenant in the Tenants page.

ORION-198847: Made updates to avoid triggering the SSH REMOTE HOST IDENTIFICATION HAS CHANGED! warning when logging into VAST CLI from a CNode that does not run VMS.

ORION-214371: Eliminated a flow that could cause temporary service disruption due to an internal race condition.

ORION-193956: Resolved an issue that could cause a leader hogging for <number> us alert message to occasionally appear in VAST logs when using IceLake (HPE) CBoxes.

ORION-158539: Updated the Hardware Layout for the CERES DBox so that the the back view shows each data port in the left or right position as appropriate.