Known Issues in 5.4.0

• (RESOLVED IN 5.4.1-SP5) ORION-329066: An  assertion failed: ((bytes_consumed_by_deserialize) == (serialized_size))  error may occur on an attempt to activate a CNode on a cluster that used to be configured with identity policies in version 5.0 and is now being upgraded to 5.4.

• ORION-270710: For some NVIDIA Mellanox NICs, the firmware upgrade process may take much longer than expected. Sometimes, a VMS timeout alert may be raised but the process still completes successfully. If a flint upgrade failure occurs during the process, try power-cycling the node.

• ORION-220738: In some cases, VMS does not provide any alerts or other status indication when a drive gets disabled while the newly added DBox is being initialized.

• ORION-175762: In some cases, a DBox expansion procedure run on a cluster with similarity-based data reduction enabled can take longer than expected.

• ORION-236122: Intense read workloads may impact performance on views controlled with a QoS policy with the prioritization flag set.

• ORION-139913: When applying a QoS policy to NFSv3 access, both data and metadata are taken into account in QoS limit calculations, while with NFSv4.1, only data are considered.

• ORION-137986: Enabling a QoS policy for a view on which a mixed (read and write) workload runs, can result in decreased performance for the workload.

• ORION-318379: When creating subdirectories through NFS, some of the subdirectories may sporadically fail to inherit the default ACL from the parent directory.

• (RESOLVED IN 5.4.0-SP2) ORION-295189: When an NFS client running Rocky 8 or later, creates a child directory in a parent that has default ACLs of rwx for user, group and other, the child directory gets incorrect permissions of other::r-x instead of other::rwx.

• ORION-238708: In some cases, an NFSv4.1 client attempting to move files to the trash folder may get a Permission denied error due to an issue that may cause the trash folder to use a more restricting policy than expected.

• (RESOLVED IN 5.4.1-SP5) ORION-323152: macOS clients may occasionally encounter an ​RPC struct is bad​​ error when moving, deleting or renaming files via SMB, although the operation completes successfully.

• ORION-142968: If a quota is exceeded during the process of coping a file to the VAST cluster, the copying process is stopped with a misleading error message: A device attached to the system is not functioning.

S3

• ORION-196170: When a parent and child NFSv4.1 view both have same ABAC tags on them, an attempt to mount the child view may result in a Permission denied error. If this occurs, try setting the ABAC tags for the machine account that the client uses to mount the view.

• (RESOLVED IN 5.4.1) ORION-293900:  When streaming S3 event notifications or VAST DataEngine function-triggering events to a VAST Event Broker view on a cluster with multiple VAST Event Broker views belonging to different tenants, some of the event notifications may encounter a flow that prevents them from being sent to their destination. If this occurs, an Internal Kafka target supported only a single tenant GUID, got 2 alert will be raised. With VAST DataEngine enabled, this issue may result in some functions not being triggered as expected.

• ORION-140894: When attempting to delete a protected path from the destination peer after an ungraceful failover, a Failed to delete following streams or a similar error occurs. The workaround is to manually change the destination peer's role to STANDALONE and retry the deletion.

• ORION-145307: Bulk permission updates are not supported for files and directories on satellite clusters.

• ORION-25479: Latin characters are not supported with LDAP. If you attempt to pass, for example, a username encoded with a Latin character set, the 'LDAP sanity check res: Invalid credentials' error is returned.

• ORION-332874: Cluster's attempts to send email notifications through SMTP may fail with a ​certificate verify failed: self-signed certificate (_ssl.c:1006)​​ error. If you encounter this issue, contact VAST Support for a workaround.

• ORION-329549: In some cases after a cluster upgrade or expansion, the Analytics -> Data Flow and Analytics -> Top Actors pages of VAST Web UI may show the No data to display error instead of actual workload data. If you encounter this issue, contact VAST Support for a workaround.

