Resolved Issues in 5.3.1

ORION-249921: Resolved an issue that could occur on some clusters with lifecycle rules configured, where the leading CNode could not start due to the failed to upgrade schema table for export <export> error, causing the upgrade task to hang.

ORION-245073: Resolved an issue where during a VAST OS upgrade, an active DNode was brought down due to the failed device threshold exceeded error, causing the upgrade task to fail with the Exception during async running tasks for Disabling nodes error.

ORION-237742: Updated VAST Cluster Install so that firmware upgrade is by default included in the installation procedure.

ORION-221554: Resolved an issue where an attempt to update a tenant during cluster upgrade caused CNodes containers to restart.

ORION-241045: Made updates to prevent the VAST cluster from generating interface names that are longer than 15 characters, which could previously cause multiple CNode containers to restart with the (len < (int)sizeof(label_with_device) && len > 0 && len >= MAX_LABEL_LENGTH) error.

ORION-230979: Updated the cluster networking configuration script (configure_network.py) to support the auto-ports-ext-iface = 'northband' option for Supermicro Gen5 (Genoa) CNodes. (This option configures the management interface on one of the two data network ports.)

ORION-226377: Adjusted the functionality that monitors OpenSM status on clusters with both internal and external IB interfaces so that it runs ibdiagnet commands on internal interfaces only.

ORION-208862: For clusters with internal IB networking, enhanced OpenSM validations with a mechanism to periodically update the ibdiag.conf file on the CNodes based on the current interface availability.

ORION-241559: Added support for the MAVERICKS_15_TO_SIXTY_TB_DELTA_LAYOUT layout during the DBox migration procedure.

ORION-208221: Updated quota notification emails to indicate blocked users and blocked groups separately. Prior to this change, both users and groups were listed in the Blocked users field.

ORION-236888: Updated the permission inheritance logic to honor the view's GID inheritance setting of BSD so that each new file being uploaded via S3 to an NFS flavor-controlled view with this setting, inherits its owning group from the parent directory.

ORION-252534: Changed the way the VAST cluster handles NFSv3 create requests that include the atime for a file on a WORM-enabled view. Prior to this change, such requests could be intermittently rejected with a permission denied error by the WORM retention logic. Starting with this release, for this type of requests, the VAST cluster ignores the incoming atime if it is less than or equal to the current time.

ORION-216835: Updated the logic used to handle SMB QUERY_DIRECTORY requests with the SMB2_RETURN_SINGLE_ENTRY flag so that when the client sends three such requests in sequence, the VAST cluster does not omit the first item found in the directory.

ORION-216381: Made updates to support CIFS mounts without the noserverino flag.

ORION-213061: Improved handling of stuck S3 HTTPS connections to eliminate a flow where the VAST cluster could ignore S3 HTTPS connection attempts by new clients because the maximum number of connections was reached.

ORION-242283: Made updates so that an invalid ACL is counted as a client error in the bucket metrics.

ORION-235815: Improved handling of S3 requests signed with Signature v4 to avoid returning status code 403 due to signature mismatch in case the request contained multiple Content-Encoding headers.

ORION-241386:  Updated Access-Based Enumeration (ABE) logic so that it does not prevent SMB privileged users from listing the contents of ABE-enabled views.

ORION-178696: Removed a validation that could prevent configuring a path as a local protected path and a replication protected path at the same time.

ORION-235789: Made updates to ensure that in case of replication of an S3 bucket, the bucket policy attached to the bucket is replicated and applied to the destination bucket as appropriate.

ORION-192002: Enhanced VMS monitoring capabilities so that it can monitor the state of the rsyslog service on the CNodes and raise an alert if the service is not up and running.

ORION-249742: Updated the logic behind the NTLM enabled toggle in the Advanced tab of Active Directory provider settings (User Management -> Active Directory -> choose to update a provider) so that the toggle is disabled if the cluster has already joined an Active Directory domain.

ORION-246284: Updated the logic behind the field that sets the unit of measure for soft and hard quota limits (Element Store -> Quotas -> choose to create or edit a quota -> Quota Rules tab) so that it does not replace the user-supplied unit of measure (e.g. PiB) with Bytes upon saving changes and reopening the dialog while the VMS is set to use base2 units.

ORION-237114: Resolved an issue that could cause the invalid for field 'leading_vid_or_vaid' of type U32Type: an integer is required","code":"service_unavailable"} error when running the VAST CLI qospolicy attach-user command to assign a QoS policy to a user by the user's VAST ID (VID).

ORION-188468: Provided a more accurate error message to be shown on an attempt to run the user query --vid command without the --context option specified.

ORION-214067: Made updates to VAST REST API documentation to eliminate discrepancies between the documentation and actual API parameters.

ORION-260144: Made updates to eliminate a flow that could occur on Ceres v1 and v2 clusters with NVRAM HA, where after physical replacement of NVRAMs, an attempt to revert to original NVRAMs could in some cases cause the cluster's leading CNode to fail due to the can't fail nvram=<...> (can reach DU) error.

ORION-239236: Resolved an issue that could cause an ingest_handle_event denylist due to CNode containers restarting with the assertion failed: (version->has_val()) fiber-cluster-version was not set for this fiber, you probably need to use FiberClusterVersionGuard before accessing this function error.