Known Issues in 5.2.1-SP6

(RESOLVED IN 5.3.2) (ORION-259291: In some cases, if the Inband option is selected in the Management network field of the VAST Cluster Install wizard, the CNodes are configured as inband but the DNodes are configured as outband. If you encounter this issue, contact VAST Support for a workaround.

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

(RESOLVED IN 5.2.2) ORION-259677: The value specified in the optional Hostname Prefix field in the DBox and CBox Expansion dialog (Infrastructure -> CBoxes or DBoxes -> choose to create a new box) is not used, and the nodes are configured with the localhost.localdomain hostname instead. If you encounter this issue, contact VAST Support for a workaround.

(RESOLVED IN 5.3.0) 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-175762: In some cases, a DBox expansion procedure run on a cluster with similarity-based data reduction enabled can take longer than expected.

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

ORION-203521: VMS may generate an internal nics rate speed is not aligned alarm although NIC link speed is the same across all nodes. This is a false alarm unless it references ports on the same NIC, or ports in a CNode Port Affinity configuration (where one port is connected to an InfiniBand network and the other to an Ethernet network, or the two ports are connected to two different InfiniBand networks).

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

ORION-201552: When using CipherTrust KMIP, if an encrypted group is deleted, the encryption key may still remain on the EKM server.

(RESOLVED IN 5.3.0) ORION-196475: When a tenant is deleted, the EKM keys may still remain on the EKM server.

(RESOLVED IN 5.2.2) ORION-250829: If an attempt to create a view with a QoS policy fails, the underlying QoS object is not automatically deleted, preventing deletion of the associated QoS policy.

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.3.1) ORION-236888: When uploading a file via S3 to a view controlled with the NFS security flavor, when the view is configured so that each new file is to inherit its owning group from the parent directory (--gid inheritance bsd), the resulting file does not inherit the directory’s owner group as expected.

(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.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.2.2-SP4) ORION-260816: When performing a VAST S3 rename operation for a directory, if the target directory already exists, the cluster creates a duplicate target object instead of rejecting the request.

(RESOLVED IN 5.2.2) ORION-242283: An invalid ACL is not counted as a client error in the S3 bucket metrics.

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

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

(RESOLVED IN 5.2.2) ORION-254660: Audit log records for SMB requests against a non-default tenant configured to use SMB native authentication, may contain empty LoginName, UID and SID field values.

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

ORION-190517: VAST Cluster does not delete replicated protection policies when the associated protected path is deleted.

(RESOLVED IN 5.3.1) ORION-235789: When replicating an S3 bucket, the bucket policy attached to the bucket is replicated to the destination peer but is not applied properly to the destination bucket.

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.

(RESOLVED IN 5.3.0) ORION-154973: There can be a performance impact when deleting a very large number of files from the origin cluster. To avoid it, delete the protection policy associated with the path on the origin cluster prior to deletion.

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

(RESOLVED IN 5.2.2) ORION-259236: If user impersonation is configured for an SMB share controlled with the NFS or Mixed Last Wins security flavor, the impersonation does not become effective for the subfolders within the SMB share top folder.

(RESOLVED IN 5.3.0) ORION-210990: In VAST Web UI, the tooltip for the Bind DN field in the Active Directory provider settings (User Management -> Active Directory -> choose to create or edit an Active Directory provider) incorrectly states that the bind DN must be a superuser, although there is no such requirement for this field.

(RESOLVED IN 5.3.3) ORION-276833: The /api/prometheusmetrics/all endpoint of VAST Prometheus Exporter may include duplicate entries for exported NIC metrics.

(RESOLVED IN 5.2.2-SP4) ORION-264000: When using VMS to turn off LEDs on the cluster nodes, the LEDs change their state to off but then go back to on, with the Led Status column in the Infrastructure -> CNodes or DNodes page showing a status of UNKNOWN.

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

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

ORION-268219: Toggling the Host button in the Analytics -> Data Flow page may cause a reset of the data flow isolation settings.

ORION-255304: The Type column in the Infrastructure -> Switches page does not let you filter by each and every of the switch vendors displayed in the grid.

(RESOLVED IN 5.2.2) ORION-249163: The SMB continuous availability field in view policy settings (Element Store -> View Policies -> choose to edit a view policy) automatically changes from Enabled to Disabled when the policy is reopened for editing. To work around this issue, use the viewpolicy * commands in VAST CLI.

(RESOLVED IN 5.2.2-SP4) ORION-233805: When adding an IPv6 address to host-based access rules in an existing view policy via VAST Web UI, the VMS returns the This field may not be blank error, although the newly configured restriction is put into effect as appropriate.

(RESOLVED IN 5.4.0) ORION-207301: When you open an existing lifecycle rule for viewing or editing (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 may show KB although the values supplied and used are in bytes.

(RESOLVED IN 5.3.0) ORION-206747: The filter in the Replicated column in the Identity Policies page (User Management -> Identity Policies) does not work as expected.

(RESOLVED IN 5.3.0) ORION-205879: When viewing or editing a tenant in the Show Tenant or Update Tenant dialog (Element Store -> Tenants -> right-click a tenant and select View or Edit), the tenant’s encryption group is not displayed in the Encryption Group field, although it is displayed for the tenant in the Tenants page.

(RESOLVED IN 5.4.0) ORION-203737: The value filter in the Box column in the Infrastructure -> CNodes and DNodes pages does not work as expected.

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.

(RESOLVED IN 5.4.0) ORION-174128: The tooltip for the Include all CNodes option in the Resource Selection tab of the Add New Application dialog (Data Engine -> Applications -> choose to create an application) claims that the option is mandatory, although it is not.

(RESOLVED IN 5.3.0) 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.3.1) ORION-237114: An invalid for field 'leading_vid_or_vaid' of type U32Type: an integer is required","code":"service_unavailable"} error occurs when running the VAST CLI qospolicy attach-user command to assign a QoS policy to a user by the user's VID.

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.

(RESOLVED IN 5.2.2-SP9) ORION-279896: In rare cases involving intensive workloads, cluster events that trigger migration of virtual IPs to a different cluster node (such as activation of a new node), may cause some of the connected clients to intermittently encounter a server not responding error. For a workaround, contact VAST Support.

(RESOLVED IN 5.3.3) ORION-217946: A fan speed of 0 RPM can be falsely reported for MLK DNodes running certain firmware versions. If you encounter this issue, contact VAST Support for a workaround.

(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.4.0) 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 a 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.

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.