Bug 2126880

Summary: [MTC] Rollback missing out deletion of some resources from the target cluster
Product: Migration Toolkit for Containers Reporter: ssingla
Component: GeneralAssignee: Scott Seago <sseago>
Status: CLOSED ERRATA QA Contact: mohamed <midays>
Severity: high Docs Contact: Anjana Suparna Sriram <asriram>
Priority: unspecified    
Version: 1.7.4CC: jmatthew, midays, rjohnson
Target Milestone: ---   
Target Release: 1.7.5   
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: 2022-10-31 11:10:35 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 ssingla 2022-09-14 16:13:56 UTC 
Description of problem:
On performing rollback of an application from the MTC UI, some resources are not getting deleted from the target cluster and rollback is showing status as successfully completed. 


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

How reproducible:


Steps to Reproduce:
1.Deploy an application on the source cluster
2.Login to the MTC UI and migrate the application using Full migration.
3.Perform the rollback using the same migplan.

Actual results:
Some resources like services, routes, imagestreams remain undeleted on the target cluster.

Expected results:
All resources should be removed from the target cluster on performing rollback.

Additional info:

Example-> Some Leftover resources after a rollback:

$ oc get all -n django
NAME                             TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
service/django-psql-persistent   ClusterIP   172.30.104.100   <none>        8080/TCP   4m55s
service/postgresql               ClusterIP   172.30.162.28    <none>        5432/TCP   4m55s

NAME                                                    IMAGE REPOSITORY                                                                 TAGS     UPDATED
imagestream.image.openshift.io/django-psql-persistent   image-registry.openshift-image-registry.svc:5000/django/django-psql-persistent   latest   3 minutes ago

NAME                                              HOST/PORT                                                                          PATH   SERVICES                 PORT    TERMINATION   WILDCARD
route.route.openshift.io/django-psql-persistent   django-psql-persistent-django.apps.cam-tgt-45860.qe.gcp.devcluster.openshift.com          django-psql-persistent   <all>                 None
Comment 2 Scott Seago 2022-09-15 14:33:58 UTC 
Fix is here: https://github.com/openshift/openshift-velero-plugin/pull/169
Comment 6 mohamed 2022-10-03 13:48:01 UTC 
Verified using MTC 1.7.5

all resources are properly removed
Comment 11 errata-xmlrpc 2022-10-31 11:10: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 (Migration Toolkit for Containers (MTC) 1.7.5 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/RHBA-2022:7262