Resolved Issues in 5.2.0-SP22

Prev Next

Install & Upgrade

  • ORION-243433: Adjusted cluster installation routines so that hardware polling does not cause the installation to be stuck for a long time.

  • ORION-247826: Resolved an issue that could cause the pre-upgrade validation routine to raise the Unexpected exception timed out waiting for next successful run of poll hw task error, due to which the upgrade could not be completed.

  • ORION-240767, ORION-182380: Fine-tuned internal SSH timeout values to avoid early failure of the VAST installation procedure due to the wait_for_ssh_ready reached timeout error.

Replication

  • ORION-244821: Resolved an issue that could cause multiple CNode containers to restart with the request-> sender.env_id < MAX_ENVS_PER_SYSTEM error after enabling asynchronous replication from a cluster running VAST release 5.1 to a 5.2 cluster.

VMS

  • ORION-246611: Updated Analytics reports to include the SchedulerMetrics,window_runtime__avg metrics per CNode. Prior to this change, the metric was available for the entire cluster only.

  • ORION-243727: Added labels alias, share and bucket to metrics that represent performance of particular users on a specific view (vast_user_view_*).

  • ORION-170119: Made updates to OpenSM log processing to ensure that VMS raises state change alerts for switch ports.

VAST Web UI

  • ORION-244912: Made updates to ensure that opening a DNS configuration for editing and then saving it without making any changes does not result in reset of the CNode selection settings for the DNS.

Platform & Control

  • ORION-248114: Updated internal routines to eliminate a flow that could cause temporary service disruption with the waiting for a lock for too long (195000ms). aka- passed max compare and swap retries. and timeout expired for @life_type=1,life_gen=1230025 (INGEST_WRITE) errors when processing an extremely large number of simultaneous write operations and replication streams.

  • ORION-249401: Resolved an issue that could cause multiple CNode containers to restart with the waiting for a lock for too long (195000ms). aka- passed max compare and swap retries error.