• ORION-300508: Some metrics may not be available in VAST Prometheus Exporter. Missing metrics include (but may be not limited to) CNode and DNode hardware metrics or CPU temperature, utilization, memory percentage, PCI error count, retransmitted segments, total correctable/uncorrectable memory errors. If you encounter this issue, contact VAST Support for a workaround.

• ORION-292325: When creating a customized analytics report for block volumes or hosts, some metrics intended to reflect a maximum latency are set to a fixed value when there are no block volumes on the cluster.

• (RESOLVED IN 5.4.1) ORION-291686: The read and write latency shown in the Analytics -> Data Flow page of VAST Web UI is calculated without taking into account the amount of I/O on each of the cluster nodes.

• ORION-282603: User-made changes to the ​csi​​ role (one of default administrative roles on the cluster) are not preserved during an upgrade.

• ORION-143717: On a cluster with CNode Port Affinity configured, there is no way to expose the VAST DNS IP on a specific port (left or right).

• ORION-131386: When there is a parent directory that has a very large number of child directories, a total of children’s capacity values displayed in the Capacity page can exceed the capacity value shown for the parent directory.

• ORION-89570: In some cases, capacity analytics for subdirectories cannot be reported due to an internal timeout. This issue occurs when there is an extremely large number of subdirectories to be estimated.

• (RESOLVED IN 5.4.1) ORION-290976: When creating an Active Directory or LDAP provider configuration on the VAST cluster, the attribute mapping fields are read-only. To edit these fields, save the provider configuration, then open it for editing and update the fields as needed.

• ORION-281960: The Activate Write Buffer RAID button (Settings -> Cluster -> General Cluster Setup and Actions -> Write Buffer RAID pane) is not grayed out when the feature has already been activated on the cluster.

• ORION-246284: When entering a value in the Capacity field in the Quota Rules tab in quota settings (Element Store -> Quotas -> choose to create or edit a quota), the UI can unexpectedly alter the value when the user is backspacing or trying to add a decimal point.

• ORION-260502: The Capacity Estimation page (Analytics -> Capacity), which is designed to display capacity for directories or, in case of a VAST Database, for its schema, sometimes also includes VAST Database tables in capacity estimations.

• ORION-239505: The VAST Web UI toggles for selecting operations to be logged in the syslog (Settings -> Notifications -> Syslog Setup) do not enforce logging of the selected operation types as expected. If you encounter this issue, contact VAST Support for a workaround.

• ORION-234835: Some VAST Web UI pages might not allow for proper filtering or sorting by column where value presentation differs from that in the VAST internal database.

• ORION-203189: The External Netmask field in cluster networking settings (Settings -> Configure Network) does not accept alphabetic characters.

• ORION-175189: When querying a local user using the Aggregated context, the Leading GID and Primary group SID fields in the User Details dialog have a value of -1 instead of an empty string.

• ORION-322120: When displaying path names in VAST CLI, the names written in right-to-left languages may appear spelled from left to right.

• ORION-282853: In some cases, changing the view path by using the view modify --path <new path> command does not work as expected. The command may seem to succeed initially but automatically revert back to the original path within minutes.

• ORION-269350: An illegal argument error occurs when trying to run the protectedpath list command with the --protection-policy-name option specified.

• ORION-156628: An attempt to run the viewpolicy show --audit command results in a 'ViewPolicyProtocolsAudit' object has no attribute 'get' error.

• ORION-178569: The /users/names endpoint always returns only the first 50 entries, regardless of the page size parameter or the total amount of entries to be returned.

• ORION-255054: Once a DNode replacement operation is complete, the old node may still be listed in the Infrastructure -> DNodes page of VAST Web UI for some minutes.

• ORION-269349: When obfuscating a support bundle, the obfuscation is not applied to files that have already been zipped.

• ORION-239170: When obfuscating a support bundle, the CNode hostname may not get obfuscated in some of the logs included in the bundle.