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

ENHANCE_YOUR_CALM / too_many_pings #124

Closed
raphink opened this issue Jan 18, 2022 · 5 comments
Closed

ENHANCE_YOUR_CALM / too_many_pings #124

raphink opened this issue Jan 18, 2022 · 5 comments
Labels
upstream-dependency Issue depends on changes being made to upstream dependencies (e.g. `argoproj/argo-cd`)

Comments

@raphink
Copy link
Contributor

raphink commented Jan 18, 2022

Upon creating multiple resources (argocd_project and argocd_application) on the same server, I'm often getting GOAWAY responses:

Error: application thanos could not be created
│ 
│   with module.metrics-archives.module.thanos.argocd_application.this,
│   on .terraform/modules/metrics-archives/modules/main.tf line 39, in resource "argocd_application" "this":
│   39: resource "argocd_application" "this" {
│ 
│ rpc error: code = Unknown desc = closing transport due to: connection error: desc = "error reading from server: EOF", received prior goaway: code: ENHANCE_YOUR_CALM, debug data:
│ too_many_pings

From what I understand, this is because the Grpc client is sending more pings than the server is configured to receive. Could it be because the resources are applied in parallel?

@luke-plausin-kidsloop
Copy link

I am also impacted by this. It would be nice if the ArgoCD provider could implement backoff and retry logic when this happens.

@onematchfox onematchfox added the upstream-dependency Issue depends on changes being made to upstream dependencies (e.g. `argoproj/argo-cd`) label May 17, 2023
@onematchfox
Copy link
Collaborator

onematchfox commented May 17, 2023

Believe (:crossed_fingers:) that this should have been resolved in this provider (>v4.0.0) due to the dependency upgrade in #207, which contained the following fix to argoproj/argo-cd. Feel free to let me know if this is still an issue, and we can look at it again.

@peturgq
Copy link

peturgq commented Jul 13, 2023

Hi I am encountering this issue on 5.6.0, shot in the dark but it seems the provider might be a bit too aggressive with state refreshing.

@jcogilvie
Copy link

@onematchfox I am also encountering this on 5.6.0 with argo 2.6.7.

I am creating an argo project, repo, and multi-source application. The project and app are already created; the biggest problem I have is when adding a new source to the app. The issue is repeatable.

@jcogilvie
Copy link

@peturgq I opened #326 to track the new issue. By chance are you using a multi-source app?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream-dependency Issue depends on changes being made to upstream dependencies (e.g. `argoproj/argo-cd`)
Projects
None yet
Development

No branches or pull requests

5 participants