Title
Create new category
Edit page index title
Edit category
Edit link
Release 3.15.3
Release Date
v3.15.3 was released to the public on March 19, 2026.
New in This Release
This release introduces the following changes since version 3.14.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 |
|---|---|---|
Enhancement | AMD dual socket support - all previous AMD dual socket support-related limitations have been lifted in this release. | LBM1-43382 |
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 | Enabled encrypted clones from unencrypted base snapshots, allowing derived volumes to use unique keys. Supported on clusters configured with encryption. | LBM1-42408 |
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 rare 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 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 | Fixed an issue where a volume rebuild may fail to complete following an internal error in the handling of create new snapshot. When a very specific portion of the handling of a create snapshot task occurs exactly as the cluster manager service is switched over, this volume and other volumes that share the same protection group may get into an inconsistent state that will prevent the completion of a volume rebuild. | LBM1-40208 |
Major |
| LBM1-41460 |
Minor |
| LBM1-42614 |
Minor | Fixed an issue when cluster encryption is enabled, KEK is rotated, and the cluster manager service is switched over - that could lead to a failure to process new API calls, and actively react to changes in the cluster. If the cluster manager fail-over sequence coincides exactly with a very specific time window in the KEK rotation process, the cluster manager service may fail to start again, preventing successful handling of new API requests or changes of state in cluster. | LBM1-42309 |
Minor | Fixed an issue where a volume protection state might be reported incorrectly in the API as fully protected instead of degraded or read only, following a permanent failure re-balance that fails. | LBM1-42282 |
Minor | Resolved an issue where a snapshot deleted while a node was inactive and 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 |
| LBM1-40243 |
Minor |
| LBM1-40871 |
Installation and Upgradeability
You can upgrade to this release from all previous Lightbits 3.12.x, 3.13.x, and 3.14.x releases.
© 2026 Lightbits Labs™