From the log, the backup's name is backup-pv-filter-08898514opt-out, and the created namespace name is pv-filter-08898514-opt-out-1.
The E2E test assumes the namespaces that start with the backup's name are created by the backup, then they are deleted after the backup completes.
This E2E test case doesn't follow that rule.
If you are using velero v1.7.0+:
Please use velero debug --backup <backupname> --restore <restorename> to generate the support bundle, and attach to this issue, more options please refer to velero debug --help
If you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs deployment/velero -n velero
velero backup describe <backupname> or kubectl get backup/<backupname> -n velero -o yaml
velero backup logs <backupname>
velero restore describe <restorename> or kubectl get restore/<restorename> -n velero -o yaml
velero restore logs <restorename>
Anything else you would like to add:
Environment:
Velero version (use velero version):
Velero features (use velero client config get features):
Kubernetes version (use kubectl version):
Kubernetes installer & version:
Cloud provider or hardware configuration:
OS (e.g. from /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.
:+1: for "I would like to see this bug fixed as soon as possible"
:-1: for "There are more important bugs to focus on right now"
What steps did you take and what happened:
From the log, the backup's name is
backup-pv-filter-08898514opt-out, and the created namespace name ispv-filter-08898514-opt-out-1. The E2E test assumes the namespaces that start with the backup's name are created by the backup, then they are deleted after the backup completes. This E2E test case doesn't follow that rule.Those cases create namespaces by those lines. https://github.com/vmware-tanzu/velero/blob/f02613d2f7a7cfbf687f84d1deac7414d679569e/test/e2e/pv-backup/pv-backup-filter.go#L38-L40
Those namespaces are not deleted by default test case Destroy method. https://github.com/vmware-tanzu/velero/blob/f02613d2f7a7cfbf687f84d1deac7414d679569e/test/e2e/test/test.go#L128-L133
And those cases don't have their own specific Destroy method.
What did you expect to happen: Those namespaces should be deleted after test cases completed.
The following information will help us better understand what's going on:
The name mismatch between the backup and the created namespace happens here. https://github.com/vmware-tanzu/velero/blob/f02613d2f7a7cfbf687f84d1deac7414d679569e/test/e2e/pv-backup/pv-backup-filter.go#L33-L40 Align them should fix this issue.
If you are using velero v1.7.0+:
Please use
velero debug --backup <backupname> --restore <restorename>to generate the support bundle, and attach to this issue, more options please refer tovelero debug --helpIf you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs deployment/velero -n velerovelero backup describe <backupname>orkubectl get backup/<backupname> -n velero -o yamlvelero backup logs <backupname>velero restore describe <restorename>orkubectl get restore/<restorename> -n velero -o yamlvelero restore logs <restorename>Anything else you would like to add:
Environment:
velero version):velero client config get features):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.