Created attachment 1788501 [details]
screenshot

Description of problem:
When a migration fails because a hook has failed, if we look at the migration resources list the hook that failed is still reported as Active.

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

How reproducible:
Always

Steps to Reproduce:
1. Create an empty namespace in the source cluster

oc new-project bz-test


2. Create a migration plan for this namespace and add a PreBackup hook that will always fail. We can use "openshift-migration" namespace and "migration-controller" SA to run the hook and run it in the source cluster.

Hook example:

- hosts: localhost
  tasks:
  - fail:
      msg: "Always fail"

3. Run the migration

4. When the migration fails click on "Migration resources"

Actual results:
The migration resources list will show the hook job as "Active", even if it failed and the migration finished.

Expected results:
Since the job was already executed and failed, and the migration is finished too, the job for the hook should not be displayed as an active resource in the list.

Additional info:
Attached a screenshot showing the Active Job resource in a finalized and failed migration plan.