---
title: "Resolved Issues in 5.3.0-SP8"
slug: "resolved-issues-in-530-sp8"
updated: 2026-10-27T17:24:31Z
published: 2026-10-27T17:24:31Z
canonical: "docs.vastdata.com/resolved-issues-in-530-sp8"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vastdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Resolved Issues in 5.3.0-SP8

## Install & Upgrade

- ORION-250937: Resolved an issue that could cause the `Error in function "get_drives_fw_versions". Failed sending ssh commands` error when trying to activate an EBox.
- ORION-251652: Eliminated a flow where the cluster installation procedure could not complete because of the `AttributeError: 'NoneType' object has no attribute 'name'` error when trying to upgrade from a VAST OS version prior to 12.14.6-1673751 to VAST Cluster 5.3.
- ORION-254913: Updated pre-upgrade validations to avoid raising a false `Fan interfaces have fan_status=None, but 'OK' expected` error when the actual hardware does not have any fan issues.

## Quality of Service (QoS)

- ORION-244936: Made updates to prevent unexpected decrease of read performance after applying a QoS policy that imposes a minimum QoS.

## VMS

- ORION-232477: Eliminated a potential race condition in VAST Prometheus Exporter that could cause some metrics to be missing due to the `could not obtain lock on row in relation "vmsapp_view"` error.

## VAST Web UI

- ORION-251819: Made updates to avoid raising the `Cannot reset default_retention_period! It must have a default value.` error when trying to set the object lock retention period to *None* (Element Store -> Views -> choose to edit a view -> S3 tab -> Object Lock tab -> Retention Mode).
- ORION-247427: Updated the logic behind the object size unit selector in lifecycle rule settings (Element Store -> Lifecycle Rules -> choose to create or edit a rule -> Object size pane) so that the UI does not substitute *Bytes* with *KB* when viewing or editing a lifecycle rule that was originally defined with *Bytes*.

## Platform & Control

- ORION-243331: Enhanced handling of *mtime* updates on CNodes to eliminate a flow that could cause a `non-synced clocks detected` alert during an upgrade.
- ORION-236781: Introduced optimizations to improve write performance when running some types of workloads on Supermicro EBoxes.