Satellite pods keep running after fatal error

LINBIT SDS Integrations
, ,
1

When running up a LinstorCluster and when the nodes do not have the drbd module, the pods start ok. Viewing the logs can see error (“modprobe: FATAL: Module drbd not found in directory”):

2026-08-19 09:35:32.217 [DeviceManager] INFO  LINSTOR/Satellite/749e1b SYSTEM - DeviceManager waiting for service-condition
2026-08-19 09:35:32.219 [DrbdEventService] WARN  LINSTOR/Satellite/a55be3 SYSTEM - DRBD 'events2' returned error: 
modprobe: FATAL: Module drbd not found in directory /lib/modules/5.14.0-570.131.1.el9_6.x86_64
2026-08-19 09:35:32.226 [Main] INFO  LINSTOR/Satellite/ff2b70 SYSTEM - NetComService started on port /0:0:0:0:0:0:0:0:3366

:
2026-08-19 09:35:31.924 [Main] INFO  LINSTOR/Satellite/ff2b70 SYSTEM - Checking support for CRYPT_SETUP: supported (2.7.5)
2026-08-19 09:35:31.931 [Main] INFO  LINSTOR/Satellite/ff2b70 SYSTEM - Checking support for LVM: supported (2.3.31)

The fact that it is hidden in the log and the pods keep running ie to success is unfortunate whereas a failing pod would be much more helpful IMO.

Thank you

2

Usually, the drbd-module-loader container should check that DRBD is loaded, and that the correct DRBD version is loaded. I’m wondering how it got past this stage.