To create a post conversion report, we require the functions running after the PONR to be ported to the Action framework.

This includes two main subdivisions of post PONR conversion steps and post PONR final changes:

Post PONR conversion steps

• Calling the transaction handler to replace system packages
• Preparing the kernel
• Displaying the remaining non-Red Hat packages
• Configuring the bootloader
• Patching the yum configuration file
• Locking the releasever in RHEL repositories

Post PONR final changes

• Displaying RPM files modified by the conversion
• Updating the GRUB2 configuration
• Removing the temporary folder 
• Checking kernel boot files
• Updating the custom RHSM facts

Acceptance Criteria

Action

1) An action ID and action dependencies are defined

2) An action class is created with the name being based on the functions purpose

3) A run() method is created to hold the contents of the function being converted to an action

4) Any logger critical calls (System Exits) are replaced with set_result() calls to create an error level result (ERROR, OVERRIDABLE) for reporting the logger.critical contents

5) Any relevant logger warning or logger info calls are replaced with add_message() calls to add to the list of reported messages for the report

Unit tests

6) Create a fixture that returns an instance of the action you are testing

7) Invoke the action and assert any results defined in the action using the assert_actions_result() method and any messages using issuperset() and issubset().