Actions
Bug #33943
closed
Content migration fails with 502 Proxy Error
Description
When i start the content prepare tasks with foreman-maintain content prepare the task ends with 502 Proxy Error.
I can not see why this happens, but it happens always even when i retry the command to start the prepare again.
foreman-maintain content prepare
Running Prepare content for Pulp 3
================================================================================
Prepare content for Pulp 3:
Rubocop not loaded.
Rubocop not loaded.
Checking for valid Katello configuraton.
Starting task.
2021-11-17 11:23:42 +0100: Importing migrated yum repositories: 41/43Migration failed, You will want to investigate: https://johnny.nr.eight/foreman_tasks/tasks/df15003c-867e-4014-81a7-81fb9ab6de81
rake aborted!
ForemanTasks::TaskError: Task df15003c-867e-4014-81a7-81fb9ab6de81: Pulp2to3MigrationClient::ApiError: Error message: the server returns an error
HTTP status code: 502
Response headers: {"Date"=>"Wed, 17 Nov 2021 10:23:12 GMT", "Server"=>"Apache", "Content-Length"=>"429", "Content-Type"=>"text/html; charset=iso-8859-1"}
Response body: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>502 Proxy Error</title>
</head><body>
<h1>Proxy Error</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
The proxy server could not handle the request <em><a href="/pulp/api/v3/pulp2content/">GET /pulp/api/v3/pulp2content/</a></em>.<p>
Reason: <strong>Error reading from remote server</strong></p></p>
</body></html>
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.18.4/lib/katello/tasks/pulp3_migration.rake:39: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:pulp3_migration
(See full trace by running task with --trace)
[FAIL]
Failed executing foreman-rake katello:pulp3_migration, exit status 1
--------------------------------------------------------------------------------
Scenario [Prepare content for Pulp 3] failed.
The following steps ended up in failing state:
[content-prepare]
Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="content-prepare"
All other pulp tasks in this task are completed successfully.
Updated by
Actions