Bug 2090595
Summary: | [MTC] Migrations fails because of backup not found | ||
---|---|---|---|
Product: | Migration Toolkit for Containers | Reporter: | Prasad Joshi <prajoshi> |
Component: | Velero | Assignee: | Jason Montleon <jmontleo> |
Status: | CLOSED WONTFIX | QA Contact: | ssingla |
Severity: | low | Docs Contact: | Richard Hoch <rhoch> |
Priority: | low | ||
Version: | 1.6.5 | CC: | ernelson |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-07-01 15:42:21 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Prasad Joshi
2022-05-26 05:44:10 UTC
We are able to reproduce this bug reliably, when backup location has too many backup resources in that case it's happening. In our case s3 bucket had a 500+ backups. QE's reproducer works something like this: - set up two new clusters - use an existing (GCP in this case) bucket with 700+ backups on it - run a small/quick migration, which causes the BSL to be set up for the first time - the backup finishes before all the backups are sync'd from the bucket, and migration-controller cannot find the new one. - if you rerun after everything is sync'd it seems to work Currently it's not clear to us why the backup that is created locally apparently cannot be found until the backup sync is complete. A customer reproducer could happen in a scenario where: - they perform many migrations from source cluster 1 to destination cluster 1. - Moving on they start migrations from source cluster 2 to the same or another destination cluster reusing the same bucket. - If the sync of backups takes longer than the first migration it's likely they'll encounter this. One possibility is that we ignore the not found error and continue polling. Eventually the backup should be returned. It does open us up to the possibility to hanging if the backup is somehow really missing, but we can't think of a situation that would occur at present. We'll be deprecating 1.6/1.5 shortly, please open distinct bug against 1.7 if this continues to be seen. |