Outgoing webhooks from qastaging.launchpad.net not successfully contacting target endpoint

Bug #1829268 reported by Hemanth V. Alluri
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

What I'm trying to achieve:
    I'm trying to generate test fixtures from the (outgoing) Launchpad API/Webhook for git based repositories.

What steps I've taken and what happened:
    I've configured a webhook target for my project: https://code.qastaging.launchpad.net/~hdrive1999/zulip-x-launchpad and pointed it to a webhook.site endpoint (a tool commonly used for this sort of thing). However when trying out the "push" event I was confronted with the following error message: `git:push:0.1 Connection error: [Errno 2] No such file or directory`.
    Then I changed the target to a pasteb.in endpoint which is another commonly used tool for testing webhooks. However I received the same error.

Additional comments:
    At this resource: https://help.launchpad.net/API/Webhooks, the following was mentioned: "You should ensure that your firewall allows HTTP/HTTPS access (as appropriate) from all the IP addresses associated with webhooks-proxy.launchpad.net. If you are testing from the qastaging sandbox, you should also allow webhooks-proxy.qastaging.paddev.net." Now as far as I'm aware, I do not think that either one of the online tools that I've used would actively block internet traffic from either source. Thus I do not think that this would be an issue, but feel free to let me know if I'm wrong (with supporting details though).

Ultimately what I want here:
    Why am I not able to receive updates from the webhook? Is this due to a known bug in launchpad? Is this even a bug in the first place (as opposed to me doing something wrong)? Is this an issue due to the webhook still being in a beta phase? How can I fix this situation - i.e. actually receive the output of the webhook so that I can save the results as test fixtures?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.