Are outgoing webhooks from qastaging.launchpad.net currently stable?

Asked by Hemanth V. Alluri

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?

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Colin Watson (cjwatson) said :
#1

I think this is a bug, but it's a slightly strange one - the webhook proxy logs seem to show a successful request to the target URL, and it looks as though some specific request exception is then being erroneously serialised as "[Errno 2] No such file or directory". Could you please press "Create bug report" on this question and we'll look into it some more?

Revision history for this message
Hemanth V. Alluri (hypro999) said :
#2

Done.

Revision history for this message
Hemanth V. Alluri (hypro999) said :
#3

Colin Watson, is there any more information that you need from my end?

Revision history for this message
Colin Watson (cjwatson) said :
#4

Not at present, thanks. We're in planning meetings this week so I probably won't be able to look seriously until next week.

Revision history for this message
Hemanth V. Alluri (hypro999) said :
#5

Colin Watson, have there been any advancements/updates regarding this?

Revision history for this message
Colin Watson (cjwatson) said :
#6

Could you retry the delivery now? qastaging has some known wonkiness in its job scheduler that occasionally requires restarting some services; we've just done that and it may help.

(I'm assuming you only need this for short-term testing. qastaging and staging are only for testing Launchpad itself; we make absolutely no guarantees about their stability for things like setting up CI jobs for code elsewhere.)

Revision history for this message
Hemanth V. Alluri (hypro999) said :
#7

> I'm assuming you only need this for short-term testing.

This is correct, I currently only need this to work for about a day on qastaging so that I can store sample responses.

> Could you retry the delivery now? qastaging has some known wonkiness in its job scheduler that occasionally requires restarting some services; we've just done that and it may help.

 I just gave it another go, and unfortunately, I'm still facing the same exact error as before.

Revision history for this message
Colin Watson (cjwatson) said :
#8

Ah, there was long enough between me asking and you trying that we landed a couple more commits to Launchpad and the same problem recurred! However, we've restarted it again and your webhook delivery seems to have succeeded. Is that good enough? We probably won't land much more before the weekend, so you have a few days before it breaks again ...

Revision history for this message
Hemanth V. Alluri (hypro999) said :
#9

I can verify that the payload was successfully delivered on my end, and I'll try to wrap things up by today.

Can you help with this problem?

Provide an answer of your own, or ask Hemanth V. Alluri for more information if necessary.

To post a message you must log in.