Foreman/Katello no longer talking to pulpcore

Support
#1

Problem:
I somehow managed to disconnect pulpcore from foreman/katello during various pulp2to3 migrations and possible fixes for the migrations.

For example the remove_orphans task never arrives at pulpcore currently. Verified via API Curl to list pulpcores task. Foreman keeps endlessly querying its api and never receives a result.

As well i am not able the reset the current migration task.
foreman-rake katello:pulp3_migration_reset gives:
Only one migration plan can run or be reset at a time
While
foreman-rake katello:pulp3_migration_abort results in
Cancelled 0 tasks.

Ran foreman-installer multiple times with no errors.

Is there a way reconnect or debug the connection in between them?

Foreman and Proxy versions:
Foreman 2.3.4 Katello 3.18.2.1

Distribution and version:
Centos 7

#2

Does hammer ping show OK for pulp3? If not, is there a stack trace in your /var/log/foreman/production.log or any errors in journalctl when you are performing the commands you mentioned?

#3

Hi,
i managed to resolve the issue.
If somebody else running into this:
The problem were pulp3 zombieworkers. Further info and a solution can be found here:

1 Like