The parent issue RHELC-1276 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:
Currently convert2rhel exits with 1 when run in a conversion mode and an inhibitor is detected. To distinguish an inhibitor from any kind of unexpected convert2rhel termination (traceback, rollback failure, etc.), we've decided on Cabal that we'll introduce a new exit code 2 for inhibitors detected during the conversion.

This will allow the consumers of convert2rhel (scripts, playbooks, etc.) to stop parsing the pre-conversion analysis report json to find out if there was "just" an inhibitor detected during the analysis or if convert2rhel failed in a serious way.

Acceptance criteria:

• When convert2rhel is run in the conversion mode (not the 'analyze' mode), whenever there's an inhibitor detected during the pre-conversion analysis convert2rhel stops with exit code 2.
  • Unless the inhibitors are overrided by the user (the conversion continues) or unless there's been a rollback failure (exit code 1, RHELC-1275)
• Bump the convert2rhel version number
  • Customers can already have automation/scripts depending on the exit code being 0 when there's an inhibitor