Resolved Issues in 5.0.0-SP70

Prev Next

Cluster Expansion

  • ORION-204266: Improved handling of BMC firmware versions to eliminate an issue that could cause a BMC matching query does not exist error when trying to add a Mavericks MLK DBox to the cluster.

Networking

  • ORION-203521: Improved NIC link rate validations to avoid generating a false internal nics rate speed is not aligned alarm.

Element Store

  • ORION-207892: Resolved an issue which could cause the cluster to encounter a assertion failed: (eres != EStoreRes::OK) ranges_to_mark not empty alert followed by denylisting @handle=<handle> as traversal_type=19 resulted with res=PERSISTENT_ERROR and then locally denylisting shard_type=0 shard_id=<shard> as op=DELETE_ELEMENT resulted with res=28 deny list alerts.

  • ORION-206865: Enhanced Alternate Data Stream (ADS) handling to eliminate a flow that could result in a CNode container restart with the assertion failed: (!at_least_one_generation_taken) at least one generation type is taken by this fiber or an ancestor fiber in context that expects error.

Replication

  • ORION-204928: Resolved an issue that could cause a false clone_id=1000065870 is MISSING but should have existed alarm associated with a previously deleted replication stream.

Platform & Control

  • ORION-197141: Resolved an issue that could prevent adding new Cumulus 5.9.1 switches in VAST Web UI.