From 81953af6915f89466da97d7a9c61e2c98bb6f797 Mon Sep 17 00:00:00 2001 From: Jakub Kadlcik Date: Oct 30 2025 12:05:22 +0000 Subject: copr: describe what to do when experiencing Pulp-related issues Fix https://github.com/fedora-copr/copr/issues/3862 --- diff --git a/modules/sysadmin_guide/pages/copr.adoc b/modules/sysadmin_guide/pages/copr.adoc index 8796caf..1c05554 100644 --- a/modules/sysadmin_guide/pages/copr.adoc +++ b/modules/sysadmin_guide/pages/copr.adoc @@ -177,6 +177,28 @@ Logs for the action dispatcher can be found in: Check if there's no stucked process under `Action dispatch` parent process in `pstree -a copr` output. +=== Pulp issues === + +Copr stores (some) build results in Pulp. We don't maintain our own Pulp +instance but rather use an instance hosted on console.redhat.com and maintained +by the Pulp team. In case of issues, please contact them directly. + +How to check for Pulp-related issues: + +- This https://console.redhat.com/api/pulp-content/public-copr/ needs to be + available and return 200 +- If builds get stuck in the `running` state forever, check whether their + `backend.log` ends with repeated attempts to upload the results to Pulp +- Check if builds have any unexpected Pulp-related errors in their `backend.log` + +If you confirmed or suspect a Pulp-related issue, contact the Pulp team: + +- If you have access to the Red Hat internal Slack server, join the + `#pulp-services` channel and ping the `@pulp-services-team` +- Alternatively, join https://matrix.to/#/#pulp-dev:matrix.org and ping one of + the team members: `@dkliban`, `@bmbouter`, `@decko`, `@hyagi`, `@ytrahnov` + + == Deploy information Using playbooks and rbac: