When I try to access tickets in the "releng" pagure instance, I just get a server response with status code 500: "A fatal error occured"
Example URL: https://pagure.io/releng/fedora-scm-requests/issue/73977
I suspect that this also affects automated creation of branches:
releng-bot added a new comment to an issue you are following: Error happened during processing: Traceback (most recent call last): File "/opt/app-root/src/toddlers/plugins/scm_request_processor.py", line 189, in process self.process_ticket(issue) File "/opt/app-root/src/toddlers/plugins/scm_request_processor.py", line 301, in process_ticket self.create_new_branch(issue, issue_body) File "/opt/app-root/src/toddlers/plugins/scm_request_processor.py", line 775, in create_new_branch self.dist_git.new_branch( File "/opt/app-root/src/toddlers/utils/pagure.py", line 500, in new_branch raise PagureError( toddlers.exceptions.pagure_error.PagureError: Couldn't create branch in project 'rpms/python-responses' Request to 'https://src.fedoraproject.org/api/0/rpms/python-responses/git/branch': {'branch': 'epel10.0', 'from_commit': 'e73b53b22717935eedc1a5100708cccb5e37b78a'}
On Mon, Mar 31, 2025 at 08:10:26AM +0000, Felix Schwarz wrote:
fschwarz reported a new issue against the project: fedora-infrastructure that you are following: `` When I try to access tickets in the "releng" pagure instance, I just get a server response with status code 500: "A fatal error occured" Example URL: https://pagure.io/releng/fedora-scm-requests/issue/73977
fschwarz reported a new issue against the project: fedora-infrastructure that you are following: `` When I try to access tickets in the "releng" pagure instance, I just get a server response with status code 500: "A fatal error occured"
fedora-infrastructure
This should have been fixed in #12467
Let us know if that issue remains.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: high-gain, low-trouble, ops
Metadata Update from @zlopez: - Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)
yes, thank you.
Metadata Update from @fschwarz: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.