Description of problem: foreman-rake katello:approve_corrupted_migration_content command failed with rake aborted!


Version-Release number of selected component (if applicable):
6.9 

How reproducible:
2/2 with specific customer database

Steps to Reproduce:
1. Restore the 6.9 satellite using the backup data
2. Run the pulp migration.
3. Pulp migration failed with 255 status.
4- Run the command to approve the corrupted contents but it failed with "rake aborted!" error.

 foreman-rake katello:approve_corrupted_migration_content
 {:services=>
   {:candlepin=>{:status=>"ok", :duration_ms=>"63"},  
    :candlepin_auth=>{:status=>"ok", :duration_ms=>"49"},
    :foreman_tasks=>{:status=>"ok", :duration_ms=>"3"},
    :katello_events=>
     {:status=>"FAIL", :message=>"Not running", :duration_ms=>"2"},
    :candlepin_events=>
     {:status=>"ok", :message=>"0 Processed, 0 Failed", :duration_ms=>"0"},
    :pulp3=>{:status=>"ok", :duration_ms=>"67"},
    :pulp=>{:status=>"ok", :duration_ms=>"57"},
    :pulp_auth=>{:status=>"ok", :duration_ms=>"30"}},  
  :status=>"FAIL"}
 rake aborted!
 Not all the services have been started. Check the status report above and try again.
 /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.18.1.32/lib/katello/tasks/reimport.rake:10:in `block (2 levels) in <top (required)>'
 /opt/rh/rh-ruby25/root/usr/share/gems/gems/rake-12.3.3/exe/rake:27:in `<top (required)>'
 Tasks: TOP => katello:approve_corrupted_migration_content => katello:check_ping
 (See full trace by running task with --trace)


Actual results:
foreman-rake katello:approve_corrupted_migration_content command failed with rake aborted!

Expected results:
Command should be completed successfully.

Additional info:
I raised this bug because I am not sure of the actual behavior whether the services should be running after 255 status or need to restart the services after getting the 255 status and then run the "foreman-rake katello:approve_corrupted_migration" command.