Bug 1822380 - PVC that is not attached to any pods can not be discovered for migration
Summary: PVC that is not attached to any pods can not be discovered for migration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Migration Tooling
Version: 4.3.z
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.4.z
Assignee: Scott Seago
QA Contact: Xin jiang
URL:
Whiteboard:
: 1763832 (view as bug list)
Depends On: 1831253
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-08 20:52 UTC by jooho lee
Modified: 2023-12-15 17:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1831253 (view as bug list)
Environment:
Last Closed: 2020-06-16 11:37:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:2570 0 None None None 2020-06-16 11:37:54 UTC

Description jooho lee 2020-04-08 20:52:48 UTC 
Description of problem:
Customer who wants to stop their application during migration to avoid desynchronization issue can not copy PVC for their application. CAM tool can not discover any PVC because the PVCs are not attached to any pods.

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


How reproducible:


Steps to Reproduce:
1. Change replica count to 0
2. Try to create migration plan
3. It does not discover PVC

Actual results:
Cam tool can not discover any PVC

Expected results:
All PVC have to be discovered 

Additional info:
Comment 2 John Matthews 2020-04-08 21:39:27 UTC 
See also https://bugzilla.redhat.com/show_bug.cgi?id=1763832
Comment 3 John Matthews 2020-04-08 21:40:15 UTC 
Related to: https://issues.redhat.com/browse/MIG-179
Comment 4 jooho lee 2020-04-09 13:14:26 UTC 
As I mentioned above, the PVC attached to the COMPLETED pod is also discovered even though the pod is not running anymore.

The COMPLETED pod is from cronjob so I think the conditions for discovering PVC are something vague.
Comment 5 John Matthews 2020-05-04 18:31:12 UTC 
*** Bug 1763832 has been marked as a duplicate of this bug. ***
Comment 6 Scott Seago 2020-05-14 14:38:45 UTC 
Fixed by https://github.com/konveyor/mig-controller/pull/485
Comment 9 Sergio 2020-06-09 09:28:36 UTC 
Verified using CAM 1.2.2 stage

    - name: MIG_CONTROLLER_REPO
      value: openshift-migration-controller-rhel8@sha256
    - name: MIG_CONTROLLER_TAG
      value: 3923f6000eaff8c5f02d778e1d7b93515a8bc23990d54f917c30a108f7a37b3a
    - name: MIG_UI_REPO
      value: openshift-migration-ui-rhel8@sha256
    - name: MIG_UI_TAG
      value: 6abfaea8ac04e3b5bbf9648a3479b420b4baec35201033471020c9cae1fe1e11
    - name: MIGRATION_REGISTRY_REPO
      value: openshift-migration-registry-rhel8@sha256
    - name: MIGRATION_REGISTRY_TAG
      value: ea6301a15277d448c8756881c7e2e712893ca8041c913476640f52da9e76cad9
    - name: VELERO_REPO
      value: openshift-migration-velero-rhel8@sha256
    - name: VELERO_TAG
      value: 1a33e327dd610f0eebaaeae5b3c9b4170ab5db572b01a170be35b9ce946c0281
    - name: VELERO_PLUGIN_REPO
      value: openshift-migration-plugin-rhel8@sha256
    - name: VELERO_PLUGIN_TAG
      value: 37d5167cbbeedcedaf6750d64ba992a75d3ae21f3d3df6c0c6eef6eb400dd076


After scaling the application to 0, the PVCs could be discovered by the UI, added to the migration and migrated properly.
Comment 11 errata-xmlrpc 2020-06-16 11:37:52 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:2570
Note You need to log in before you can comment on or make changes to this bug.