+++ This bug was initially created as a clone of Bug #1854908 +++ Description of problem: Sometimes a migration may fail as the stage pods are created and stay in Pending as they are unable to mount a PVC due to it being stuck in a Terminating state. To recreate: 1) Create a Pod that mounts a PVC 2) Create a MigPlan that references the Pod and PVC 3) Delete the PVC while it is mounted to the Pod, PVC will be in terminating 4) Run a migration with the MigPlan --- Additional comment from John Matthews on 2020-07-08 12:37:08 UTC --- Fixed via https://github.com/konveyor/mig-controller/pull/583
Already fixed: https://github.com/konveyor/mig-controller/pull/583
Verified in CAM 1.2.4 stage Source cluster: 3.11 aws Target cluster: 4.4 aws Replication repository: aws s3 PVC storageclass: gp2 Image: openshift-migration-rhel7-operator@sha256:540ece2453575615cf1447d1b6faeca312d363a56de966a4c29f6a0c24d66f2b 1. Deploy application 2. Create migration plan 3. Remove pvc 4. Execute migration plan The result is that, as expected, the execution failed with this error: status: conditions: - category: Advisory durable: true lastTransitionTime: "2020-07-22T11:56:08Z" message: '[1] Stage pods created.' status: "True" type: StagePodsCreated - category: Advisory durable: true lastTransitionTime: "2020-07-22T11:56:49Z" message: 'The migration has failed. See: Errors.' reason: StagePodsCreated status: "True" type: Failed errors: - 'PVC: ocp32834/mysql, deleted.' itenerary: Failed
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 (Cluster Application Migration (CAM) Tool 1.2.4 Operator Metadata Image 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/RHBA-2020:3321