-
Notifications
You must be signed in to change notification settings - Fork 61
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
Pod no longer able to mount persistent volume #459
Comments
Something has kept the resource open on You may try |
Thanks for the quick reply @WanzenBug! I ran the command you suggested. It returned no errors and caused the volume on node eu-central-68d6 to be promoted to primary automatically. See:
If this should ever happen again I now know how to solve it, but this should have been resolved by the controller right? Are there any other logs which I could check to see what might have caused this? |
That So I suspect some manual inspection took place. Only other possibilty I could think of is LINSTOR itself timed out during resource creation, but somehow the resource was still usable. I'd take a look at the kernel logs for 1771, grep for |
I ran initially ran the Here are the results for that pvc. All these logs are from the moment I ran the command it seems.
|
You might want to check older logs ( |
Ah you're right. Found the relevant logs in kern.log.3
|
We are running a Strimzi Kafka cluster using Pireaus as the storage layer. Since a fews days (not sure how long), one of the kafka pods is no longer able to mount its persistent volume. The operator is now stuck in a loop recreating the pod every 10 min.
Events from the pod:
Not sure how to move forward here. I've found a similar error message in #424, but don't believe it's the same issue.
I've generated an SOS report in the current state: sos-report.tar.gz
The text was updated successfully, but these errors were encountered: