-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pods in terminating loop on creation #20
Comments
Here's the relevant logs from the controller with debugging enabled
This one specifically looks similar:
|
These error reports are coming from the arbitrator node:
|
It looks like this was due to deleting the piraeus controllers before removing the pvs, so there were still drbd devices on the tiebreaker node as it was not rebooting. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We created a bunch of new pvcs at the same time (when setting the debug setting for piraeusdatastore/linstor-csi#172) and now the ha-controller is continuously evicting them due to lost quorum.
It seems that none of the nodes has been assigned to the volume on the linstor side as the primary:
This is causing the ha-controller to continuously delete the pods when they are re-created:
Could it be the same timeout affecting us with piraeusdatastore/linstor-csi#172 is causing none of the nodes to become primary?
The text was updated successfully, but these errors were encountered: