Release 3.18.1

New Feature Tech Preview

api-service: Support new maintenance APIs for stopping, starting, and restarting a specific logical node on a Lightbits server. Note that these APIs are introduced in this release for evaluative purposes only, and should not be invoked in a production cluster.

LBM1-39365

Enhancement

Added a new field exposing via get/list volume response (available only in json/yaml format in lbcli) the protection group identifier (pgUUID) of the volumes.

LBM1-40409

Enhancement

Added openstack os-brick configuration to check discovery-client health in a custom network (not just localhost).

LBM1-42202

Enhancement

Changed AEN for deleted volumes to only notify the necessary clients - thus reducing the overhead and load on the servers/nodes as well as the client machines following delete volume operations.

LBM1-39262

Enhancement

duroslight: Improved data integrity checks by adding the LBA number to the object header.

LBM1-40379

Enhancement

duroslight: Improved data integrity checks by adding a checksum to block headers, in addition to the existing checksum on the stored data.

LBM1-38653

Enhancement

Changed Ansible chrony role to skip configuration if the service is already configured.

LBM1-22143

Enhancement

Grafana: Added journal SSD latency and bandwidth plots to the server performance dashboard.

LBM1-36841

Enhancement

New Grafana panels were added in node-tab and cluster-tab dashboards, presenting a provisioning ratio gauge. New Prometheus alert rules were added for 200% and 400% over-provisioning.

LBM1-39802

Enhancement

Removed excess log messages from the exporter log file.

LBM1-36159

Enhancement

During offline installation, RPMs in the target directory are now cleared before copying new files.

LBM1-32399

Enhancement

Updated the default values of automatically generated keys from none (-m0) to SHA512 (-m3).

LBM1-42334

Major

Fixed a bug related to incorrect error handling that might occur during the handling of a change in a volume's protection state, which under certain circumstances can lead to service loss.

LBM1-39742

Major

Fixed a bug where a node could crash when powering up from an abrupt failure in the rare case where the volume containing the most recently written data is deleted just before an NVMe device failure. The system also completes the full rebuild before any new writes are issued to any volume replicated on that node.

LBM1-41068

Major

Fixed a rare issue where an abrupt shutdown during writing of the last unit in storage (on the first iteration) resulted in no available writes after recovery.

LBM1-40284

Major

Fixed a bug where under an extremely rare race condition that can occur during background garbage collection while two successive snapshots are deleted, it is possible for data from an older volume snapshot to overwrite more recent data.

LBM1-40626

Major

node-manager & etcd: Reduced Etcd's leader election timeout for new installations. In rare cases, if the Etcd leader experiences slowness (e.g., due to a malfunctioning disk), lightbits-nodes could miss heartbeats and become inactive before Etcd followers trigger a new leader election. By lowering the leader election timeout, leader elections now occur promptly, preventing nodes from incorrectly turning inactive.

LBM1-41460

Minor

Resolved an issue where a temporary event, such as a brief network glitch during a specific short window in the node power-up process, could prevent the node from completing power-up successfully.

LBM1-39951

Minor

Resolved an edge case where, during a rebuild, a failure of the Duroslight service to write to the journal device could cause the service to crash without generating a Journal SSD Failed event, resulting in only a NodeInactive event being recorded.

-40607

Minor

Resolved an issue where, in rare cases, a newly created volume could be assigned the same NSID as an existing volume. This condition could lead to incorrect delete or update operations for volumes sharing the same NSID.

LBM1-40068

Minor

Resolved an issue where a snapshot deleted while a node was inactive was not removed from the node after it recovered. This inconsistency could potentially cause rebuild or migration failures when the node later assumed the primary role.

LBM1-41162

Minor

Fixed a potential inaccuracy issue with logical counters when TRIM is enabled and a user issues a discard operation.

LBM1-39184

Minor

node-manager: Fixed cleanup logic in upsertEndpoint and deleteEndpoint to ensure that iptables rules are immediately updated when an admin-endpoint is created, updated, or deleted. Previously, old iptables rules remained active even after an admin-endpoint was deleted or modified, leaving ports unintentionally open until the next service restart. The fix ensures that rules are dynamically added, updated, or removed according to the current admin-endpoint configuration.

LBM1-40293

Minor

userlbe: Enabled graceful recovery even when some required cores or workers are unavailable, preventing fallback to abrupt recovery as long as at least one graceful recovery worker can be allocated.

LBM1-40871

Minor

node-manager: Fixed incorrectly-propagated exit status code on service graceful shutdown. Version 3.17.1 mistakenly introduced incorrect parsing of internal events, resulting in the service exiting with a bad status code even if its shutdown was graceful. It does not affect the node's lifecycle.

LBM1-42039

Minor

API: Fixed a typo in the RotationState enum, changing EncryptyingDEKs to EncryptingDEKs for cluster encryption rotation states. The original value is maintained for backward compatibility using allow_alias = true in protobuf, with the new, correct value as the canonical serialization.

LBM1-38329

Minor

Fix: A few alerts were raised multiple times - i.e.; for a six-node cluster, when one of the nodes entered state NodeRebuildNotPossible, six alerts would be fired instead of one.

LBM1-37059