Skip to main content
Question

Restore to the new namespace fails

B

Hello,
We are testing functionalities of the Kasten K10 7.5.2 and Kasten fails to restore the app/namespace to the different one in the same cluster. Kasten reports the following:
 

Excerpt:

namespace"},"fields":[{"name":"AppNS","value":"project-passportsrestore"}],"file":"kasten.io/k10/kio/exec/phases/phase/restore_app.go:2902","function":"kasten.io/k10/kio/exec/phases/phase.transformToAppPVC","linenumber":2902,"message":"Failed
          moving PVC from K10 namespace to app
          namespace"},{"cause":{"cause":{"message":"persistentvolumeclaims
          \"redis-data-redis-1738916131-replicas-1\" already
          exists"},"file":"kasten.io/k10/kio/pvccloner/clone.go:92","function":"kasten.io/k10/kio/pvccloner.kubeCloner.Clone","linenumber":92,"message":"Failed
          to create cloned PVC in target


Almost every error line reprots:  “alread exists” as a cause. Which is sort of impossible considering restoration to a new namespace.

Complete restore log is attached.

Any ideas ?

 

1 Attachments

3 comments

Hagag
Forum|alt.badge.img+2
  • Hagag
  • Experienced User
  • 154 comments
  • February 20, 2025

Hi ​@branislav.mihajlovic 

Could you share the list of PVCs in the new namespace where you're attempting the restore?
i need to check the status of the PVCs inside this namespace.

Best regards,
Ahmed Hagag

B
1 person likes this
  • B
    branislav.mihajlovic
B

Hi ​@Hagag I used the restore option to “Add prefix/suffix to the tarhet name namespaces”, suffix in my case as the original name is “project-passports” I added suffix “restore” so the new namespace “project-passportsrestore” is new and totally empty.

B

​@Hagag 
Here is the list of PVCs of original and restored namespace, it if helps.

 

 

Comment


Terms & Conditions