Resolved Issues in 5.2.0

ORION-207794: Updated upgrade routines to eliminate a flow where the upgrade could not be completed due to a docker cp command failure.

ORION-189672: Enhanced the logic behind the Northband option that can be selected for the management network during a VAST Easy Install process so that the option applies to CNodes only. Prior to this change, an attempt to run the installation process with the Northband option selected would fail with the northband is supported only on cnodes and only those with 2 HCAs error.

ORION-182412: Updated pre-upgrade validations to skip inactive SCMs when checking for locked NVRAMs so that this check does not cause the AttributeError("'NoneType' object has no attribute 'host'") error during an upgrade.

ORION-109128: Resolved an issue where during installation of a cluster with B2B IPMI, an SSH connection to CNodes 1, 3, and 4 (per CBox) could not be established using the expected technician port IP.

ORION-196907: Improved cluster networking configuration routines to avoid an issue that could occur during CNode FRU procedure, resulting in a failed to fetch new IPV6 error when trying to activate the new HPE IceLake CNode.

ORION-184225: Enhanced the logic behind the Mgmt IP field of the non-disruptive network reconfiguration wizard (Settings -> Configure Network -> click Expand to open the External (MGMT IPs) - MTU definitions pane) in VAST Web UI to properly handle IPv6 addresses.

ORION-179941: Enhanced IB switch monitoring functionality to prevent raising OpenSM is not enabled correctly alerts for hosts that have the OpenSM service in the masked state.

ORION-175251: Updated the cluster’s networking configuration script (configure_network.py) to use port enp211s0f0 as the B2B IPMI port when creating a B2B IPMI configuration on a cluster with MLK DNodes.

ORION-136815: Updated NIS refresh routines to resolve an issue where NIS could not be refreshed after adding new NIS servers to the cluster.

ORION-115298: Made updates so that the functionality of setting a TTL when configuring the VAST DNS service works as expected (Network Access -> DNS -> Create DNS Service -> TTL field).

ORION-176635: Resolved an issue that could cause an assertion failed: (inserted) couldn't insert source handle to mapping (created two images for same handle in same crate?!) alert on the cluster.

ORION-139891: Fine-tuned file listing timeouts to prevent high latency spikes on write operations when dealing with non-nested directories that contain a very large number of files.

ORION-65250: Enhanced cluster behavior upon removal of a directory with a very large number of files to the trash folder so that such a removal, as well as any subsequent removals, can be reflected in quota information without delay. Prior to this change, the quota capacity reclamation tasks could get stuck and the freed capacity could be seen in capacity pages but not in quotas.

ORION-178975: Resolved an issue where after creating a user quota with the identifier type set to UID, VMS listed this quota under the corresponding username pulled from the LDAP provider but not under the UID specified during quota creation.

ORION-172465: Enhanced the quota update logic to eliminate an issue that could cause a defined user quota to stop being displayed in VAST Web UI and VAST CLI, although the quota was enforced as expected.

ORION-169675: Updated the quota deletion logic to prevent a flow where after hitting the quota limit and removing the quota to continue write operations on a path, any write attempt to the path still failed due to the quota limit exceeded.

ORION-165483: Eliminated an issue that could occur when a user QoS policy was set to limit both bandwidth and IOPS, causing the sum of write metrics on two views accessed by the user to be much lower than the limits set by the policy.

ORION-178975: Resolved an issue where after creating a user quota with the identifier type set to UID, VMS listed this quota under the corresponding username pulled from the LDAP provider but not under the UID specified during quota creation.

ORION-122505: Updated protocol auditing to eliminate an issue that could cause a CNode container to restart with the timeout expired for life_type=29,life_gen=551782 (AUDIT_LOGS) error.

ORION-171796: Removed an internal limitation on the maximum number of NFSv4.1 lock owners which could cause the Out of NFSv4 handles for silo and NFS4 owners pool usage is at full capacity alerts.

ORION-179201: On newly installed clusters with version 5.2 and higher, when listing SMB shares on a VAST cluster, a complete share path is shown for shares residing on a VAST cluster (with all directory names separated by backward slashes). On clusters upgraded to version 5.2, the share path field would show the share name preceded with a slash.

ORION-179067: Updated SMB processing to avoid flows where the VAST cluster could respond with an information structure of an incorrect size, causing INFO LENGTH MISMATCH errors on the client.

ORION-173222: Fine-tuned TCP session keep-alive timeouts to avoid a scenario where increased latency could be occasionally encountered on file read attempts.

ORION-145507: Improved handling of SMB compounded related requests to eliminate a corner-case scenario where a file read error could occur.

ORION-189731: Resolved the issue where an attempt to create an S3 Bucket view with the ACLs disabled option enabled, could result in the view created with ACLs enabled instead.

ORION-187046: Updated internal bucket synchronization routines to resolve an issue where, occasionally, after enabling or disabling an ACL on a bucket VMS reported the correct ACL enabled/disabled state for a short time and then changed it back to the previous state.

