Pagure.io is sending a bunch of logs (I'm at 4k in about 1 or 2 hours) about errors coming from firmitas.
Here is one:
URL: https://pagure.io/api/0/firmitas-staging/new_issue args: ImmutableMultiDict([]) form: {'title': '[FMTS] TLS certificate for git-hooks service is about to expire in 300 days', 'issue_content': '\nThis is to inform that the TLS +certificate for **git-hooks** service will expire in about **300 day(s)** from now on **2025-08-03 15:01:55 UTC**. The following are information relevant to +the associated TLS certificate.\n\n- **Service name** - **git-hooks** (Certificate stored as **production/git-hooks.crt**)\n- **Issuing authority** - +RabbitMQ PRODUCTION CA (**#292127154797115116917240515451877285883**)\n- **Validity starting** - **2023-05-01 15:01:55 UTC** (**526 day(s)** passed since +beginning)\n- **Validity ending** - **2025-08-03 15:01:55 UTC** (**299 day(s)** left before expiring)\n\nThe point of contact for the service have been +tagged into this ticket and notified about the same. It is strongly recommended to promptly renew the TLS certificate for the service before the existing one +expires.\n\n_This issue ticket was automatically created by the [**Firmitas not ification service**](https://gitlab.com/t0xic0der/firmitas). Please contact [**Fedora Infrastructure**](https://pagure.io/fedora-infrastructure/issues) team +if you believe that this notification is mistaken._\n', 'tag': 'firmitas,automate,notifier', 'assignee': 'firmitas'} user: firmitas-automata Message: -------- Error while processing request Callstack that lead to the logging statement -------------------------------------------- Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/flask/app.py", line 1982, in wsgi_app response = self.full_dispatch_request() File "/usr/lib/python3.6/site-packages/flask/app.py", line 1614, in full_dispatch_request rv = self.handle_user_exception(e) File "/usr/lib/python3.6/site-packages/flask/app.py", line 1517, in handle_user_exception reraise(exc_type, exc_value, tb) File "/usr/lib/python3.6/site-packages/flask/_compat.py", line 33, in reraise raise value File "/usr/lib/python3.6/site-packages/flask/app.py", line 1612, in full_dispatch_request rv = self.dispatch_request() File "/usr/lib/python3.6/site-packages/flask/app.py", line 1598, in dispatch_request return self.view_functions[rule.endpoint](**req.view_args) File "/usr/lib/python3.6/site-packages/pagure/api/__init__.py", line 228, in decorated_function return function(*args, **kwargs) File "/usr/lib/python3.6/site-packages/pagure/api/__init__.py", line 264, in wrapper result = function(*args, **kwargs) File "/usr/lib/python3.6/site-packages/pagure/api/issue.py", line 197, in api_new_issue user=flask.g.fas_user.username, File "/usr/lib/python3.6/site-packages/pagure/lib/query.py", line 1824, in new_issue assignee_id = get_user(session, assignee).id File "/usr/lib/python3.6/site-packages/pagure/lib/query.py", line 140, in get_user raise pagure.exceptions.PagureException('No user "%s" found' % key) pagure.exceptions.PagureException: No user "firmitas" found
@t0xic0der you're explicitly mentioned there, is this coming from you? Could you fix your script?
Turns out I had something like 23k emails of errors waiting for me to sync. Deleted those... I'll see if I get more recent emails
Thanks for the headsup and apologies for the inconvenience. @dkirwan This is something that we need to look into in today's call.
Metadata Update from @t0xic0der: - Issue assigned to t0xic0der - Issue tagged with: OpenShift, low-trouble, pagure
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
I think this was fixed a while back. At least I don't see them anymore.
Please re-open if this is still happening/we need to do anything further.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.