Hi @senetm ! Is there a chance that you upgraded from Foreman 2.3.x to 2.3.2 without running the foreman-installer? I wonder if there are any other stack traces in journalctl related to this error (not including what you’ve shared from /var/log/foreman/production.log)
Hi…i have upgraded from Foreman 2.2.x direct to 2.3.2 with foreman-installer. I have try to migrate from pulp2 to pulp3 and unfortionaly not successful.
Thank you. This is the most interesting part of your pastebin:
Response body: {"detail":"You do not have permission to perform this action."}undefined method each’ for nil:NilClass`
When you perform the file upload do you see a stack trace in journalctl related to this error? The one you shared is from the Forman app in /var/log/foreman/production.log which relates to the Ruby stack. I’m looking for a Python stack trace in particular.
Also, what error did you encounter with the pulp 2->3 migration? Could be related.
Now i am getting ( katello-3.18.2-1.el7.noarch and foreman-2.3.3-1.el7.noarch):
foreman-maintain content prepare
Running Prepare content for Pulp 3
Prepare content for Pulp 3:
Starting task.
2021-03-26 09:33:09 +0100: Content migration starting. Migration failed, You will want to investigate: https://foreman.com/foreman_tasks/tasks/fae253a9-0f64-48da-97f0-1326b8e6a467
rake aborted!
ForemanTasks::TaskError: Task fae253a9-0f64-48da-97f0-1326b8e6a467: Pulp2to3MigrationClient::ApiError: Error message: the server returns an error
HTTP status code: 400
Response headers: {“date”=>“Fri, 26 Mar 2021 08:33:10 GMT”, “server”=>“gunicorn/20.0.4”, “content-type”=>“application/json”, “vary”=>“Accept,Cookie”, “allow”=>“POST, OPTIONS”, “x-frame-options”=>“SAMEORIGIN”, “content-length”=>“57”, “via”=>“1.1 foreman.com”, “connection”=>“close”}
Response body: [“Only one migration plan can run or be reset at a time”]
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.18.2.1/lib/katello/tasks/pulp3_migration.rake:33:in block (2 levels) in <top (required)>' /opt/rh/rh-ruby25/root/usr/share/gems/gems/rake-12.3.0/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”