-
Notifications
You must be signed in to change notification settings - Fork 115
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
etcd datastore migration doesn't succeed #375
Comments
👋🏻 may I ask you how do you change the DataStore reference? Since Cluster API is mentioned here, I take for granted you're doing that by editing the |
|
As I suggested in another comment, when May I ask you to try to replicate the unsuccessful migration this time by editing the |
ah ok, yes , sorry I forgot that |
No problem at all, mate! 🤗 Give it a try, and if it works, please, feel free to close the issue! |
nevermind, it works as soon as you do it the right way, I'll close this |
I was thinking of a safe trigger to prevent direct changes to the What we need, maybe, is just to make it more clear that once a |
Hi
We started a migration of a newly created cluster from one newly ceated kamaji-etcd datastore to another one.
(We did this to test the fix for issue #350, which seems to be not an issue anymore.)
The migration pod is created and completes and the TCP gets patched into "Migrating":
Logs of the Job:
The problem is: The migration never comes to an end, although the job completed.
And if you have a look at the pods of the TCP, they still point to the old datastore.
Logs of kamaji:
Versions:
The text was updated successfully, but these errors were encountered: