Known Issues in Lightbits 3.18.3

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 may 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

Some clients may temporarily lose connection to volumes on a storage node and experience I/O timeouts until network services on that node are restarted.

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.

45625

After running the ansible cleanup script, stale RAID devices may keep drives attached, causing the next install to detect fewer NVMe drives than expected. Workaround: Stop the mdadm RAID device manually before reinstalling.

45202

lbcli drops part of a label key that contains a hyphen. When creating a volume, if a label key contains a hyphen (-), lbcli incorrectly drops everything before the hyphen. For example: lbcli create volume ... --labels="pve-vmid=100" is saved as vmid=100 instead of pve-vmid=100. Workaround: Avoid hyphens in label keys, or create the volume via the REST API, which is not affected.

45157

During a node power-up after an abrupt shutdown, a node's reported power-up progress may reach 100%, drop back to 50-60%, and then climb to 100% again, because the last of three internal recovery phases is not included in the calculation. This affects the reported percentage only. Recovery completes correctly and the node returns to service only when it is actually done.

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.