Bug 1956738 - [Doc]: if a BSL is deleted but an older backup references, going to see error noise in the logs
Summary: [Doc]: if a BSL is deleted but an older backup references, going to see error...
Keywords:
Status: ON_QA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Documentation
Version: 1.4.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: 1.5.0
Assignee: Avital Pinnick
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On: 1929832
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 10:33 UTC by Avital Pinnick
Modified: 2021-05-13 11:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1929832
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Avital Pinnick 2021-05-04 10:33:28 UTC
Bug cloned for downstream docs.

+++ This bug was initially created as a clone of Bug #1929832 +++

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):
1.4.0


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