Dmitry Mishin

There's no last line, I think it's getting killed before the line is flushed. And no, it has plenty of memory Although I think I saw some errors about getting...

Ok, I figured the problem. The controller is killed because the livenessProbe is failing, and it's failing because the health check returns "Services not running: SpaceTrackingService"

Another error now: ``` ERROR REPORT 64CBFA4E-00000-000024 ============================================================ Application: LINBIT�� LINSTOR Module: Controller Version: 1.23.0 Build ID: 28dbd33ced60d75a2a0562bf5e9bc6b800ae8361 Build time: 2023-05-23T06:27:14+00:00 Error time: 2023-08-03 19:20:48 Node: linstor-controller-58c7d99c94-9rqws Peer: RestClient(10.244.193.250; 'linstor-csi/v1.1.0-20969df70962927a06cbdf714e9ca8cc3912cb4d')...

Could I please get the image with first error fixed at least?

Still stuck and can't use the storage... Help please

> The fix for the first exception `Uncaught exception in k` was released with v1.24.0. Ah, I missed it. Thanks! > For the second exception, I'm still not sure how...

Here's the attempt to run 1.24: ``` run-migration time="2023-08-09T06:37:58Z" level=info msg="running k8s-await-election" version=refs/tags/v0.3.1 run-migration time="2023-08-09T06:37:58Z" level=info msg="no status endpoint specified, will not be created" run-migration I0809 06:37:58.920430 1 leaderelection.go:248] attempting...

> > Do you mean the kubernetes objects? All of them? > > As yamls? > > Sure, usually I do something like these two lines: > > ``` >...

I've sent the whole /var/log/linstor-controller folder to the email, is that good?

Some satellites are not available, it's a big cluster.. Are you saying that's the problem? Ok, trying with just a few satellites (if it will let me remove the rest...)