-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Labels
bug
Something isn't working
Comments
mhoyer
added a commit
to mhoyer/argo-cd
that referenced
this issue
Apr 14, 2021
Signed-off-by: Marcel Hoyer <[email protected]>
10 tasks
alexmt
pushed a commit
that referenced
this issue
Apr 14, 2021
Signed-off-by: Marcel Hoyer <[email protected]> Co-authored-by: Marcel Hoyer <[email protected]>
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
…roj#6034) Signed-off-by: Marcel Hoyer <[email protected]> Co-authored-by: Marcel Hoyer <[email protected]>
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist:
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
:The Webhook event details ("View details") show me:
Request details
Headers
Body
Response
HTTP status:
200
Headers
Body
... and in the logs of the
argocd-server
pod I find similar lines related to the "test connection" requests: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:Expected behavior
diagnostic:ping
should work and return a200
in Bitbucket serverVersion
Logs
Essential parts posted above already.
The text was updated successfully, but these errors were encountered: