"Completed" pod is not restored although is was backed up #6605
Labels
backlog
Needs investigation
Needs triage
We need discussion to understand problem and decide the priority
Describe the problem/challenge you have
We had an fixed issue #6182 which fixed a wrong backup result issue, so currently non-running pods existance won't effect the backup result, and this kind of pods will be backed up, but the pod was not restored, as we can see it was skipped accroding to velero log.
time="2023-08-04T07:34:58Z" level=info msg="default/test11-bhrhc is complete - skipping" logSource="pkg/restore/restore.go:1040" restore=velero/backup-job-1-20230804073455
Describe the solution you'd like
If there is no need for Job type of pod, then we can skip backing up them. or restore them.
Anything else you would like to add:
Environment:
velero version
):kubectl version
):/etc/os-release
):Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: