Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1822425

Summary:	Migrating an empty PV causes problems.
Product:	OpenShift Container Platform	Reporter:	John Matthews <jmatthew>
Component:	Migration Tooling	Assignee:	Scott Seago <sseago>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	dwhatley, dymurray, jmatthew, mberube, pvauter, sregidor
Target Milestone:	---
Target Release:	4.4.0
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:	2020-05-28 11:09:56 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 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