Project

General

Profile

Actions

Bug #33173

closed

'[pulp3] foreman-rake katello:approve_corrupted_migration_content command failed with rake aborted!'

Added by James Jeffers over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Repositories
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

'Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1981017 \n\n*Description of problem:* foreman-rake katello:approve_corrupted_migration_content command failed with rake aborted!\n\n\n*Version-Release number of selected component (if applicable):*\n6.9 \n\n*How reproducible:*\n2/2 with specific customer database\n\n*Steps to Reproduce:*\n1. Restore the 6.9 satellite using the backup data\n2. Run the pulp migration.\n3. Pulp migration failed with 255 status.\n4- Run the command to approve the corrupted contents but it failed with "rake aborted!" error.\n\n foreman-rake katello:approve_corrupted_migration_content\n {:services=>\n {:candlepin=>{:status=>"ok", :duration_ms=>"63"}, \n :candlepin_auth=>{:status=>"ok", :duration_ms=>"49"},\n :foreman_tasks=>{:status=>"ok", :duration_ms=>"3"},\n :katello_events=>\n {:status=>"FAIL", :message=>"Not running", :duration_ms=>"2"},\n :candlepin_events=>\n {:status=>"ok", :message=>"0 Processed, 0 Failed", :duration_ms=>"0"},\n :pulp3=>{:status=>"ok", :duration_ms=>"67"},\n :pulp=>{:status=>"ok", :duration_ms=>"57"},\n :pulp_auth=>{:status=>"ok", :duration_ms=>"30"}}, \n :status=>"FAIL"}\n rake aborted!\n Not all the services have been started. Check the status report above and try again.\n /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)>\'\n /opt/rh/rh-ruby25/root/usr/share/gems/gems/rake-12.3.3/exe/rake:27:in `<top (required)>\'\n Tasks: TOP => katello:approve_corrupted_migration_content => katello:check_ping\n (See full trace by running task with --trace)\n\n\n*Actual results:*\nforeman-rake katello:approve_corrupted_migration_content command failed with rake aborted!\n\n*Expected results:*\nCommand should be completed successfully.\n\n*Additional info:*\nI 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.'

Actions

Also available in: Atom PDF