Resolved Issues in 5.1.0-SP56

  • Updated on Jan 30, 2026
  • Published on Jan 28, 2026
  • 2 minute(s) read
Prev Next

Install & Upgrade

  • ORION-216721: Updated cluster deployment routines to avoid a flow where the VAST Easy Install procedure could not be started anew after having failed on the first attempt to deploy the cluster.

  • ORION-215200: Enhanced cluster hardware validations so that no 'types.SimpleNamespace' object has no attribute 'bmc_upgrade' error occurs when running the pre-upgrade validation task.

  • ORION-207794: Updated upgrade routines to eliminate a flow where the upgrade could not be completed due to a docker cp command failure.

  • ORION-207170: Resolved an issue that could cause multiple CNode containers to restart with an assertion failed: (((int)res) != ((int)EStore::EStoreRes::TIMEOUT)) (26 != 26) waiting for the completion of @truman_tid=<...> error after initiating an OS and firmware upgrade on the cluster.

  • ORION-204309: Resolved an issue that could cause an cp: cannot stat '/tmp/bundle/bmc/x86_64/libcrypto.so.6': No such file or directory error when trying to run a BMC or firmware upgrade on a Mavericks Dbox.

  • ORION-202969: Resolved an issue that could cause a NoneType object has no attribute is_b2b_configuration error when adding the boxes that have been discovered during the cluster installation procedure.

  • ORION-201422: Updated VAST Easy Install routines to correctly set the IPMI B2B address for SuperMicro Genoa CBoxes.

Cluster Expansion

  • ORION-217979: Resolved an issue where during cluster expansion, no new CNodes could be automatically discovered, and an attempt to add the nodes manually resulted in an add_cnode() got an unexpected keyword argument 'cluster_id' error.

  • ORION-184006: Updated cluster expansion routines to ensure that rack, subsystem and hostname parameters are set correctly for the newly added boxes during the expansion.

Element Store

  • ORION-214869: Resolved an issue that could cause multiple CNode container restarts due to the timeout expired for @life_type=16,life_gen=<...> (TRAVIS) error.

NFS

  • ORION-216344: Updated handling of POSIX ACLs to eliminate a flow where NFSv3 access to a file created in a directory controlled with the defalt ACL by a client that does not overwrite ACLs upon creation (such as the Windows SMB client) could in some cases be denied for members of the group that owns the file, except for the file owner user.

S3

  • ORION-227797: Made updates to return an error if an S3 request contains the x-amz-trailer heading.

  • ORION-215970: Improved handling of HEAD Object requests to eliminate a potential race condition that could cause subsequent delete requests to fail.

VAST Data Engine

  • ORION-209079: Updated the cluster networking configuration script (configure_network.py) so that it supports use of VLANs for application CNodes. Prior to this change, VLANs could be assigned to application CNodes in VAST Web UI or VAST CLI, but the resulting configuration could be incorrect.

VAST Web UI

  • ORION-217317: Updated the logic behind the Default POSIX modebits tab of the Update Policy dialog (Element Store -> View Policies -> choose to update a policy) to ensure that changes in the mode bits are saved and take effect as expected.

Platform & Control

  • ORION-222175: Fine-tuned internal timeouts to eliminate a flow where a SSD failure could lead to a failure of two DNodes in the same Mavericks DBox.

VAST REST API

  • ORION-192652: Made updates to eliminate discrepancies between the API documentation for the /token/ endpoint and actual API responses.

Related articles