Title
Page icon
Create new category
Edit page index title
Edit category
Edit link
Known Issues in Lightbits 3.20.1
ID | Description |
|---|---|
46714 | In rare cases, after the etcd service on a server is stopped and restarted, the node on that server may remain inactive and not rejoin the cluster within the expected time. |
46108 | In rare cases, adding an NVMe device may fail when the add operation coincides with lightbox-exporter collecting NVMe error metrics for the same device. If this occurs, re-issue the add device command. |
45729 | When SSD journaling is configured with multiple NVMe devices, cluster cleanup does not remove the RAID (mdadm) arrays created by Lightbits. Before re-deploying on the same servers, manually remove these arrays using mdadm. |
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. |
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. |
37505 | In a rare combination of events, the physicalOwnedCapacity volume statistic may report an incorrect value when data at a specific LBA is overwritten with content that has a different compression ratio. This affects the reported statistic only; stored data and I/O are unaffected. |
© 2026 Lightbits Labs™