Known Issues in Lightbits 3.18.3

49019

In rare cases, after a node becomes active, the frontend service on this or another node could transiently fail a replication connection (with connection error: seastar::metrics::double_registration, automatically reestablished), thus leaving some stale stats under /mnt/stats. Subsequently, an access to the stats (manual or via lb_support) could cause a frontend segfault.

48930

In a rare situation where during a rebuild at least two snapshots are deleted, one containing data and a higher one containing a trim to the same blocks, the trim might be applied to the next existing version/snapshot - thus losing the valid data in it.

48605

In v3.18.3 and v3.20.1, upgrading a cluster with RPM packages from a release that ships etcd 3.5.18 (for example, v3.18.2 or v3.19.1) does not upgrade etcd. The cluster keeps running etcd 3.5.18 instead of the etcd 3.5.30 included in the release. To check a server, run "rpm -q etcd". This issue is fixed in v3.20.2 and v3.21.1; upgrading to a fixed version also upgrades etcd.

48546

When SSD Journaling is enabled and the journal devices are allocated from the same device pool as the data devices, the node-manager service can fail to start after a data drive is lost. No workaround is currently available.

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 initialDeviceCount in system-profile.yaml to a lower value. This issue is fixed in v3.18.4, v3.20.2 and v3.21.1.

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.

48041

In affected versions, when a management operation fails repeatedly, the delay between retries eventually drops to almost zero: after about 1.5 minutes of consecutive failures in v3.18.x, or about 16 hours in v3.19.x and v3.20.x. The continuous retries can keep a CPU core busy and flood the logs, pushing out older log entries needed to investigate the original failure. This issue is fixed in v3.18.4, v3.20.2, and v3.21.1.

47941

A snapshot creation can fail and report an "error" state if the same source volume had a management operation (such as an attach, detach, or another snapshot) interrupted shortly beforehand; for example, by a cluster-manager restart. The source volume is unaffected (no data loss) and stays available. Retrying the same request does not help; the failed snapshot should be deleted manually, and a new one should be created instead. If the new snapshot also fails, contact Lightbits Support.

47792

A volume can be reported as stuck in an "Updating" state indefinitely, even though the underlying operation actually completed successfully and the cluster is healthy. This can happen if the cluster-manager process restarts while a volume update (such as an attach or detach) is in progress; for example, during an upgrade, node failure, or other control-plane disruption. There is no data loss, and affected volumes continue to serve I/O. No customer-side workaround is available; contact Lightbits Support to recover an affected volume.

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.

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.

46209

The bundled Grafana Alloy log-streaming agent ships with Grafana's anonymous usage statistics reporting enabled by default. The report is sent out on a fixed four-hour schedule to https://stats.grafana.org/. In air-gapped or firewalled deployments, these attempts fail and produce recurring error entries in the journal. In connected deployments, they could represent an unsanctioned outbound connection to a third party. The exact list of fields collected is documented at https://grafana.com/docs/alloy/latest/data-collection/.

45912

If a storage node has some working and some stalled or failed replication connections to other nodes, clients may experience write I/O timeouts. Workaround: Restart the network services on the affected node. This issue is fixed in v3.21.1.

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.

45712

In rare cases, if the internal connection used to track volume or snapshot state changes is interrupted (for example, due to a leader change, network interruption, or a brief service restart), a volume or snapshot update can remain stuck showing as still in progress even though the underlying change has completed. Workaround: Restart node-manager on the affected server to resolve the stuck state.

45625

After running the Ansible node cleanup, leftover journaling RAID (mdadm) devices can keep drives attached, so the next installation detects fewer NVMe drives than expected. Workaround: Stop the mdadm RAID device manually before reinstalling. This issue is fixed in v3.21.1.

45202

When a volume is created with lbcli, any part of a label key before a hyphen is dropped. For example, --labels="pve-vmid=100" is saved with the key "vmid" instead of "pve-vmid". Workaround: Avoid hyphens in label keys, or create the volume through the REST API, which is not affected.

45157

During a node power-up after an abrupt shutdown, the node's reported power-up progress can reach 100%, drop back to 50-60%, and then climb to 100% again. This affects the reported percentage only. Recovery completes correctly, and the node returns to service only when it is actually done. No workaround is needed.

44464

In affected versions, if the server selected as the new primary for an in-progress volume migration becomes permanently failed, the migration does not abort and instead retries indefinitely, repeatedly updating the cluster state. This issue is fixed in v3.21.1.

44386

Grafana dashboards may display a short spike of negative BW/Throughput rate, following the stoppage of a Lightbits service.

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.