ORION-176151: Updated ABAC-related limits so that creating a view with many 50-character ABAC tags in VAST Web UI does not result in an ABAC tags were not set, they were inherited from another view instead message while no ABAC tag inheritance occurs.

ORION-166268: Updated ABAC validations to allow a user with ABAC attributes that provide read/write access to an ABAC-tagged view, to list files and directories on the view when the associated view policy sets All Squash for the host.

ORION-184012: Resolved an issue that was causing the Query: Please correct the form error when trying to export VAST Catalog query results to a CSV file in VAST Web UI.

ORION-189280: Made updates to prevent deletion of VAST Database elements even if the S3 lifecycle rules configured on the cluster stipulate the deletion.

ORION-178460: Resolved an issue that could cause a Got an error: Must pass at least one table error when running queries against a VAST database using VAST Database CLI (vast-db-cli).

ORION-196575: Updated routines responsible for bulk deletion of protected paths so that failure to delete one of the paths in the group does not entail timeout errors for the other paths being deleted.

ORION-177810: Enhanced handling of date and time in protection policies so that VAST Web UI always shows the local timezone date and time. Prior to this change, a UTC time could be displayed in some cases.

ORION-196091: Improved the flow for protected path creation to ensure that no objects are created or displayed in VAST Cluster as a result of attempts to create a protected paths with incorrect settings (for example, to create a path with a target directory that already exists on the destination peer).

ORION-181145: Enhanced handling of group SIDs to resolve an issue that could cause UDB2 lookup user on sid=<SID> failed to return a token alerts during async replication.

ORION-166445: Introduced a number of enhancements to prevent a scenario where based on existing protection policies, local snapshots were created but were not delivered to the remote site, with many missed PRO alerts reported at the remote site.

ORION-165822: Resolved an issue where after setting both async replication peers of a replicating protected path to Standalone state, the peers could not resync and begin replication again.

ORION-160019: Updated the async replication certificate expiration alerts so that they can trigger notifications to admin users. Prior to this change, the alerts were visible to root and support users only.

ORION-144137: Resolved an issue that could cause miscalculation of user quotas for Alternate Data Stream (ADS) children at the replication destination when the size and/or used attributes of an ADS child are updated due to replication.

ORION-175331:  Added a validation to ensure that when creating a managed application in WAST Web UI (Data Engine -> Applications -> choose to create an application), the count of virtual IPs entered for worker nodes in the Network tab does not exceed the count of selected CNodes (in the Resource Selection tab).

ORION-179744: Made updates to prevent CNode container restarts in case a client initiates a user refresh (which entails clearing of the internal database cache and retrieving all the user information from a provider) too frequently within a short period of time.

ORION-179713: Enhanced the Active Directory configuration creation routines to stop domain auto-discovery with a proper error message if a network configuration error was encountered during the discovery process.

ORION-167553: Changed the behavior to ignore character case when matching ABAC tags assigned to views to ABAC attribute values assigned to users. ABAC tags are now case-insensitive. For example, tags AB and ab are considered the same value. Prior to this change, VAST Cluster was taking the case into account; tags such as AB and ab were considered different values, resulting in permission deny error for the user.

ORION-176490: Made updates to the logic behind the VAST Prometheus Exporter endpoints to ensure that they provide same or more capabilities than the deprecated exporter script.

ORION-198768: Fine-tuned the logic of VMS accessing the internal database to resolve an issue that could cause a large number of key='APPLY_LOGS_OBFUSCATION' failed retrieved from DB messages to appear in the VMS log.

ORION-194862: Updated view path validations to allow for view paths or SMB share names that include any UTF8 characters. Prior to this change, an attempt to create a view with a path that included a non-ASCII character resulted in an error.

ORION-194555: Fine-tuned timeouts related to LDAP create/modify flows to resolve an issue where an attempt to change the LDAP authentication method from SIMPLE to SASL failed with the ObjectModifyResultCode.INVALID_PARAM error.

ORION-193904: Enhanced handling of alarm metadata to resolve an issue that caused the 'NoneType' object has no attribute 'update' error when trying to acknowledge a NIC error alarm via VMS.

ORION-186672: Enhanced the logic for VMS manager password expiration to ensure that a temporary password set for a VMS manager expires according to the configured password expiration options. With this change, the following minimum valid values are introduced:

ORION-180832: Updated the event definition creation flow to always use microseconds as the unit of measurement for latency.

ORION-175424: Enhanced internal database cleanup logic to prevent issues that might occur when there are multiple entities with the same user name/UID and different VIDs, such as the "detail":"get() returned more than one QuotaEntityInfo error when attempting to run a userquota create command in VAST CLI.

ORION-172955: Improved error handling to report ??? as a CNode status in cases where the node’s NIC responds with junk data to VMS polling (due to cabling issues, for example). Prior to this change, VMS would report an empty status and log an UTF-8 decode error in such cases.

