Bug 2236829 - Old restic pods are not getting removed on upgrading MTC 1.7.x -> 1.8
Summary: Old restic pods are not getting removed on upgrading MTC 1.7.x -> 1.8
Keywords:
Status: NEW
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Operator
Version: 1.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: John Matthews
QA Contact: ssingla
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-09-01 16:21 UTC by ssingla
Modified: 2023-09-26 16:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
pods (157.22 KB, image/png)
2023-09-01 16:21 UTC, ssingla 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OADP-2139 0 None None None 2023-09-26 16:45:03 UTC

Description ssingla 2023-09-01 16:21:36 UTC 
Created attachment 1986601 [details]
pods

Description of problem:
On upgrading the MTC operator from 1.7.x to 1.8.x, the old restic pods are not being removed. Hence, after the upgrade,both restic and node-agent pods are visible in the namespace.

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

How reproducible:
Always


Steps to Reproduce:
1. Install and setup MTC 1.7.x operator
2. Upgrade MTC 1.7.x to MTC 1.8.x
3. Check the pods in openshift-migration namespace

Actual results:
Old restic pods are still there.

Expected results:
Old restic pods should be removed.

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