Release 3.16.1
Release Date
v3.16.1 was released to the public on July 15, 2025.
New in This Release
This release introduces the following changes since version 3.15.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 support for Lightbits servers to accept NVMe connections over multiple networks. This feature is currently available only for single server deployments. A new Ansible flag, listen_on_all_interfaces, has been introduced. When set to true, duroslight will listen for incoming connections on all available network interfaces, instead of being restricted to a single interface. | LBM1-37795 | |
| Added support for single-server Lightbits deployment. For more information, see the relevant documentation. Note: Upgrading a single-server deployment is only supported via the upgrade server command, not upgrade cluster. | LBM1-37794 | |
| Added support for volume renaming. For more details, please refer to the relevant documentation (lbcli update volume) . | LBM1-36811 | |
| Enhanced the NVMe deallocate implementation to improve capacity utilization. This enhancement integrates with the file system’s TRIM command, enabling the operating system to identify and release unused data blocks. Refer to the Lightbits TRIM documentation for more on how to enable this capability (Lightbits TRIM Support). | LBM1-38231 | |
cluster-manager: Implemented different timeouts for operations based on TPM involvement. Operations using a TPM now have longer timeouts due to slower hardware responses, while non-TPM operations use shorter timeouts to allow faster failure handling. | LBM1-36337 | |
dms: Release of version 1.3 includes new configuration options and various fixes. See the DMS documentation for full details (DMS Overview). | LBM1-37685 | |
installation: Renamed the installation flag from enable_iptable to ipacl_explicit_allow. When IPACL is enabled, Lightbits no longer blocks all ports or override user configurations. Instead, Lightbits applies explicit DROP rules only for NVMe and Discovery Service ports. | LBM1-37088 | |
los-csi: Added support for K8s version v1.33.1. | LBM1-36894 | |
node-manager: Improved the logic for opening the discovery-service port when iptables are enabled. Previously, a node without any volumes placed on it would not open its discovery-service port, causing all client connections to target only nodes with volumes. With this change, every node will open its discovery-service port as long as there are volumes in the cluster. | LBM1-37090 | |
discovery-client: Resolved a potential deadlock during initial NVMe connection setup occurring before KATO arming. Additionally, ensured that any pending receive syscalls are canceled when KATO fires. | LBM1-37388 | |
duroslight: Added a sanity check for rebuild/data recovery object data size. This allows older primary software sending illegal objects to persist them without triggering assertion failures. | LBM1-38330 | |
duroslight: Added a sanity check on objects read from the primary to ensure rebuild read response data sizes comply with the replication protocol, even if the original object is malformed. This prevents link failures caused by sendmsg: Bad Address errors on Alma9 kernels. | LBM1-37887 | |
duroslight: This change ensures that the primary adheres to protocol assumptions when passing objects, and that the secondary sanity checks received objects - detecting and correcting any violations so malformed objects can still be safely persisted. Previously, when a primary read an object requested by a secondary rebuild, it might have detected corruption (e.g., decompression failure, CRC mismatch). However, if dek_generation is corrupted (non-zero), the primary may miss the issue and treat the object as encrypted, passing it as is. The secondary then assumes that the object is valid and writable, which can cause problems if the object is malformed. | LBM1-37650 | |
ansible: The installer will no longer update system packages to the latest version, to avoid unexpected changes. | LBM1-37738 | |
api-service: Fixed an issue in the 'list connected-hosts' command, where the IPACL was ignored when using a volume UUID filter, resulting in hosts being listed even if they were not actually connected to the volume. | LBM1-37852 | |
api-service: Fixed an issue where - following a restart - the api-service could return a snapshot with all statistics set to zero. | LBM1-37725 | |
api-service: Fixed an issue where - following an api-service restart - there was a brief window during which some nodes and servers might have been missed, potentially resulting in a partial list of nodes and/or servers being returned. | LBM1-36980 | |
api-service: Fixed an issue where no hosts were listed as connected when iptables was disabled and the volume's IPACL was empty. | LBM1-37834 | |
api-service: Fixed the volume connected-hosts API to display only hosts that are actually connected to the specified volume. | LBM1-37789 | |
cluster-manager: The TLS configuration for internal cluster communication now enforces a predefined list of allowed ciphers. | LBM1-37337 | |
data-layer: Fixed a bug that caused the events manager to stop and return stale events after encountering unexpected or deleted events like EnableServerEncryptionFailed(from versions 3.12 and 3.13). | LBM1-38043 | |
discovery-client: Default configuration no longer pins CPU affinity to core 0. | LBM1-37901 | |
los-csi: Resolved an issue affecting pods with securityGroupby configuring the fstypefield as ext4 in the CSI StorageClassexample. | LBM1-20579 |
Installation and Upgradeability
You can upgrade to this release from all previous Lightbits 3.13.x, 3.14.x, and 3.15.x releases.
Was this page helpful?