In order to be represented in the pre-assessment report, we need all pre-PONR actions which can fail to be ported to the Action framework.

This includes two main subdivisions:

• The current checks.py code. These pieces of code are already pretty small and self-contained. Porting them to the Action framework should be straightforward. It mostly involves moving the present check into a run() method of an Action subclass and changing logger.critical() calls to raise an exception which can be caught by the Action Runner.
• Miscellaneous pre-ponr actions which are in main() and pre_ponr_changes(). These include:
• backing up files
• removing problematic packages
• preparing the packaging system to install RHEL packages
• registering the system with subscription-manager
• some checks which were not included in the checks.py for case-by-case reasons

The second category will need considerably more analysis and work than the first as what they do is less standardized and may perform changes to the system which would need to be reverted in case of a rollback or once the pre-assessment command finishes.