-
Sub-task
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
4
-
False
-
-
False
-
ToDo
-
-
-
0
-
0.000
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
Description of problem:
While executing FileSystemBackup with Kopia, I noticed node agent pod has an additional logs related to "podvolumebackup starting" after it's being marked as completed.
I'm also seeing the same issue in OADP 1.2 and OADP 1.1 with FSB.
Upstream tracking issue:- https://github.com/vmware-tanzu/velero/issues/6781
Version-Release number of selected component (if applicable):
Installed velero from release-0.12 branch also tested it with OADP 1.2.2
How reproducible:
Always
Steps to Reproduce:
1. Create a File system backup
2. Verify the Node agent logs.
Actual results:
Node agent pod has an additional log "PodVolumeBackup starting" which is misleading.
time="2023-09-08T10:35:22Z" level=info msg="PodVolumeBackup completed" backup=openshift-adp/test-backup controller=podvolumebackup logSource="/remote-source/velero/app/pkg/controller/pod_volume_backup_controller.go:213" podvolumebackup=openshift-adp/test-backup-9bqkk time="2023-09-08T10:35:22Z" level=info msg="PodVolumeBackup starting" backup=openshift-adp/test-backup controller=podvolumebackup logSource="/remote-source/velero/app/pkg/controller/pod_volume_backup_controller.go:92" podvolumebackup=openshift-adp/test-backup-rj4d6 time="2023-09-08T10:35:22Z" level=info msg="PodVolumeBackup starting" backup=openshift-adp/test-backup controller=podvolumebackup logSource="/remote-source/velero/app/pkg/controller/pod_volume_backup_controller.go:92" podvolumebackup=openshift-adp/test-backup-9bqkk
Expected results:
Node agent pod shouldn't have PodVolumeStarting log after it's being completed.
Additional info:
