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

Cluster Migration with Data Movement #8270

Open
raynay-r opened this issue Oct 6, 2024 Discussed in #8194 · 4 comments
Open

Cluster Migration with Data Movement #8270

raynay-r opened this issue Oct 6, 2024 Discussed in #8194 · 4 comments
Labels
area/datamover Needs info Waiting for information

Comments

@raynay-r
Copy link

raynay-r commented Oct 6, 2024

Discussed in #8194

Originally posted by raynay-r September 8, 2024
Hi!

I have two OKD cluster and want to migrate an application between them. Both clusters run rook-ceph with the same storage classes. I am using an additional Minio instance as backup storage. Both OKD cluster have access to the Minio instance.

I was able to successfully migrate the application using the file system backup, but I am not able to get it working with data movement. The backup itself works without issue but when I try to restore in the second cluster I get the following error

Errors:
  Velero:     <none>
  Cluster:    <none>
  Namespaces:
    projects-xwiki-restore:  error preparing persistentvolumeclaims/projects-xwiki-restore/data-xwiki-mysql-0: rpc error: code = Unknown desc = fail get DataUploadResult for restore: xwiki-restore-23: no DataUpload result cm found with labels velero.io/pvc-namespa
ce-name=projects-xwiki.data-xwiki-mysql-0,velero.io/restore-uid=f7c9dc29-e46e-4b9f-b67c-46564c16c0d9,velero.io/resource-usage=DataUpload

Should Data Movement between clusters work?


Opening an issue from a discussion, because I got no further answers in the discussions section and I was told that this should work. Please take a look at the linked discussion for detailed description and log output.

Would be great if you could help me out here.

Thanks!

@Lyndon-Li
Copy link
Contributor

Could you share velero log bundle by running velero debug?

@raynay-r
Copy link
Author

Sure. Here are the bundles from the source and target cluster:

bundle-source-cluster.tar.gz
bundle-target-cluster.tar.gz

@ywk253100
Copy link
Contributor

ywk253100 commented Oct 14, 2024

The restore forgejo-restore-1 in the debug bundle was created in 2024-09-14, but the log started from 2024-10-03, cannot find any useful information related to the failed restore.
Could you create a new restore and collect the debug bundle again?

@ywk253100 ywk253100 self-assigned this Oct 14, 2024
@reasonerjt reasonerjt assigned reasonerjt and unassigned ywk253100 and reasonerjt Oct 14, 2024
@ywk253100 ywk253100 added the Needs info Waiting for information label Oct 14, 2024
@raynay-r
Copy link
Author

I created a new backup with the name "forgejo-backup-10" on the source cluster and a restore with the name "forgejo-restore-11" on the target cluster an could reproduce the same error again. Here are the bundles:
bundle-target-cluster.tar.gz
bundle-source-cluster.tar.gz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/datamover Needs info Waiting for information
Projects
None yet
Development

No branches or pull requests

4 participants