Bug 2039852 - "migration-controller" pod goes into "CrashLoopBackOff" state if "MigPlan" CR contains an invalid "destMigClusterRef" or "srcMigClusterRef"
Summary: "migration-controller" pod goes into "CrashLoopBackOff" state if "MigPlan" CR...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Controller
Version: 1.6.3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 1.6.3
Assignee: Pranav Gaikwad
QA Contact: Xin jiang
Steve Goodman
URL:
Whiteboard:
Depends On:
Blocks: 2039864
TreeView+ depends on / blocked
 
Reported: 2022-01-12 14:41 UTC by Prasad Joshi
Modified: 2022-01-20 06:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2039864 (view as bug list)
Environment:
Last Closed: 2022-01-20 06:31:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor mig-controller pull 1251 0 None open Bug 2039852: Fix nil pointer when wrong MigCluster is provided in the plan 2022-01-12 14:51:20 UTC
Github konveyor mig-controller pull 1252 0 None open Bug 2039852: fix nil pointer when wrong cluster is provided in migplan (#1251) 2022-01-12 15:02:12 UTC
Red Hat Product Errata RHSA-2022:0202 0 None None None 2022-01-20 06:31:47 UTC

Description Prasad Joshi 2022-01-12 14:41:11 UTC 
Description of problem: Migrationcontroller pod going in  "CrashLoopBackOff" state when migplan is pointing to an invalid destMigClusterRef/srcMigClusterRef. 


Version-Release number of selected component (if applicable):
MTC 1.6.3
SOURCE CLUSTER: AWS 4.6 MTC 1.6.3
TARGET CLUSTER: AWS 4.9 MTC 1.6.3



How reproducible:
Always


Steps to Reproduce:
1. Create a migplan which pointing to a invalid destMigClusterRef/srcMigClusterRef
For eg.
oc get migplan test3 -n openshift-migration -o yaml
  srcMigClusterRef:
    name: foo
    namespace: openshift-migration


Actual results: Migrationcontroller pod going in "CrashLoopBackOff"


Expected results: Migplan should display critical warning in conditions and status should be not Ready


Additional info:

$ oc get pods -n openshift-migration
NAME                                    READY   STATUS             RESTARTS   AGE
migration-controller-c444f7d67-2zxdj    1/2     CrashLoopBackOff   10         80m
Comment 7 errata-xmlrpc 2022-01-20 06:31:35 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 (Moderate: Migration Toolkit for Containers (MTC) 1.6.3 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-2022:0202
Note You need to log in before you can comment on or make changes to this bug.