fedora-infrastructure

#8497 missing push events from src.fedoraproject.org
Closed: Fixed by pingou. Opened by praiskup.

Closed: Fixed
Reopen Issue

Looking at:
https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.pagure.git.receive

The event for this commit doesn't seem to be logged.

I noticed that copr is sometimes unable to post messages to fedora-messaging bus, so we'll have to do something like this.

original report against copr

This needs to be looked at by @pingou when they get back from PTO. We are not sure if this is an upstream pagure problem or our messaging problem.

Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: src.fp.o

Metadata Update from @pingou:
- Issue assigned to pingou

So the message was not sent under the topic: pagure.git.receive but it was under the git.receive topic, cf: https://apps.fedoraproject.org/datagrepper/id?id=2020-62bfd816-fcac-4089-9a52-074ff1d319ef&is_raw=true&size=extra-large

I'm not sure anymore if we used to send all commits to both topics or not?

Checking the config, it looks like we did use to send using both topics, so I've looked further into it.

It seems somehow the configuration changed, so I've changed it again and from my tests, it looks like it is working as desired :)

Is it? When I push, I get a whole bunch of new output and a Python error:

remote: 2020-01-07 19:57:38,890 [INFO] pagure.lib.git_auth: Looking for backend: distgit
remote: 2020-01-07 19:57:38,890 [INFO] pagure.lib.git_auth: Looking for backend: distgit
remote: 2020-01-07 19:57:38,936 [INFO] requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): pdc.fedoraproject.org
fedpkg build remote: 2020-01-07 19:57:40,481 [INFO] pagure.lib.git_auth: Looking for backend: distgit
remote: 2020-01-07 19:57:40,481 [INFO] pagure.lib.git_auth: Looking for backend: distgit
remote: 2020-01-07 19:57:40,530 [INFO] requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): pdc.fedoraproject.org
--nowait
remote: 2020-01-07 19:57:41,976 [INFO] pagure.lib.git_auth: Looking for backend: distgit
remote: 2020-01-07 19:57:41,976 [INFO] pagure.lib.git_auth: Looking for backend: distgit
remote: 2020-01-07 19:57:42,023 [INFO] requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): pdc.fedoraproject.org
git co remote: 2020-01-07 19:57:43,458 [INFO] pagure.lib.git_auth: Looking for backend: distgit
remote: 2020-01-07 19:57:43,458 [INFO] pagure.lib.git_auth: Looking for backend: distgit
remote: 2020-01-07 19:57:43,508 [INFO] requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): pdc.fedoraproject.org
f30
^[[A^[[A
gitremote: Emitting a message to the fedmsg bus.
remote: * Publishing information for 1 commits
remote: * Publishing information for 2 commits
remote: * Publishing information for 2 commits
 coremote: 2020-01-07 19:57:45,685 [INFO] pagure.lib.git_auth: Looking for backend: distgit
remote: 2020-01-07 19:57:45,685 [INFO] pagure.lib.git_auth: Looking for backend: distgit
 remote: Sending to redis to log activity and send commit notification emails
remote: * Publishing information for 2 commits
remote: 2020-01-07 19:57:45,975 [INFO] pagure.lib.notify: Sending blinker signal to: pagure - topic: git.receive
remote: 2020-01-07 19:57:45,975 [INFO] pagure.lib.notify: Sending blinker signal to: pagure - topic: git.receive
master
^[[Aremote:   - to fedmsg
remote: 2020-01-07 19:57:47,084 [WARNING] pagure.lib.notify: fedmsg support is being deprecated in favor of fedora-messaging you likely want to stop relying on it as it will disapear in the future, most likely in the 6.0 release
remote: 2020-01-07 19:57:47,084 [WARNING] pagure.lib.notify: fedmsg support is being deprecated in favor of fedora-messaging you likely want to stop relying on it as it will disapear in the future, most likely in the 6.0 release
remote: Sending to redis to log activity and send commit notification emails
remote: * Publishing information for 1 commits
remote: 2020-01-07 19:57:47,134 [INFO] pagure.lib.notify: Sending blinker signal to: pagure - topic: git.receive
remote: 2020-01-07 19:57:47,134 [INFO] pagure.lib.notify: Sending blinker signal to: pagure - topic: git.receive
remote:   - to fedmsg
remote: 2020-01-07 19:57:47,136 [ERROR] pagure.hooks.default: Error sending fedmsg notifications on commit push
remote: Traceback (most recent call last):
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/default.py", line 52, in send_fedmsg_notifications
remote:     fedmsg.init(name="relay_inbound", **config)
remote: TypeError: init() got multiple values for keyword argument 'name'
remote: 2020-01-07 19:57:47,136 [ERROR] pagure.hooks.default: Error sending fedmsg notifications on commit push
remote: Traceback (most recent call last):
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/default.py", line 52, in send_fedmsg_notifications
remote:     fedmsg.init(name="relay_inbound", **config)
remote: TypeError: init() got multiple values for keyword argument 'name'
^[[Aremote: 
remote: Create a pull-request for f30
remote:    https://src.fedoraproject.org/rpms/R-mime/diff/master..f30
remote: 
remote: Sending to redis to log activity and send commit notification emails
remote: * Publishing information for 2 commits
remote: 2020-01-07 19:57:47,250 [INFO] pagure.lib.notify: Sending blinker signal to: pagure - topic: git.receive
remote: 2020-01-07 19:57:47,250 [INFO] pagure.lib.notify: Sending blinker signal to: pagure - topic: git.receive
remote:   - to fedmsg
remote: 2020-01-07 19:57:47,252 [ERROR] pagure.hooks.default: Error sending fedmsg notifications on commit push
remote: Traceback (most recent call last):
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/default.py", line 52, in send_fedmsg_notifications
remote:     fedmsg.init(name="relay_inbound", **config)
remote: TypeError: init() got multiple values for keyword argument 'name'
remote: 2020-01-07 19:57:47,252 [ERROR] pagure.hooks.default: Error sending fedmsg notifications on commit push
remote: Traceback (most recent call last):
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/default.py", line 52, in send_fedmsg_notifications
remote:     fedmsg.init(name="relay_inbound", **config)
remote: TypeError: init() got multiple values for keyword argument 'name'

Hm, you pushed two commits at once, I'll test that.

Looks like we had a hotfix left in ansible that was helping on one side and breaking on the other.
Since it is no longer needed with the recent pagure release, I've just removed it and reinstalled the RPM, I was then able to push two commits with traceback :)

Ansible commit removing the hotfix: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=f90fce8

could be @fbo 's event problems (https://pagure.io/pagure/issue/4636) related to this?

that's the upstream issue. downstrea, one: https://pagure.io/fedora-infrastructure/issue/8320

@jlanda no I don't think so, it seems all events are affected in my case not only the push one. The most probable issue is this dns resolve issue mentioned by @kevin

Looking at datagrepper for https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.pagure.git.receive and https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.git.receive

The list of commit/notifications seems to be identical, so I believe this ticket can be closed.

Feel free to re-open it or open a new one if you think differently :)

Thanks!

Metadata Update from @pingou:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata

src.fp.o

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.