Katello-nightly-rpm-pipeline 1027 failed

Katello nightly pipeline failed:


foreman-pipeline-katello-nightly-centos7-upgrade (failed) (remote job)
foreman-pipeline-katello-nightly-centos7-install (failed) (remote job)
foreman-pipeline-katello-nightly-centos8-stream-install (failed) (remote job)
foreman-pipeline-katello-nightly-centos8-install (failed) (remote job)
foreman-pipeline-katello-nightly-centos8-upgrade (passed) (remote job)

seems this


broke the proxy, as I see in the logs (on the proxy) now:

pulpcore-api[27707]: pulp [2140b308e4e846deb48c5f130b5ed405]: pulpcore.app.views.status:ERROR: Connection to Redis failed during status check!

which is translated to this error in Katello:

2021-07-13T00:22:34 [I|bac|1fffc985] Task {label: Actions::Katello::CapsuleContent::Sync, id: 007c16b7-20e4-4ca6-8190-4cecf00500e1, execution_plan_id: 5391d69e-d01c-4bc0-bf8e-7a3e52de328c} state changed: stopped  result: error
2021-07-13T00:22:34 [E|app|1fffc985] RuntimeError: There was an issue with the backend service pulp3: Pulp redis connection issue at https://pipe-katello-proxy-nightly-centos7.n12.example.com/pulp/api/v3.

I didn’t read the logs carefully, but looking at the code this may be an issue:

This suggests Pulp doesn’t consider Redis as optional:

I’ve submitted a PR and will reach out to upstream to see if we can change this:

It also looks like we need to update our local_redis? definition here:

The “optional redis” was now reverted by Eric.

And to close the loop, after the revert, pipeline is green again

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.