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

RBD Mirror import bootstrap token infinitly loading. #14479

Open
TheCodingSheikh opened this issue Jul 22, 2024 · 4 comments
Open

RBD Mirror import bootstrap token infinitly loading. #14479

TheCodingSheikh opened this issue Jul 22, 2024 · 4 comments

Comments

@TheCodingSheikh
Copy link

TheCodingSheikh commented Jul 22, 2024

I'm trying to setup rbd mirror between two ceph clusters, each cluster in different k8s cluster, both ceph clusters have provider: host
tested connectivity between mons, they can reach each other
followed the documentation steps, the bootstrap token secret is not imported with rook, i tried with ceph ui and cli, it keeps loading infinitly, both clusters are in version 14.8.
no logs are appearing in the operator regarding importing the token

both mirror daemon and the mirror pool healths are OK

@travisn
Copy link
Member

travisn commented Jul 22, 2024

You're following this guide to setup the mirroring?

You might try the command kubectl rook-ceph dr health with the kubectl plugin to help troubleshoot.

@TheCodingSheikh
Copy link
Author

@travisn yes the guide you mentioned.
I'll check with the command and update.
Much appreciated

@TheCodingSheikh
Copy link
Author

TheCodingSheikh commented Jul 23, 2024

@travisn I tested the command, surprisingly it got the peer cluster information correctly, i decided to continue with the steps, i added the csi plugin and setup the VolumeReplicationClass and VolumeReplication

The VolumeReplication status is stuck at empty volume ID in request. It is in the same namespace as the pvc i want to mirror, the pvc has the storageclass with the mirrored pool.

Thanks a lot

Copy link

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.

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