|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc |
| 4 | +// * migration-toolkit-for-containers/troubleshooting-mtc.adoc |
| 5 | + |
| 6 | +[id="migration-viewing-migration-plan-resources_{context}"] |
| 7 | += Viewing migration plan resources |
| 8 | + |
| 9 | +You can view migration plan resources to monitor a running migration or to troubleshoot a failed migration by using the {mtc-short} web console and the command line interface (CLI). |
| 10 | + |
| 11 | +.Procedure |
| 12 | + |
| 13 | +. In the {mtc-short} web console, click *Migration Plans*. |
| 14 | +. Click the *Migrations* number next to a migration plan to view the *Migrations* page. |
| 15 | ++ |
| 16 | +The *Migrations* page displays the migration types associated with the migration plan, for example, *Stage*, *Migration*, or *Rollback*. |
| 17 | + |
| 18 | +. Click the *Type* link to view the *Migration details* page. |
| 19 | + |
| 20 | +. Expand *Migration resources* to view the migration resources and their status. |
| 21 | ++ |
| 22 | +[NOTE] |
| 23 | +==== |
| 24 | +To troubleshoot a failed migration, start with a high-level resource that has failed and then work down the resource tree towards the lower-level resources. |
| 25 | +==== |
| 26 | + |
| 27 | +. Click the Options menu {kebab} next to a resource and select one of the following options: |
| 28 | + |
| 29 | +* *Copy `oc describe` command* copies the command to your clipboard. |
| 30 | + |
| 31 | +** Log in to the relevant cluster and then run the command. |
| 32 | ++ |
| 33 | +The conditions and events of the resource are displayed in YAML format. |
| 34 | + |
| 35 | +* *Copy `oc logs` command* copies the command to your clipboard. |
| 36 | + |
| 37 | +** Log in to the relevant cluster and then run the command. |
| 38 | ++ |
| 39 | +If the resource supports log filtering, a filtered log is displayed. |
| 40 | + |
| 41 | +* *View JSON* displays the resource data in JSON format in a web browser. |
| 42 | ++ |
| 43 | +The data is the same as the output for the `oc get <resource>` command. |
0 commit comments