Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BitbucketServer Webhooks: diagnostic:ping not working after upgrade to v2.0.0 #6029

Closed
3 tasks done
mhoyer opened this issue Apr 14, 2021 · 0 comments
Closed
3 tasks done
Labels
bug Something isn't working

Comments

@mhoyer
Copy link
Contributor

mhoyer commented Apr 14, 2021

Checklist:

  • I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
  • I've included steps to reproduce the bug.
  • I've pasted the output of argocd version.

Describe the bug

With the previous installation of ArgoCD v1.8.7 (and earlier) we successfully established a webhook with our own on-premise Bitbucket server (currently v7.10.1) following the guidelines in the docs. After the update to v2.0.0 last week it's still working, but started to break with diagnostic:ping events.

In Bitbucket the Test connection button now fails with a 400:

image

The Webhook event details ("View details") show me:

Request details

Headers

X-Event-Key: diagnostics:ping
X-Request-Id: a528e9e3-d16f-4746-8772-91d58192d7bd
Content-Type: application/json

Body

{"test": true}

Response

HTTP status: 200

Headers

Connection: keep-alive
Content-Length: 58
X-Content-Type-Options: nosniff
Date: Tue, 13 Apr 2021 16:31:58 GMT
Via: 1.1 localhost (Apache-HttpClient/4.5.5 (cache))
Content-Type: text/plain; charset=UTF-8

Body

Webhook processing failed: event not defined to be parsed

... and in the logs of the argocd-server pod I find similar lines related to the "test connection" requests:

time="2021-04-13T15:56:26Z" level=info msg="Webhook processing failed: event not defined to be parsed"

I guess this is simply and straight related to #5565, which actually enabled the exposure of such a errors at all!? Still it's weird. Hence, the underlying go-playground/webhooks repository knows about this diagnostics:ping event: bitbucket-server/bitbucketserver.go#L51.

To Reproduce

Just POST this request to the Argo CD webhook endpoint:

POST /api/webhook
X-Event-Key: diagnostics:ping
X-Request-Id: a528e9e3-d16f-4746-8772-91d58192d7bd
Content-Type: application/json

{"test": true}

Expected behavior

  • diagnostic:ping should work and return a 200 in Bitbucket server

Version

$ argocd version --port-forward --insecure
argocd: v2.0.0+f5119c0
  BuildDate: 2021-04-07T06:03:59Z
  GitCommit: f5119c06686399134b3f296d44445bcdbc778d42
  GitTreeState: clean
  GoVersion: go1.16
  Compiler: gc
  Platform: windows/amd64
argocd-server: v2.0.0+f5119c0
  BuildDate: 2021-04-07T06:00:33Z
  GitCommit: f5119c06686399134b3f296d44445bcdbc778d42
  GitTreeState: clean
  GoVersion: go1.16
  Compiler: gc
  Platform: linux/amd64
  Ksonnet Version: v0.13.1
  Kustomize Version: v3.9.4 2021-02-09T19:22:10Z
  Helm Version: v3.5.1+g32c2223
  Kubectl Version: v0.20.4
  Jsonnet Version: v0.17.0

Logs

Essential parts posted above already.

@mhoyer mhoyer added the bug Something isn't working label Apr 14, 2021
mhoyer added a commit to mhoyer/argo-cd that referenced this issue Apr 14, 2021
alexmt pushed a commit that referenced this issue Apr 14, 2021
@mhoyer mhoyer closed this as completed Apr 15, 2021
yujunz added a commit to abcue/argo-cd that referenced this issue Apr 15, 2021
5bc7297 fix: bitbucket server failing diagnostics:ping (argoproj#6029) (argoproj#6034)
8f53bd5 fix: add helm dependencies with custom CA (argoproj#6003)
8fd6f13 docs: Custom resource actions (argoproj#5838)
8a2897d docs: update delete policy verbiage (argoproj#6025)
c847bd9 chore: remove Argo CD CRDs from namespaced install (argoproj#6022)
61080b3 docs: improve Orphaned Resources Monitoring with more examples and correct grammar (argoproj#6006)
8301d39 Adding explicit bind to redis and sentinel for IPv4 clusters argoproj#5957 (argoproj#6005)
12cabdf fix: adding tests for helm OCI registry (argoproj#5978)
9da9514 docs: Add Ant Group to the list of users (argoproj#6011)
5e34a8a add Polarpoint.io (argoproj#6010)
2f92777 chore: move access checks from api server to repo server (argoproj#5940)
ae2d0ff fix(ui): Unscheduled pods in node view are now visible. Fixes argoproj#5981 (argoproj#5988)
b003f70 docs: SealedSecret status missing on k8s 1.16+ (argoproj#5846)
445872f fix: use correct field for evaluating whether or not GitHub Enterprise is selected (argoproj#5987)
9afa833 chore: Make e2e tests runnable against remote cluster (argoproj#5895)
shubhamagarwal19 pushed a commit to shubhamagarwal19/argo-cd that referenced this issue Apr 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant