-
Notifications
You must be signed in to change notification settings - Fork 59
DRDB 9.2.15 is not compatible with Ubuntu 24.04 #240
Copy link
Copy link
Open
Description
Pods are not “Pending” in the scheduler sense; they are stuck in Init (or effectively blocked by it). The underlying failure is in the LINSTOR satellite pods.
Failure chain:
LINSTOR satellites stay in Init:0/3 because the first init container, drbd-module-loader, exits with code 1 (and then restarts and fails again).
No LINSTOR nodes are ever registered (linstor node list is empty).
CSI node and NFS server pods use an init container linstor-wait-node-online that polls the LINSTOR API for the node. They get 404 Not Found (node doesn’t exist) and never finish Init.
So: satellite init fails → no nodes in LINSTOR → CSI/NFS init never succeeds.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels