Known Issues in 5.0.0-SP16

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

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

(RESOLVED IN 5.0.0-SP30) ORION-167457: If an attempt to run a DBox replacement procedure fails, the Replace option in the DBox actions menu in VAST Web UI (Infrastructure -> DBoxes -> right-click a DBox) remains grayed out, and there is no way to make another attempt. If you encounter this issue, try running the replacement task from VAST CLI using the dbox modify --replace --force command.

ORION-205395: If during an HA event on a cluster with InfiniBand internal networking the OpenSM service is found unavailable on a CNode, the CNode may occasionally encounter a failed connecting to the leader's platform error.

ORION-155530: Sometimes after you run the cluster networking configuration script (configure_network.py) and then rebooted the CNode, the eb1 interface can still be down with the Device ib1 has different MAC address than expected, ignoring error. In this case, rerun the script after the reboot to bring the interface up.

(RESOLVED IN 5.0.0-SP24) ORION-159071: A false mtu is not configured correctly. mtu is 1500 alarm can be raised on all CNodes after upgrading to 5.0.0-SP10, although the MTU is set correctly.

(RESOLVED IN 5.2.0) ORION-178975: After creating a user quota with the identifier type set to UID, VMS lists this quota under the corresponding username pulled from the LDAP provider but not under the UID specified during quota creation.

(RESOLVED IN 5.1.0) ORION-114057: A tenant_create returned an error : ObjectCreateResultCode.FAILURE error occurs when attempting to create 256 tenants, each with a unique encryption group, if prior to this attempt, a tenant with per-tenant encryption enabled was created and then deleted.

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.

(RESOLVED IN 5.1.0-SP60, 5.2.0-SP10) ORION-216774: For views with the SMB and S3 protocols enabled and the Mixed Last Wins or SMB security flavor set, the owner of a child directory in a parent that has no default ACL, may in some cases be set incorrectly.

(RESOLVED IN 5.3.0) ORION-204972: When creating S3 objects on a multi-protocol view controlled with the NFS security flavor, in a directory for which the SGID POSIX modebit is set, the SGID modebit may get propagated to files/objects created in that directory.

(RESOLVED IN 5.0.0-SP16) ORION-175600: An NFS client would get a permission deny error when trying to read a file for which a read-only attribute has been set through SMB.

(RESOLVED IN 5.1.0-SP50) ORION-193090: The READDIR and READDIRPLUS operations against a directory with a name longer than 255 characters may hang without returning an error.

(RESOLVED IN 5.1.0) ORION-135514: The word percent in the CNode <...> nfs over rdma connections is at <...> percent alert should be read as connections, since the alert shows the number of connections but not a percentage.

(RESOLVED IN 5.0.0-SP24) ORION-160315: After upgrading to 5.0.0-SP4, a STATUS_INSUFF_SERVER_RESOURCES SMB error can be reported when the Use SMB native authentication option is enabled together with asynchronous replication due to a gap in handling of trusted forest’s group SIDs during replication.

(RESOLVED IN 5.0.0-SP24) ORION-157632: An access denied error may occur when trying to copy a newly created file or directory with a read-only attribute to a VAST SMB share.

(RESOLVED IN 5.0.0-SP24) ORION-146159: In rare cases, upon deletion of a view that had SMB, NFSv3 and NFSv4.1 enabled, the view can still be seen via SMB.

(RESOLVED IN 5.3.0) 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.

(RESOLVED IN 5.3.0) ORION-198606: In rare cases, an IO is stuck - should close alert can be raised on a CNode caused by the cluster waiting for completion of an S3 multi-part upload.

(RESOLVED IN 5.1.0) ORION-136816: S3 GET of a symlink is blocked but HeadObject and GetObjectACL operations still succeed.

(RESOLVED IN 5.0.0-SP24) ORION-156126: When adding a user in the Read-access Users field in General auditing settings (Settings -> Auditing -> General), the user name as appended with an extra ampersand (@).

(RESOLVED IN 5.1.0) ORION-134836: When displaying path details in the VAST Audit log dialog, the phandle field does not show the phandle.

ORION-163038: When importing data into a VAST Database table and there is a type mismatch between the column and the data being imported, VAST Cluster produces an ambiguous error message (Failed to get column) instead of pointing to the expected data type.

(RESOLVED IN 5.2.0, 5.1.0-SP50) ORION-196575: An attempt to bulk delete a large number of protected paths may result in a timeout in case an issue occurs during deletion of one of the protected paths.

(RESOLVED IN 5.1.0-SP30) ORION-201982: An attempt to replicate from more than eight source clusters may result in a CNode container restart with the Buffers pool is exhausted error.

