Closed OrvilleQ closed 3 weeks ago
It looks like something went wrong when we switched our image builds in https://github.com/piraeusdatastore/piraeus/commit/547bb823f7b0b6e2cb4e3b899e89718abf009639
I've reverted the tags to point at the old manifests, so that should solve the immediate issue once you clean up the old images/reprovision.
Fixed by 4f1af0f293a99ac1efdcce0e2dfd76bc4fbe84c2
Hello there. I'm new to Piraeus and Linstor, and I was trying to install the Piraeus operator on an arm64 cluster I created on Hetzner (only 1 node for now) using Talos Linux, but it's not working.
I was using Talos Linux v1.8.0 with Kubernetes v1.31.1. First, I deployed the operator using Kustomize with no issues at all.
Then I deployed a
LinstorSatelliteConfiguration
copied from this document, without change.Finally I deployed a "blank"
LinstorCluster
yaml following the get started tutorial.Things started to get strange from here. The
linstor-satellite
kept going into an Error state and enteredCrashLoopBackOff
, while thelinstor-controller
had already enteredCrashLoopBackOff
during the Init phase.I tried to check the logs of
linstor-satellite
.After [searching](https://github.com/search?q=org%3ALINBIT%20execve()&type=code), ~it seems like this
execve()
is something relate to systemd? which should be all disabled with theLinstorSatelliteConfiguration
I applied.~I'm not sure what's happening with the linstor cluster or where should I start to debug with this mess. Please help me with this issue.
Thank you.