Known Issues in 5.3.1

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

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-173816: VAST Cluster does not block expansion from CERES 15TB to CERES 60TB, although such expansion is not supported.

ORION-228412: When running the cluster networking configuration script (configure_network.py) with both auto_ports_ext_iface=northband and auto_ports_skip_nic=ext options specified, no error is raised although this combination of options may result in incorrect network configuration.

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

(RESOLVED IN 5.4.0) ORION-243368: Prioritization of workloads based on the QoS policy prioritization flag is not supported if the policy also has burst and/or total limits defined.

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

(RESOLVED IN 5.4.0) ORION-231253: When the cluster-wide write bandwidth limit is set, the actual performance can be up to 10% off from the limit specified. For example, if the limit is set to 7.5GB, the actual performance would be about 6.6GB.

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

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.2) ORION-263906: When you create a view and the view configuration includes a setting to enable bucket logging, the logging does not start immediately upon view creation. To start bucket logging, you need to update it (e.g. in VAST Web UI, re-open the view for editing and save it without changing the view configuration).

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

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

(RESOLVED IN 5.3.2-SP7) ORION-272853: The functionality that lets you set a new indestructibility password in VAST Web UI (Settings -> Indestructibility) does not work as expected. Use the VAST CLI indestructibility modify command instead.

(RESOLVED IN 5.4.0) ORION-233749: VAST Cluster does not automatically delete access keys associated with a replication destination tenant which has been 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.

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

(RESOLVED IN 5.4.0) ORION-230479: A false Periodic readiness check failed for OS upgrade alarm may be raised on a VoC on GCP cluster. This alarm can be ignored; it occurs due to OS upgrade validation which is not relevant for VoC clusters.

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

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-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.3.3) ORION-276833: The /api/prometheusmetrics/all endpoint of VAST Prometheus Exporter may include duplicate entries for exported NIC metrics.

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

(RESOLVED IN 5.3.2) ORION-262422: The Data Flow page of VAST Web UI displays the No data to display error when callhome obfuscation is enabled on the cluster.

(RESOLVED IN 5.3.3) ORION-238083: The VMS option to power off an EBox does not work as expected. In some cases, the power off task can be reported as complete although the box is inactive but not powered off.

ORION-225432: Some metrics listed under Analytics -> Predefined Analytics in VAST Web UI may be unavailable for EBoxes.

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.

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

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

ORION-246972: The Add Volumes manually option in the Map Volumes dialog (Data Protection -> Snapshots -> right-click a snapshot and choose Map Snapshot Volumes) does not start the volume mapping process.

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.

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

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

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.

(RESOLVED IN 5.4.0) ORION-232944: When clicking the Power off option in the CNode page of VAST Web UI (Infrastructure -> CNodes -> right-click a node), the node gets deactivated but not powered off. To power it off, click Power off one more time.

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

(RESOLVED IN 5.4.0) ORION-238168: If you try to delete a support bundle that is still in the process of being created, the creation process does not stop and the bundle does not get deleted immediately.