Known Issues in 5.2.0-SP4

(RESOLVED IN 5.2.0-SP15) ORION-236788: An attempt to deploy a cluster with more than one CERES DBox where B2B IPMI is not in use, can fail with the assert ipmi configuration failed 1 times: [Exception('Overlapping IPMI IPs were found in DTray-dbox<...> DTray-dbox-<...>')] error. If you encounter this issue, rerun the VAST Easy Install procedure with the B2B - IPMI option enabled.

(RESOLVED IN 5.2.0-SP6) ORION-216386: A Prod mode for Call Home is not enabled. Are you sure you want to continue? warning may appear when saving the parameters for the VAST Easy Install procedure. This warning can be ignored. To continue, click the Yes button in the warning popup.

(RESOLVED IN 5.2.0-SP6) ORION-210281: VMS version may be automatically promoted as a result of CNode activation even when there is no new version installed. Due to this issue, VMS upgrade may be skipped during a subsequent upgrade procedure.

(RESOLVED IN 5.2.0-SP6) ORION-206577: On clusters with InfiniBand internal networking, the OpenSM service does not automatically start on the CNodes upon completion of the VAST Easy Install procedure, resulting in OpenSM is not enabled correctly alerts on the cluster. If this occurs, contact VAST Support to start the OpenSM service manually.

(RESOLVED IN 5.2.0-SP6) ORION-201844: When completing the VAST Easy Install wizard, if you supply an incorrect number of DNode IPMI IPs, VAST Cluster displays the wrong count of dnode ipmi ips error message that contains an incorrect indication of the IPs to be supplied.

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.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.0-SP7) ORION-219774: In some cases, the Identifier field in the Users Accounting tab in quota settings (Element Store -> Quotas -> choose to create or update a quota) displays the user's VAST ID (VID) instead of the user's username or UID.

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.2.0-SP6) ORION-201538: The lifecycle rule mechanism deletes empty directories that were created through NFS and SMB protocols on the view for which a lifecycle rule is enabled, even when the empty directories are not expired according to the enabled lifecycle rule.

(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.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.2.0-SP15) ORION-235601: On views controlled with the NFS security flavor with POSIX ACLs enabled, a permission translation issue may occur when a file inherits its ACL from the parent directory, resulting in unexpected Permission denied errors when an NFSv3 user, being a member of a group present in the ACL, tries to access a file created through NFSv4.

(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.0-SP10) ORION-227797: VAST Cluster does not support trailing checksums included in a an S3 request with the x-amz-trailer header. If the request contains a trailing checksum, the checksum is not recognized as such and is appended to the request body.

(RESOLVED IN 5.2.0-SP20) ORION-217661: If the final part of a multipart upload has a size of 0 (zero), VAST Cluster responds with a 400 Bad Request error.

(RESOLVED IN 5.2.0-SP20) ORION-213741: Bucket logging cannot be effectively disabled after enabling it for a view. After toggling the Enable bucket logging option off, the feature state changes to disabled for a short time and then goes back to enabled.

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

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.2.0-SP6) ORION-200613: In some cases, which might depend on the current user, an attempt to disable Access-Based Enumeration (ABE) that was previously set for a view, results in a UserDBResultCode.INVALID_ARGUMENT error.

(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.2.0-SP10) ORION-217267: When trying to modify the lists of read access users or groups in protocol auditing settings (Settings -> Auditing -> General tab -> Read access Users and Read access Groups fields) by removing users and groups that are not available on the local provider any longer, a don't exist on the system error is raised and the read access lists do not get updated as expected.

(RESOLVED IN 5.2.0-SP6) ORION-215317: An attempt to drop a VAST Database table that is used as a source for an existing semi-sorted projection may fail if the source table is subject to a quota or replication.

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

(RESOLVED IN 5.1.0-SP56) ORION-209079: Assigning a VLAN to application CNodes (e.g. Data Engine -> Applications -> choose to create or edit an application -> Network tab -> VLAN field) does not work as expected, resulting in incorrect network configuration.

(RESOLVED IN 5.2.0-SP6) ORION-209151: An attempt to create an S3 bucket under a path protected with a local backup protection policy (used to take local snapshots) results in a S3 is not allowed on this tenant because the tenant contains protected paths error.

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

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.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.2.1) ORION-232589: If the cluster being upgraded from version 5.1 to version 5.2 has webhook setup for sending event alarms to third-party applications, the VMS may end up in a restart loop due to the DataError: value too long for type character varying(256) error.

(RESOLVED IN 5.2.1) ORION-221021: The CNode write latency event definition contains the word 'read' instead of 'write' in the description text. The event description should read: CNode <CNode> write latency is {threshold} micro seconds.

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.

(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.2.0-SP10) ORION-218961: The SMB allow and SMB disallow options in the Active Directory provider right-click menu (User Management -> Active Directory -> right-click an entry) do not change their state to grayed out as expected.

(RESOLVED IN 5.2.0-SP6) ORION-217317: Changes made to the default POSIX modebits in the Update Policy dialog (Element Store -> View Policies -> choose to update a policy -> Default POSIX modebits tab) cannot be saved and do not take effect. Use VAST CLI's viewpolicy modify --smb-file-mode or viewpolicy modify --smb-directory-mode commands instead.

(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.1) ORION-246581: VMS automatically selects the DEFAULT section layout for Solidigm SBFPF2BV307T hard drives, while the correct layout would be THIRTY_TB_DRIVES.

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

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