Search
Lightbits Release Notes
Lightbits Known Issues
Title
Message
Create new category
What is the title of your new category?
Edit page index title
What is the title of the page index?
Edit category
What is the new title of your category?
Edit link
What is the new title and URL of your link?
Release 3.18.1
Copy Markdown
Open in ChatGPT
Open in Claude
Release Date
v3.18.1 was released to the public on February 18, 2026.
New in This Release
This release introduces the following changes since version 3.17.x. A change is classified as either a new feature, an enhancement, a major issue (e.g., an issue that could lead to potential data loss or service loss), or a minor issue.
| Issue Type | Description | ID |
|---|---|---|
| Added a new field exposing via get/list volume response (available only in json/yaml format in lbcli) the protection group identifier (pgUUID) of this volume. | LBM1-40409 | |
| Added os-brick configuration to check discovery-client health in a custom network (not just localhost). | LBM1-42202 | |
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 | |
| 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 | |
| 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 | |
duroslight: Improved resiliency against data corruption by adding sanity LBA to the object header to help detect cases where (due to some bug), the backend returns the wrong LBA. | LBM1-40379 | |
duroslight: Improved resiliency against data integrity issues by adding checksum to headers of the blocks written to storage. | LBM1-38653 | |
| Fixed for Ansible chrony role to skip configuration if the service is already configured. | LBM1-22143 | |
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 | |
| Grafana: Added journal SSD latency and bandwidth plots to the server performance dashboard. | LBM1-36841 | |
| 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 | |
| Removed excess log messages from the exporter log file. | LBM1-36159 | |
| The fix clears the RPMs from the target directory before copying them back in the offline installation flow. | LBM1-32399 | |
| Updated the default values of automatically generated keys from none (-m0) to SHA512 (-m3). | LBM1-42334 | |
| 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 | |
| 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 | |
| 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 | |
| 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. A permanent fix for this issue is in development and will be included in an upcoming release. | LBM1-40626 | |
node-manager & etcd: Reduced Etcd's leader election-timeout for new installations. In some very rare cases, if the Etcd leader suffers from slowness, for example due to a malformed disk, the slowness could be great enough for lightbits-nodes to miss heartbeats and eventually turn themselves inactive. It would not be slow enough for the Etcd followers to initiate a new election, and replace the slow leader (which would have prevented any ligthbits-node from becoming inactive). By reducing the Etcd leader election-timeout, we make sure that such elections will take place in time, before any lightbits-node will turn inactive. | LBM1-41460 | |
| Fixed an issue where a temporary issue (such as a network glitch) might prevent the Lightbits node from powering up correctly. | LBM1-39951 | |
| Fixed a bug that occurs when a journaling SSD device fails just as a rebuild is starting. | LBM1-40607 | |
| Fixed issues that might lead to reuse of an existing NSID. | LBM1-40068 | |
| Fixed snapshot deletion while a node is inactive: the snapshot was not deleted in the node GFTL after it recovered, potentially causing a rebuild/migration failure with this node in the primary role (as the node has volume versions that other nodes do not). | LBM1-41162 | |
| Fixed a potential inaccuracy issue with logical counters when TRIM is enabled and a user issues a discard operation. | LBM1-39184 | |
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 | |
userlbe: Allowed graceful recovery even when missing required cores/workers, without falling back to abrupt recovery - as long as we succeed to allocate at least one graceful recovery worker. | LBM1-40871 |
Installation and Upgradeability
You can upgrade to this release from all previous Lightbits 3.15.x, 3.16.x, and 3.17.x releases.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Last updated on
Was this page helpful?
Next to read:
Release 3.17.1© 2026 Lightbits Labs™
Discard Changes
Do you want to discard your current changes and overwrite with the template?
Archive Synced Block
Message
Create new Template
What is this template's title?
Delete Template
Message