Known Issues in Lightbits 3.15.3
ID | Description |
|---|---|
48532 | The node-manager service can fail to start if the number of drives present falls below the minimum required for the node's configured layout, for example, after a drive failure, power loss or planned maintenance. In earlier releases, the node started with the missing drive marked as failed; in affected releases it does not start at all. Workaround: Set |
48452 | The installer's etcd disk performance check does not work as intended; it can pass disks whose write IOPS are well below the required 10,000. Workaround: Before installation, verify the etcd disk's random-write performance manually (for example, with fio), and make sure it meets the 10,000 IOPS requirement. |
48435 | On some AMD EPYC servers, NVMe SSDs can report I/O timeouts. This can cause a storage node to be marked as failed, and while the node is out of service, volumes with reduced protection can become read-only. Workaround: Disable PCIe Relaxed Ordering in the server BIOS. |
48205 | When a large number of clone volumes are created from a small number of shared snapshots and a node is then restarted or replaced, some of those clone volumes can become stuck retrying volume creation, which can leave the node's protection groups unable to complete their rebuild. This issue is fixed in v3.20.2 and v3.21.1. |
47753 | Changing a node's Permanent Failure (PF) threshold can behave unexpectedly if the node is already Inactive. Lowering the threshold to a value that has not yet elapsed does not take effect until the original threshold time passes, and raising the threshold can prevent the node from reaching Permanent Failure at all. Workaround: Change a node's PF threshold before maintenance that will make it inactive. To shorten the threshold of a node that is already inactive, use a value that has already elapsed. |
47343 | In rare cases, deleting a snapshot while a rebuild is in progress can raise |
47300 | If the cluster manager's connection to the cluster's internal coordination service is interrupted (for example, due to a leader change, network disruption, or a brief service restart), the cluster manager's view of cluster servers can stop updating entirely, with no automatic recovery. Workaround: Restart the cluster-manager service to restore normal operation. |
44673 | In rare cases, performing a KEK rotation while simultaneously executing a high volume of volume/snapshot control plane operations could result in increased etcd contention. This affects only customers utilizing cluster-level encryption with the KEK rotation API. |
44435 | pmem_init and lbe executables are linked using staticx and therefore require /tmp to be mounted with the exec option enabled; otherwise, these executables will fail to run with "permission denied". |
44383 | When cluster-level encryption is enabled, deleting a server that hosts the active Cluster Manager (CM) could prevent subsequent server additions from completing successfully. After removing such a server from the cluster, stop the CM service on it or shut the server down. |
42991 | In a rare case, a network disconnect coinciding precisely with an NVMe SSD device state change could prevent subsequent state updates for that specific device, so changes to its health might not be reflected. The condition resolves automatically the next time the Node Manager service is restarted. |
41873 | Under a specific race condition, if a snapshot is created while a node is down and subsequently deleted during a very precise window in the node's startup sequence, the node may become unavailable. |
41466 | Creating a snapshot with a retention time greater than 192 years will fail and cause the API service to restart. |
41095 | The |
40883 | When using the vCenter Plugin (VCP) to upgrade a cluster to Lightbits 3.17.1 or later, the upgrade fails because VCP cannot parse the updated version format. To complete the upgrade, use the Lightbits core CLI or REST API directly. |
40068 | In rare cases, a newly-created volume could be assigned the same NSID as an existing volume. This condition can lead to incorrect delete or update operations for volumes sharing the same NSID. If this issue is encountered, contact Lightbits Support for a manual remediation procedure to identify and fix the affected volumes. |
38706 | In some rare cases, the frontend could hang during shutdown. |
37830 | In extremely rare cases, a node may not recover to an active state if an I/O error or bad block is encountered on an underlying SSD during its startup sequence. This prevents a key service (gftl) from initializing correctly and may require manual intervention (such as removing the failed SSD from the system) to allow the node to complete its recovery successfully. |
37505 | In a rare combination of events, the |
33865 | In certain cases when migrating volumes during dynamic rebalancing, a |
28027 | In specific circumstances, the server upgrade status may not reflect the correct state after a successful retry. This occurs in the following sequence: 1. A server is upgraded to version x.y.z. 2. The operation fails (for example, due to a timeout); however, the server binaries are successfully updated to version x.y.z. 3. The upgrade is retried to version x.y.z — this step is skipped internally, as the binaries are already up to date. 4. The upgrade status continues to show the previous failed operation, even though the retry completed without error. |
© 2026 Lightbits Labs™