Currently, when an inhibitor is detected, convert2rhel exits with 1 when run in a conversion mode and exits with 0 when run in a the analysis mode. 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 both the conversion and 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 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 current exit codes when there's an inhibitor