Bug 1822425 - Migrating an empty PV causes problems.
Summary: Migrating an empty PV causes problems.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Migration Tooling
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.4.0
Assignee: Scott Seago
QA Contact: Xin jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-09 00:27 UTC by John Matthews
Modified: 2020-05-28 11:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-28 11:09:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:2326 0 None None None 2020-05-28 11:10:21 UTC

Description John Matthews 2020-04-09 00:27:23 UTC
We ran into an issue migrating 'Robot Shop', the redis DB had an empty PV.
The Migration attempted to proceed, got stuck for ~1 hour, then was marked successful.  Upon trying to use Robot Shop we weren't able to add anything to the 'cart'.

After investigation it was determined that the root cause was a bug in Velero working with empty PVs.


The below Velero PR is believed to fix the problem
https://github.com/vmware-tanzu/velero/pull/2390
"bug fix: save PodVolumeBackup manifests to object storage even if the volume was empty, so that on restore, the PV is dynamically reprovisioned if applicable"

Comment 1 Scott Seago 2020-04-21 16:28:56 UTC
PR for upstream fix, cherry-picked to our repo: https://github.com/konveyor/velero/pull/58

Comment 5 Sergio 2020-05-08 12:39:28 UTC
Verified using CAM 1.2 stage

A sample application (nginx) using an empty PVC was migrated with no problem.

Comment 7 errata-xmlrpc 2020-05-28 11:09:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:2326


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