I guess we still use fedmsg on bodhi-backend01 for koji-sync-listener? If so, it's probably not working right now because a CRL has expired there:
[2019-06-10 19:44:23][fedmsg.crypto.x509_ng ERROR]
[12, 0, 'CRL has expired']
File "/usr/local/bin/koji-sync-listener.py", line 55 in <module> for _, _, topic, msg in fedmsg.tail_messages(topic=topic): File "/usr/lib/python2.7/site-packages/fedmsg/__init__.py", line 109 in tail_messages for item in __local.__context.tail_messages(**kw): File "/usr/lib/python2.7/site-packages/fedmsg/core.py", line 367 in tail_messages for msg in self._poll(poller, subs): File "/usr/lib/python2.7/site-packages/fedmsg/core.py", line 439 in _poll yield self._run_socket(s, name, ep, watched_names) File "/usr/lib/python2.7/site-packages/fedmsg/core.py", line 458 in _run_socket if not validate or fedmsg.crypto.validate(msg, **self.c): File "/usr/lib/python2.7/site-packages/fedmsg/crypto/__init__.py", line 244 in validate return backend.validate(message, **cfg) File "/usr/lib/python2.7/site-packages/fedmsg/crypto/x509_ng.py", line 182 in validate _log.error(str(e))
yeah, I'm getting tracebacks with the same error from the openQA servers too. I presume this is breaking everything fedmsg-y. Which is...bad.
This should now be fixed.
:eyeglasses:
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.