Bug 1813025
| Summary: | Migration fails due to restic time out when migrating 50 projects. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Migration Toolkit for Containers | Reporter: | Roshni <rpattath> | ||||||
| Component: | General | Assignee: | Dylan Murray <dymurray> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Xin jiang <xjiang> | ||||||
| Severity: | medium | Docs Contact: | Avital Pinnick <apinnick> | ||||||
| Priority: | unspecified | ||||||||
| Version: | 1.3.0 | CC: | chezhang, dymurray, ernelson, jmatthew, sregidor, whu, xjiang | ||||||
| Target Milestone: | --- | Keywords: | WorkItem | ||||||
| Target Release: | 1.4.z | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1831605 (view as bug list) | Environment: | |||||||
| Last Closed: | 2021-01-14 21:51:26 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Roshni
2020-03-12 18:25:23 UTC
This likely has nothing to do with migrating 50 namespaces, but more specifically that the restic restores were never acted upon properly. It would be helpful to get the output of `oc get podvolumerestores -n openshift-migration -o yaml` as this will tell us what exactly happened to the restic restores being run. The timeout generally means something went wrong with restic and Velero couldn't recover. Please paste this output if you still have this environment available. Created attachment 1673583 [details]
output of podvolumerestore
Attaching the output of
# oc get podvolumerestores -n openshift-migration -o yaml
*** Bug 1831605 has been marked as a duplicate of this bug. *** |