---
title: "Resolved Issues in 5.3.2-SP6"
slug: "resolved-issues-in-532-sp6"
updated: 2026-10-27T17:24:19Z
published: 2026-10-27T17:24:19Z
canonical: "docs.vastdata.com/resolved-issues-in-532-sp6"
---

> ## 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.2-SP6

## Install & Upgrade

- ORION-279911: Resolved an issue that could cause the `Failed to extract tarball: [Errno 2] No such file or directory: '/vast/bundles/<release>.vast.tar.gz'` error when using the option to upgrade the cluster to a target release package uploaded to a CNode.
- ORION-274013: Resolved an issue that could cause an upgrade procedure to fail with the `Unexpected exception timed out waiting for next successful run of poll hw task` error.
- ORION-273642: Resolved an issue where multiple CNode containers restarted during an upgrade due to the `invalid StreamState enum value: 11` error.
- ORION-272702: Enhanced the upgrade routines so that in case an upgrade bundle is not found on the node being upgraded, the RPMs are taken from the node where VMS runs, ensuring that the no-bundle node gets upgraded as appropriate.
- ORION-276442: Resolved an issue where an attempt to upgrade the cluster could not succeed due to the `assertion failed: ((num_buckets) > (0)) (0 > 0)` error.

## Cluster Expansion

- ORION-277857: Resolved an issue where an attempt to run DBox expansion could not succeed due to the `Not enough space for all write buffers` error.

## Networking

- ORION-270122: Resolved an issue where an attempt to run the cluster networking configuration script (`configure_network.py`) could not succeed due to an `invalid syntax` error.

## Element Store

- ORION-278559: Disabled an optimization that could cause a `content_verifier is not monotonic?!` alert on the cluster.

## S3

- ORION-277800: Improved the way bucket logging is done on a closing HTTPS socket to eliminate a flow that could result in denylisting S3 workloads.