Skip to content
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

ceph rdb attached pod failover not happening when node goes down #5902

Closed
jobin-AT opened this issue Jul 27, 2020 · 3 comments
Closed

ceph rdb attached pod failover not happening when node goes down #5902

jobin-AT opened this issue Jul 27, 2020 · 3 comments

Comments

@jobin-AT
Copy link

Hello,

I have a kubernetes cluster installed and rook ceph deployed successfully.

When i try to create a pvc it works fine. I can see the pvc created also I mounted the storage to container successfully.

When my node goes down kubernetes is trying the recreate the pod on other node but its not happening due to storage side issue, please find the below error I am getting.

Warning FailedMount 66s kubelet, test-14.64.local Unable to attach or mount volumes: unmounted volumes=[mysql-persistent-storage], unattached volumes=[default-token-phmsf mysql-persistent-storage]: timed out waiting for the condition

i have installed the rook using the rook documentation, same steps i used

I am using the ceph Block Storage in rook

Anyone experiencing this problem?

Thanks!

@travisn
Copy link
Member

travisn commented Jul 27, 2020

@jobin-AT If the node is not responding, this is a general K8s issue, not specific to rook or ceph. You can read about the details in ceph/ceph-csi#578. If you know the node is gone, you can force delete the pod and K8s will free the volume to be mounted from another node. But if the node ever comes back online while the new pod is active, the volume could be corrupted so you must be careful with this option.

@stale
Copy link

stale bot commented Nov 1, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Nov 1, 2020
@github-actions
Copy link

This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants