Issues Fixed in Lightbits 3.18.3
ID | Description |
|---|---|
48538 | If the rebuild on the destination node of a protection group migration fails, for example, in a migration started by proactive rebalance after a node is added, the migration can remain stuck indefinitely. The migration task stays in the Running state, the protection group keeps an extra, unsynchronized replica, and the rebuild is not retried automatically, including after a cluster-manager restart. Affected versions: v3.18.2 through v3.21.1. Workaround: Contact Lightbits Support to restart the rebuild. Do not restart services on the destination node to recover, because this can cancel the migration and discard the rebuild progress. This issue is fixed in v3.22.1. |
48012 | In rare cases, a volume or snapshot that is created while a server's node-manager service is down (or the server is powered off), and deleted just as node-manager recovers, can remain on that server. If the leftover is a clone, or a snapshot of a clone, deleting the snapshot it was created from never completes: that snapshot stays in Deleting state and blocks new operations on its source volume. A leftover object can also prevent a rebuild from completing. Data is not lost, and affected volumes remain accessible and continue to serve I/O. Workaround: Contact Lightbits Support to remove the leftover volume or snapshot. This issue is fixed in v3.18.4 and v3.21.1. |
47343 | A race between rebuild with a snapshot deletion may result in DataIntegrityDuringRebuild events and a failure to rebuild the affected objects to the secondary (they will be marked as corrupted and have an incorrect CRC32C). The frontend log on the primary will show "Rebuild read detected a damaged object". |
46869 | If a snapshot is deleted while a rebuild is in progress, the rebuild can fail and display log errors similar to "Exceeded maximum number of 50 write attempts". The failed rebuild is not retried automatically, so the affected protection group remains degraded. Workaround: Contact Lightbits Support to restart the node instance on which the rebuild failed. This issue is fixed in v3.18.3, v3.20.2, and v3.21.1. |
45998 | VMWare customers may encounter unexpected cluster behavior if/when the client kernel decides to abort NVMe commands issued to the cluster. This can cause unexpected node state fluctuation (down, then back up). |
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. |
44334 | In affected versions, stopping or restarting the node-manager service on a server (for example, during maintenance or an upgrade) can leave the data-path service hung while it waits for a configuration update that never arrives, which delays or blocks the server's shutdown. This issue is fixed in v3.18.3 and v3.21.1. |
© 2026 Lightbits Labs™