The parent issue RHELC-1275 has the label that triggered autocreation of this subtask to track the relative story point estimation for the integration test part of the issue.

The parent issue description at the time of creation of this issue was:
During testing of the pre-conversion analysis in Insights, we've realized we have no easy way to programatically discern when a rollback that is being performed at the end of the analysis ends up incomplete (HMS-3128). Currently we have a workaround that looks for keywords like fail or error in the terminal output but that's obviously not ideal.

Acceptance criteria:

• All the rollback steps are performed - i.e. even if one step fails, the following ones are performed nevertheless.
• Rollback step failures are recorded and with 1 or more failed steps convert2rhel exits with 1.
• A critical level log message saying that the rollback failed is printed at the end of the teminal output
  • With a rollback failure the system is in an undefined state and the pre-conversion analysis report has much less of a value - it can be omitted so that the user focuses on the resolving the rollback failure (omit printing the analysis result to terminal as well as generating the json/txt report files)

Related:

• Currently convert2rhel exits with 1 when run in a conversion mode and an inhibitor is detected. To distinguish an inhibitor from a rollback failure, we've decided on Cabal that we'll introduce a new exit code 2 for inhibitors detected during the conversion.