ORION-172811: Enhanced the logic behind user selection of properties to be displayed in an analytics report in VAST Web UI (Analytics -> Analytics -> Customized Analytics -> choose to create a custom report -> choose an Object Type and select properties to be included in the report) so that the displayed data always matches the properties selected. Prior to this change, some inconsistencies were possible, e.g. selecting NFS Write IOPS property produced a graph showing the write IOPS not only for NFS but for all protocols.

ORION-168744: Enhanced handling of users created in the local provider to eliminate flows where some local users that could be seen under User Management in VAST Web UI, could not be found in relevant fields of other VAST Cluster features.

ORION-201832: Improved cursor behavior when a user makes changes in the Configure Network page.

ORION-196513: Improved usability and performance when dealing with a large number of client IP ranges defined for a tenant (Element Store -> Tenants -> choose to create or edit a tenant -> Tenant Access tab).

ORION-194719: Updated the logic used to select tenants when creating a virtual IP pool in VAST Web UI so that the All tenants option creates a virtual IP pool for all tenants but not for the default tenant only.

ORION-182932: Updated the header of the BW (MB/s) column in the Global Snapshot Clones page (Data Protection -> Global Snapshot Clones) to read MB/s for megabytes per second.

ORION-184206: Updated the logic behind the cbox list and cbox show commands so that the commands do not fail with the Invalid value for `subsystem`, must be a value greater than or equal to `1` error if the cluster uses subsystem 0.

ORION-175435: Made updates so that an attempt to attach an identity policy to a user with the ‘user modify --identity-policy-ids’ command does not result in a “S3 Policies with the following ID don't exist” error.

ORION-174843: Updated the logic behind the role create command to avoid throwing an unrecognized argument error when the --tenant-ids option is specified.

ORION-181114, ORION-167477: Made updates for the /views/ endpoint to correctly return the S3 object ownership rule when listing views.

ORION-167477: Made update for the /views/ endpoint to correctly return the S3 object ownership rule when listing views.

ORION-198918: Resolved an issue that could cause a CNode container to restart with the assertion failed: ((local_old_value) != (P::INVALID_LOCKER_ID)) error.

ORION-196174: Made updates to ensure that VAST Cluster can be used with switches running Cumulus Linux 5.9.1 and higher.

ORION-194580: Resolved an issue that could case a CNode container to restart with the timeout expired for life_type=16,life_gen=56378412 (TRAVIS) wit 1 active jobs error.

ORION-191470: Resolved an issue that could cause a rename failed after retries=4633 alert on the cluster.

ORION-190107: Updated RDMA routines to avoid a flow where an attempt to create an NFS mount using RDMA over IPv6 could be rejected with the Connection refused error.

ORION-189215: Resolved an issue that could cause high memory usage alerts on many of the cluster’s CNodes.

ORION-188866: Resolved an issue that could cause multiple CNode containers to restart with the Child chunk not found in composite for handle error after finishing the upgrade of the last CNode during an NDU process.

ORION-187942: Resolved an issue that could cause multiple CNode containers to restart with the group=W_MIGRATE had a suspension timeout error.

ORION-184359: Decreased the minimum number of DBoxes required to implement DBox High Availability from 12 (twelve) to 11 (eleven).

ORION-180071: Resolved an issue that could cause periodic CNode container restarts with the failed to allocate vmsg args for GetUpdatedS3UsersParams error.

ORION-179428: Fine-tuned the mechanism of sorting stripes during defragmentation to resolve an issue that caused multiple the stripe is stuck alerts on the cluster.

ORION-178833: Made enhancements to prevent raising a DNode mem is not equal across hosts alarm for a DNode that is is still initializing.

ORION-177324: Resolved an issue where a cluster encountered extended high latency accompanied with a The publishers of capacity estimations are not keeping up alert after massive data deletions.

ORION-175323: Enhanced handling of syslog-related tasks to prevent performance issues when discovering new nodes during cluster expansion while the cluster is busy with client workload.

ORION-171966: Resolved an issue where the VMS encountered an out-of memory condition but VMS failover to a different CNode was not initiated automatically.

ORION-171916: Enhanced handling of NIC IDs to ensure that there are no duplicate entries created as a result of hardware polling operations.

ORION-168687: Resolved an issue that could cause CNode container restarts with the assertion failed: (num_lockable_retries < 600) (600 < 600) when handling SMB workload from clients sending a vary large amount of of SMB lock requests.

ORION-164306: Resolved an issue that could case very high latency during S3 workload processing.

ORION-163148: Updated the mechanism of splitting the data into chunks for processing to prevent it from causing a series of CNode container restarts due to an unhandled exception.

ORION-150291: Resolved an issue that could cause an assertion failed: (should_reconnect) VMsg rejected ILLEGAL RDMA connection request alert upon activation of a CNode that was previously deactivated.

ORION-141766: Adjusted SMB-related timeouts to prevent a flow that could cause CNode containers to restart with the assertion failed: (obj->wait_for_no_inflight()) error followed by the SMB POST_DECODE deny list alert.