-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
oadp 1.4
-
None
-
Incidents & Support
-
3
-
False
-
-
False
-
ToDo
-
-
-
Moderate
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
None
Description of problem:
Second attempt of sending the deletion request of an expired backup fails because the tarball was already deleted in the first attempt.
Version-Release number of selected component (if applicable):
- OADP 1.4.7
- ARO 4.16.30
How reproducible:
All the time in customer cluster
Steps to Reproduce:
1. Azure blob storage in use.
2. Have backups configured with a ttl
3. garbageCollector request a deletion through deletion_controller
Actual results:
First attempt works and deletes cloud resources from storage, but backup CR is still in the cluster after 1 hour where the second attempt of the deletion request happens and fails because cannot download the tarball deleted in the first attempt.
Expected results:
Backup CR should be deleted in the first deletion request if all cloud storage were deleted and avoid having another attempt
Additional info: