search

kubevirt / kubevirt-velero-plugin

Plugin to Velero which automates backing up and restoring KubeVirt/CDI objects
Apache License 2.0
26 stars 26 forks source link

Please reopen issue 117 #213

Open 27149chen opened 5 months ago

27149chen commented 5 months ago

Please reopen issue #117, thanks

ShellyKa13 commented 2 months ago

Hi @27149chen I saw your comment in #117 : https://github.com/kubevirt/kubevirt-velero-plugin/issues/117#issuecomment-1918529629 What you describe is definitely not the same issue as in issue 117. So can you please edit this issue with a full description of the problem, how to reproduce, yamls, etc.. thanks!

27149chen commented 2 months ago

@ShellyKa13 it is the same, and the solution is removing field dataSource and dataSourceRef before restoring the pvc, since the dataSource do not exist in new cluster

ShellyKa13 commented 2 months ago

@27149chen your data source in this case is using pvc populators volumeimportsource as source, which is not what happens in the other issue. I want to know how to reproduce this since its not the same.

27149chen commented 2 months ago

yes, the original pvc is created by a dataVolume, which will set the dataSource in pvc spec as a volumeimportsource. But the volumeimportsource is a temp object which will be deleted when population is done. When backup and restore this pvc to a new cluster, It will get stuck while waiting for the dataSource, and the solution is removing field dataSource and dataSourceRef

ShellyKa13 commented 2 months ago

We have tests that have pvc that were populated this way and they work fine. Thats why I want you to describe exactly your scenario and how to reproduce please. Providing yamls and steps to reproduce.