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.

Sign up for GitHub

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

Jump to bottom

"Resource name may not be empty" error #10

Open
mpepping opened this issue Dec 12, 2024 · 1 comment
Open

"Resource name may not be empty" error #10

mpepping opened this issue Dec 12, 2024 · 1 comment

Comments

@mpepping
Copy link

Tested v0.1.3 and v0.1.2 but with both versions I get the following error on a Rancher v2.9.4 local cluster:

./cattle-drive migrate -s rke1cluster -t rke2cluster --kubeconfig local.yaml
initiating source [rke1cluster] and target [rke2cluster] clusters objects.. \exiting tool: resource name may not be empty

The migrate, interactive and status sub commands throw the same error. Is there a way to debug this?
@mpepping
Copy link
Author

Release v0.1.0 works OK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mpepping