ORION-183432: When trying to perform a failover using the protectedpath modify --modify-replication-state VAST CLI command, the replication state remains Standalone, although it is expected to change from Standalone to Source. If you encounter this issue, use VAST Web UI to perform the failover.

(RESOLVED IN 5.0.0-SP24) ORION-168407: S3 replication and async replication cannot be deployed on the same protected path.

(RESOLVED IN 5.2.0) 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 similar error occurs. The workaround is to manually change the destination peer's role to STANDALONE and retry the deletion.

(RESOLVED IN 5.1.0) ORION-146029: When sending call home bundles from a VAST on Cloud (VoC) cluster, the Multi-Cluster Manager (MCM) sends the first bundle an hour after the cluster has been registered, and the following bundles are sent according to the user-defined interval.

(RESOLVED IN 5.0.0-SP24) ORION-160016: When merging user group information obtained from multiple providers, duplicate user group entries can be created per user in the VAST internal database. The duplicate entries may lead to exceeding the user group limit, which makes VAST Cluster drop some of the groups, resulting in access denied errors for the user.

(RESOLVED IN 5.0.0-SP24) ORION-157986: An attempt to create an additional S3 key for an Active Directory user which has a historical SID, can fail with a UserDBResultCode.UNEXPECTED_ERROR error.

(RESOLVED IN 5.0.0-SP24) ORION-156632: If the cluster joins a child Active Directory domain and there are no Global Catalog (GC) servers in the current site, VAST Cluster is not able to discover GC servers of the top-level domain.

(RESOLVED IN 5.1.0) ORION-144288: Due to a caching issue, an incorrect user UID can be returned in a user query being retried immediately after the connectivity to the provider has been restored.

(RESOLVED IN 5.0.0-SP60) ORION-206781: A CNode bulk activation task activates only first five CNodes and ignores all the rest nodes in the batch.

ORION-203155: The Unexpected width, actual link width is <...>  alarm message may contain garbage at the end of the message.

(RESOLVED IN 5.0.0-SP60) ORION-182932: The name of the BW (Mb/s) column in the Global Snapshot Clones page (Data Protection -> Global Snapshot Clones) should read BW (MB/s) to denote megabytes per second.

(RESOLVED IN 5.0.0-SP30) ORION-182099: A local variable ‘data’ referenced before assignment error occurs when trying to access predefined analytics reports that provide information per virtual IP pool (for example, VIP Pool Bandwidth).

(RESOLVED IN 5.0.0-SP60) ORION-180832: When displayed in VAST Web UI, the definition of the CNode - ProtoMetrics,proto-name=ProtoCommon,latency (ms) event includes ms as a unit of measurement, which is typically used to denote milliseconds. However, in this particular event definition, the threshold is set in microseconds.

(RESOLVED IN 5.2.0) ORION-172811: Some analytics properties that can be selected when creating a customized analytics report, produce a graph that does not precisely correspond to the property name. For example, selecting the NFS Write IOPS property produces a graph showing the write IOPS not only for NFS but for all protocols. In particular, this issue may occur with protocol-specific and replication-related properties that represent bandwidth, IOPS and latency.

(RESOLVED IN 5.0.0-SP30) ORION-171871: When using VAST Web UI to enable the VMS Preferred option for a virtual IP pool that already exists and includes more than three CNodes, a VMS Preferred must not be True if there are less than 3 CNodes error is shown. To work around this issue, perform this operation using the vippool modify --vms-preferred --cnodes command of VAST CLI.

(RESOLVED IN 5.1.0) ORION-147658: An attempt to add a user quota for a non-existing user does not  raise an error.

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).

(RESOLVED IN 5.1.0) ORION-134765: The Rows filtered out and Rows scanned metrics in the VAST DB Row Metrics analytics report show the total number of rows accumulated over time while other metrics in the report show the number of rows per second.

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.0.0-SP60) ORION-194719: When trying to create a virtual IP pool for all tenants via VAST Web UI (Network Access -> Virtual IP Pools -> choose to create a pool -> select All Tenants in the Tenant field), VAST Cluster creates a pool for the default tenant, instead of creating a pool for all tenants.

(RESOLVED IN 5.1.0-SP30) ORION-189217: The Hardware page in VAST Web UI may display a incorrect layout image for a Mavericks DBox.

(RESOLVED IN 5.0.0-SP60) 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.

(RESOLVED IN 5.0.0-SP60) ORION-182932: The name of the BW (Mb/s) column in the Global Snapshot Clones page (Data Protection -> Global Snapshot Clones) should read BW (MB/s) to denote megabytes per second.

ORION-169645: A tip for the Atime Frequency field (Element Store -> View Policies -> choose to create or edit a view policy -> General tab) states that 3600s is the default value for this field, while the actual default is 0 (no atime updates).

(RESOLVED IN 5.0.0-SP24) ORION-160971: When renaming a database column via VAST Web UI (DataBase -> VAST DB -> drill down to columns and choose to edit a column), the field where you specify the new name is named Schema name instead of Column name.

(RESOLVED IN 5.0.0-SP24) ORION-160776: When deploying a Sanmina DBox with 30TB disks, some UI messages may show the disk capacity as 30G, not 30T.

ORION-150503: A local user cannot be found when trying to add it as a value in the Database owner field of the New Database dialog.

(RESOLVED IN 5.0.0-SP24) ORION-147147: When viewing NICs in the Infrastructure -> NICs page, the Link State column does not have UNKNOWN in the list of valid values.

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

(RESOLVED IN 5.1.0) ORION-146832:  After an existing VAST Web UI session has timed out, the Multi-Cluster Management page may display a prompt to enter a registration token for a cluster for which the token has already been provided. To eliminate the prompt, refresh the page.

(RESOLVED IN 5.1.0) ORION-146273: After deleting a cluster in the Multi-Cluster Management page, subsequent delete confirmation popups can show the Type DELETE to approve field pre-populated with the DELETE word.

(RESOLVED IN 5.1.0) ORION-143724: Some of columns in the SSDs tab of the Infrastructure page opened through Multi-Cluster Management may show dm_mock or mock dev values instead of model and firmware version numbers.

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.

(RESOLVED IN 5.1.0) ORION-141670: Relative file symlinks created through SMB are listed as directory symlinks and require use of rmdir to be deleted.

(RESOLVED IN 5.2.0) 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.

(RESOLVED IN 5.1.0) ORION-139890: The QoS policy field in the Create View or Update View dialog (Element Store -> Views -> choose to create or edit a view) can list both view QoS policies and user QoS policies, although it does not let you add a user QoS policy to the view.

(RESOLVED IN 5.0.0-SP30) ORION-181077: A cnode add command where a valid value is specified for the --cores parameter may fail with the Illegal arguments: argument --cores: invalid choice error.

(RESOLVED IN 5.0.0-SP30) ORION-174959: An attempt to run the protectedpath list --progress command results in a Command Error: Got an unexpected keyword argument 'progress' error.

(RESOLVED IN 5.0.0-SP24) ORION-165957: An attempt to run a viewpolicy show --audit command fails with the 'ViewPolicyProtocolsAudit' object has no attribute 'get' error.

(RESOLVED IN 5.0.0-SP24) ORION-163858: The supportbundle create command fails when used with the --preset callhome option.

(RESOLVED IN 5.1.0) ORION-146200: The auto-completion options for the role-assign command do not list all possible parameters.

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.

(RESOLVED IN 5.0.0-SP24) ORION-172534: The /api/capacity/capacity_estimation/ endpoint does not support directory or file names that contain a comma.

ORION-205393: After disconnecting and reconnecting an InfiniBand switch, the cluster might encounter a CNode container restart due to the assertion failed: (!has_verifier(mem_dev->dest().env_id)) Failed performing rpc call! lock_op=HAS_TEMP_REFS error.

ORION-203504: A finished redistribution and still not balanced alert can occur on the cluster when one of the CNode ports is disconnected and thus even distribution of virtual IPs among the platform ports is not possible. If there are no accompanying messages indicative of any issues, this alert can be ignored.

ORION-202806: When handling extreme workloads, CNode containers may occasionally restart with the timeout expired for life_type=16,life_gen=<number> (TRAVIS) error. The error means that the cluster is busy processing the workload. If there are no other symptoms indicative of any issues, no human intervention is required.

(RESOLVED IN 5.3.0) ORION-193956: The leader hogging for <number> us message may occasionally appear in VAST logs. If there are no accompanying messages indicative of a failure, this message can be ignored.

(RESOLVED IN 5.0.0-SP24) ORION-154985: A false BMC firmware mismatch alarm can be raised when adding some types of CNodes to the cluster.

(RESOLVED IN 5.0.0-SP24) ORION-178401: An assertion failed: ((int)base_device->get_fail_reason() == (int)DeviceFailReason::FW_VERSION_MISMATCH) error occurs when trying to perform an FRU of Intel P5800 SCM running firmware version L0310600.

(RESOLVED IN 5.1.0-SP60) ORION-158539: The back view for the CERES DBox in the Hardware Layout page shows the data ports in incorrect positions (e.g. port enp3s0f1 is shown on the right while it should be on the left). To mitigate the issue, refer to the Infrastructure -> NICs page that lists the correct locations for the ports.

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

(RESOLVED IN 5.1.0) ORION-143381: When the directory used to store call home bundles reaches its size cap, a FileNotFoundError: [Errno 2] No such file or directory error is reported instead of an out-of-space error.