Bug 2072186

Summary:	Wrong migration type description
Product:	Migration Toolkit for Containers	Reporter:	Marco Berube <mberube>
Component:	UI	Assignee:	Mike Turley <mturley>
Status:	CLOSED ERRATA	QA Contact:	Prasad Joshi <prajoshi>
Severity:	medium	Docs Contact:	Richard Hoch <rhoch>
Priority:	medium
Version:	1.7.0	CC:	ernelson, prajoshi, rjohnson
Target Milestone:	---
Target Release:	1.7.1
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-05-05 13:50:07 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 Marco Berube 2022-04-05 18:29:12 UTC

Description of problem:

Wrong migration type description in the migrate type dropdown of "create a migration plan".


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


How reproducible:


Steps to Reproduce:
1. Create a migration plan
2. Open migration type dropdown


Actual results:

State migration - migrate only PVs and kubernetes resources between namespaces in the same cluster or different clusters


Expected results:

State migration - migrate only PVs between namespaces in the same cluster or different clusters


Additional info:

State migration doesn't copy k8s resources, only PVs.

Comment 1 Richard Hoch 2022-04-13 07:39:11 UTC

Marco -- I just checked the documentation. this needs to be changed in the documentation as well. I've created a BZ for this: https://bugzilla.redhat.com/show_bug.cgi?id=2074819

Comment 2 Richard Hoch 2022-04-13 10:06:36 UTC

Marco -- Section 8.2.5 of the MTC documentation ("Running a migration plan in the MTC web console")  https://access.redhat.com/documentation/en-us/openshift_container_platform/4.9/html-single/migration_toolkit_for_containers/index#migration-running-migration-plan-cam_migrating-applications-with-mtc  has note after stage 2 that says "IMPORTANT: Do not use state migration to migrate a namespace between clusters. Use stage or cutover migration instead."  Is that still correct for the web console or should I remove it and adjust the definition of "state" there (add that you can migrate between clusters, as well as removing the reference to Kubernetes resources)?

Comment 6 Prasad Joshi 2022-04-19 14:03:14 UTC

Verified with MTC 1.7.1 (Prestage)

meatadata_nvr: openshift-migration-operator-metadata-container-v1.7.1-8

I see the expected string in migration_type.

Moving this to verified status.

Comment 8 errata-xmlrpc 2022-05-05 13:50:07 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.7.1 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:1734

Comment 9 Red Hat Bugzilla 2023-09-15 01:53:38 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days