Bug 2233868 - PodVolumeRestore remain In Progress keeping the migration stuck at Stage Restore
Summary: PodVolumeRestore remain In Progress keeping the migration stuck at Stage Restore
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: General
Version: 1.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 1.8.0
Assignee: Dylan Murray
QA Contact: ssingla
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-23 15:24 UTC by ssingla
Modified: 2023-10-05 01:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-10-05 01:04:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2023:5447 0 None None None 2023-10-05 01:04:28 UTC

Description ssingla 2023-08-23 15:24:29 UTC
Description of problem:
On performing any indirect migration, the migration stucks at the Stage Restore step, waiting for the podvolumerestore to be completed.

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

How reproducible:
Always

Steps to Reproduce:
1. Deploy django or any stateful app on source cluster
2. Create a migplan to migrate the app using Indirect migration.
3. Now Execute the Cutover migration.

Actual results:
Migration stucks at Stage restore

Expected results:
Migration should finish successfully.

Additional info:





Describe PVR:

 oc describe podvolumerestore --namespace openshift-migration migration-74839-stage-l6kmp-9wglr
Name:         migration-74839-stage-l6kmp-9wglr
Namespace:    openshift-migration
Labels:       velero.io/pod-uid=003f373e-fd45-4c0f-9e89-42c04951757b
              velero.io/pvc-uid=6eab6b4f-bcf6-4808-a6b3-5eb1cca503f7
              velero.io/restore-name=migration-74839-stage-l6kmp
              velero.io/restore-uid=1d72a1fe-4e63-48c0-b52e-2a9ee492447e
Annotations:  <none>
API Version:  velero.io/v1
Kind:         PodVolumeRestore
Metadata:
  Creation Timestamp:  2023-08-23T14:21:45Z
  Generate Name:       migration-74839-stage-l6kmp-
  Generation:          1
  Managed Fields:
    API Version:  velero.io/v1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:generateName:
        f:labels:
          .:
          f:velero.io/pod-uid:
          f:velero.io/pvc-uid:
          f:velero.io/restore-name:
          f:velero.io/restore-uid:
        f:ownerReferences:
          .:
          k:{"uid":"1d72a1fe-4e63-48c0-b52e-2a9ee492447e"}:
      f:spec:
        .:
        f:backupStorageLocation:
        f:pod:
          .:
          f:kind:
          f:name:
          f:namespace:
          f:uid:
        f:repoIdentifier:
        f:snapshotID:
        f:sourceNamespace:
        f:uploaderType:
        f:volume:
      f:status:
        .:
        f:progress:
    Manager:    velero-server
    Operation:  Update
    Time:       2023-08-23T14:21:45Z
  Owner References:
    API Version:     velero.io/v1
    Controller:      true
    Kind:            Restore
    Name:            migration-74839-stage-l6kmp
    UID:             1d72a1fe-4e63-48c0-b52e-2a9ee492447e
  Resource Version:  111241
  UID:               659bf151-abec-45c6-9702-ae3f27b5229a
Spec:
  Backup Storage Location:  automatic-9dv7b
  Pod:
    Kind:            Pod
    Name:            stage-postgresql-5hq9x
    Namespace:       ocp-24730-django
    UID:             003f373e-fd45-4c0f-9e89-42c04951757b
  Repo Identifier:   s3:s3-us-east-2.amazonaws.com/camreplication/velero/restic/ocp-24730-django
  Snapshot ID:       201c1e6b
  Source Namespace:  ocp-24730-django
  Uploader Type:     restic
  Volume:            postgresql-data
Status:
  Progress:
Events:  <none>

Comment 7 errata-xmlrpc 2023-10-05 01:04:10 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 (Important: Migration Toolkit for Containers (MTC) 1.8.0 security and bug fix update), 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/RHSA-2023:5447


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