Known Issues in 5.1.2-SP1

ORION-145815: In some cases, VAST Cluster does not raise an alert on a wrong NIC firmware version during a cluster upgrade.

ORION-184301: When adding a CBox to the cluster using VAST Web UI, the external NICs are added even when the option to skip external NICs is selected.

ORION-183372: If a cluster has the Write Buffer RAID capability enabled, cluster expansion is only possible if all the SCMs in all DBoxes are of the same size.

ORION-173816: VAST Cluster does not block expansion from CERES 15TB to CERES 60TB, although such expansion is not supported.

ORION-184225: When doing non-disruptive network reconfiguration from VAST Web UI (Settings -> Configure Network -> click Expand to open the External (MGMT IPs) - MTU definitions pane), the Mgmt IP field does not work as expected when an IPv6 address is entered.

ORION-185008: Modifying a subnet in an existing virtual IP pool may result in the pool being not accessible by clients. To work around the issue, delete the existing pool and create a new one with the subnet you want.

ORION-179201: When listing SMB shares that reside on a VAST cluster, the share path field may show the share name but not the complete path.

ORION-155854: If you run a command to release locks twice in a row, the number of locks that VMS reports as successfully released for the second run includes the released locks both from the first run and from the second run.

ORION-144020: When use of Kerberos/NTLM authentication to authorize SMB users from non-trusting domains is enabled for the tenant, 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-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.

ORION-188749: The view policy option that restricts S3 read/write access based on client IP addresses (in VAST Web UI: Element Store -> View Policies -> choose to create or edit a view policy -> Host-Based Access -> S3 pane -> Read/Write) does not work for bucket-level operations, such as creating or deleting a bucket.

ORION-182790: VAST Cluster returns an incorrect error code, MalformedACLError, on attempts to put an object or bucket ACL based on a non-existing user email address.

ORION-176151: When creating a view with many 50-character ABAC tags in VAST Web UI, an ABAC tags were not set, they were inherited from another view instead error message can be displayed although no ABAC tag inheritance occurs. To avoid this message, try reducing the length of ABAC tags by one character.

ORION-171054: If an NFSv4.1-enabled view has ABAC tags assigned, an attempt to mount a nested view through NFSv4.1 fails with a Permissions Denied error.

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-160555: If a leader CNode HA event occurs during encryption group rotation, the rotation cannot be completed, and there is no indication that the rotation was not performed.

ORION-175036: The vast.rpc.import_data RPC, when used on VAST Cluster 5.1.0 with Trino 429, may fail to import data from multiple Parquet files due to the Procedure not registered: rpc.import_data error. If that occurs, try importing with the following command:

INSERT INTO vast."<bucket name>/<schema name>"."<table_name> vast.import_data" ("$parquet_file_path") 
VALUES (<parquet1>), ..., (<parquetN>) 

ORION-144137: User quotas for Alternate Data Stream (ADS) children might get miscalculated at the replication destination when the size and/or used attributes of an ADS child are updated due to replication.

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-154973: Prior to making massive deletions (from the on-premises cluster) on a path that is configured to be replicated to a remote cluster, you need to delete the protection policy associated with this path on the on-premises cluster to avoid deletion performance degradation.

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

ORION-156168: In a multi-forest environment, after migrating a group account from the forest of the cluster’s joined domain to another forest, information about historical group membership is not kept, so users in the migrated group might not be able to access resources to which they used to have access prior to the migration.

ORION-175334: When creating a managed application (Data Engine -> Applications -> choose to create an application), VMS does not block attempts to set port membership for CNodes on a cluster that does not support CNode Port Affinity.

ORION-168744: Occasionally, some local users that can be seen under User Management in VAST Web UI, cannot be found in relevant fields of other VAST Cluster features.

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-246617: When creating or editing a lifecycle rule (Element Store -> Lifecycle Rules -> choose to view or edit a rule), the field for setting the unit of measure for the Minimum object size and Maximum object size filters is not compatible with the VMS setting that stipulates use of base2 units. It is recommended to switch to base10 before using this field.

ORION-184012: An attempt to export VAST Catalog query results to a CSV file results in a Query: Please correct the form error with no CSV file generated.

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-175071: The number 9223372036854775807 shown in the tooltip for the Files and directories field under Settings -> Cluster -> General -> Global Access Cache Limits refers to the maximum number of files and directories that VMS can handle. When using VAST Web UI, the number that can be saved for this field, may be less depending on the capabilities of your browser.

ORION-147073: The Database page does not show the actual number of rows and size of objects until the page is refreshed manually.

ORION-142547: Clicking the Vast catalog policy link in the Policy column of the Snapshots page in Multi-Cluster Management opens an empty Protection Policies page instead of showing a specific policy.

ORION-140652: Auto-completion for the Logon name of the privileged domain user field in tenant settings (Element Store -> Tenants -> choose to create or edit a tenant) is not provided.

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-184206: An attempt to run a cbox list command fails 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: An attempt to attach an identity policy to a local user with the user modify --identity-policy-ids command results in a S3 Policies with the following ID don't exist error.

ORION-174843: An attempt to specify the --tenant-ids option on the role create command results in an unrecognized argument error.

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

ORION-184359: The minimum number of DBoxes required to implement DBox High Availability is 12 (twelve), which is one DBox more than stated in the documentation.

ORION-173461: Slot numbers displayed in the Slot column of the Infrastructure -> SCMs page in VAST Web UI are not aligned with slot numbers displayed in the Hardware Layout page.

ORION-162393: In some cases, a SSD failure during DBox migration might result in an failed op=RECOVER_DISK for 1500 times in a row in shard_id={ mega_shard_id=<...> mega_shard_count=<...>}. last failure res=9 will denylist op on this shard alert on a CNode. If you encounter this issue, contact VAST Support to clear the alert and complete the operation.