There was an issue with the backend service pulp3: Pulp redis connection issue at

There was an issue with the backend service pulp3: Pulp redis connection issue at

Reference URL:

Expected outcome:

Not to get this error

Foreman and Proxy versions:

Foreman and Proxy plugin versions:

Distribution and version:

Other relevant data:

Foreman version: 3.2.1

  • foreman-tasks 6.0.1
  • foreman_remote_execution 6.0.0
  • katello

Did you happen to come across a solution to this? I’m seeing the same “Pulp redis connection issue” with my setup. Pulp status shows “redis_connection” “connected”: false and I don’t really see any smoking guns in logs.

I only started to get this issue after upgrading to the 4.5 RC2, after rolling back to everything worked again :thinking:

1 Like

Thank you, @lumarel. I updated Katello to 4.5 RC 2 also when I updated Foreman to 3.3.0. I will try downgrading Katello.

Please remember, that you can’t run Foreman 3.3 with Katello 4.4, you need to roll back both :slightly_smiling_face:
But good luck! (I fortunately had a system snapshot)

(that might also be the time I could mention the other thread I opened for that to not have to duplicate the information Upgrade issue to 4.4.1 - Internal Server Error (and a notice about 4.5 RC2) )

Thank you. I generally try to ferret out an answer in old posts and from other places long before I ever consider posting. I happened to miss that one and do appreciate you dropping it here. My apology.

1 Like

I’m also trying to do that, but it’s hard sometimes, so nothing to apologize for :slight_smile:

I’m receiving this message after upgrading from 4.4.1 to 4.5.0

There were no errors during the upgrade.

Started at: 2022-07-13 14:53:48 UTC

Ended at: 2022-07-13 14:53:48 UTC (duration 0.06s)


--- {}
There was an issue with the backend service pulp3: Pulp redis connection issue at https://vlpkatello01/pulp/api/v3. (RuntimeError)
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-4.5.0/app/lib/actions/middleware/backend_services_check.rb:17:in `block in plan'

trace-pulp.tar (35 KB)

Could you please have a look in the /etc/foreman-installer/scenarios.d/katello-answers.yaml file please and check that the pulpcore_cache_enabled parameter is set to true?


If it is set to false, set it to true and rerun the foreman-installer :+1:


This fixed my Katello 4.4->4.5 upgrade too. :+1:

1 Like

FTR, this is tracked in Bug #35157: cache-enabled setting for proxy content module isn't migrated to 'true' properly - Installer - Foreman and should be fixed in the next point release of Foreman (no, I don’t know off hand when this happens)


This (fixing the pulpcore cache entry as noted above) fixed my 4.5 installation too. I just upgraded from 4.4 yesterday.

Yesterday morning: “Should I upgrade to 4.5? I see it’s 4.5.0… maybe I should wait for 4.5.1…”

Dang, should have gone with my gut feeling hahahahahahaha.

1 Like