Hi folks!
I am trying to get events from GitLab pushed to the fedora-messaging infrastructure.
For this, I created a new token via https://webhook.fedoraproject.org and followed the gitlab instructions to add a new Webhook with the url and token. I used this personal project for experimentation: https://gitlab.com/mengel1/custom-qm-policy
When triggering test events, I get an 502 error with the following message:
{ "detail": "Message could not be sent: (403, \"ACCESS_REFUSED - access to topic 'org.fedoraproject.prod.gitlab.merge_request' in exchange 'amq.topic' in vhost '/pubsub' refused for user 'webhook2fedmsg'\")" }
It seems there is a typo in the topic: In the instruction page it states org.fedoraproject.prod.gitlab.pull_request, compared to the actually sent org.fedoraproject.prod.gitlab.merge_request. The same applies for the issue (org.fedoraproject.prod.gitlab.issue vs org.fedoraproject.prod.gitlab.issues) and comment (org.fedoraproject.prod.gitlab.note vs org.fedoraproject.prod.gitlab.issue_comment) event. The org.fedoraproject.prod.gitlab.push seems to match, but I still get the same 502 error.
org.fedoraproject.prod.gitlab.pull_request
org.fedoraproject.prod.gitlab.merge_request
issue
comment
org.fedoraproject.prod.gitlab.push
Is this due to (backend) service issue or did I simply misconfigure it?
Note: Using https://webhook.fedoraproject.org for github webhooks works as expected.
@abompard @t0xic0der Do you know what is happening here?
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, medium-trouble
Any updates on this?
Commit 703e67fd fixes this issue
Sorry I didn't see this earlier. It was a permissions problem, it should be fixed now.
I'll also fix the docs. Thanks a lot for reporting.
Issue status updated to: Open (was: Closed)
Metadata Update from @zlopez: - Issue assigned to abompard - Issue tagged with: sprint-0
Issue status updated to: Closed (was: Open) Issue close_status updated to: Fixed
Metadata Update from @zlopez: - Issue untagged with: sprint-0