Add troubleshooting guide for pagure

Add guide to Pagure SOP for troubleshooting when pull request throws 500 when opened.

Signed-off-by: Michal Konecny <mkonecny@redhat.com>
This commit is contained in:
Michal Konecny 2024-01-29 14:18:24 +01:00
parent a7befa86e9
commit 4fa4bcc6ad

View file

@ -107,3 +107,57 @@ If the project remains un-accessible, check the apache logs, it could be
that the git repositories have not been created. In that case, the
simplest course of action is to delete all the duplicates and let the
users re-create the projects as they wish.
== Troubleshooting
=== Pull request throws 500 when opened
. Check the permissions on `pagure02`
+
The repositories could be found on `/srv/git/repositories/` and inside each
you can check `refs/pull/<PR_number>` directory.
. Close the PR using `requests` repository
+
If there isn't anything wrong with permissions or the directory is empty,
try to close the PR using `requests` repository.
You need to have commit/admin permissions on the repository.
+
.. Clone the `requests` repository
+
You can find the clone link in `Other Git URLs` in `Clone` button
+
.. Find the correct pull requests by hash
+
Use `git log` for that
+
.. Update the status of the pull request to `Closed`
.. Push the change
. Removing the PR from project
+
This should be last resort when everything others fails.
+
.. Log in to PostgreSQL db on `pagure02`
+
....
`sudo -u postgres psql`
....
+
.. Connect to pagure database
+
....
`\connect pagure`
....
+
.. Find the project_id by name
+
....
select id from projects where name='<name_of_project>' and is_fork=false;
....
+
.. Delete the desired pull request
+
....
delete from pull_requests where id=<PR_number_in_pagure> and project_id=536
....