Bug 1929832 - If a backup custom resource references a deleted backup snapshot location, an insignificant error message appears in the logs.
Summary: If a backup custom resource references a deleted backup snapshot location, an...
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Documentation
Version: 1.4.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 1.5.0
Assignee: Avital Pinnick
QA Contact: Xin jiang
Avital Pinnick
Depends On:
Blocks: 1956738
TreeView+ depends on / blocked
Reported: 2021-02-17 18:25 UTC by Erik Nelson
Modified: 2021-06-10 10:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1956738 (view as bug list)
Last Closed: 2021-06-10 10:22:35 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Erik Nelson 2021-02-17 18:25:00 UTC
Description of problem:
If a migration is performed and Backups are created that reference a BSL, and then that BSL is deleted and/or replaced by a new one, but the backups remain on the cluster (or are synced from the same s3 bucket), you will often see the following error in the logs as velero attempts to reconcile said Backup:

"Error checking repository for stale locks"... "error getting backup storage location: backupstoragelocation.velero.io \"my-bsl\" not found".

Often users may be troubleshooting a failed migration and will latch onto this error in the logs, because on the surface it appears to be significant, when actually it's a red herring and there is likely a different root problem at play.

We'd like to get this documented in the troubleshooting tips of the best practices, as we've often has this brought to us as a question.

Version-Release number of selected component (if applicable):

Comment 3 Avital Pinnick 2021-06-10 10:22:35 UTC
Changes merged.

Note You need to log in before you can comment on or make changes to this bug.