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

puppet infra status timeout option is unintuitive #17

Open
bastelfreak opened this issue Apr 5, 2024 · 0 comments
Open

puppet infra status timeout option is unintuitive #17

bastelfreak opened this issue Apr 5, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@bastelfreak
Copy link

Describe the Bug

puppet infra status has a timeout option. I think that's used to tell the API how long it should try to calculate the response and abort if it doesn't finish in time. However it's a bit unintuitive. I've a primary with a few compilers. One of them isn't reachable via network. puppet infra status waits 120 seconds for a response, despite the default timeout of 5 seconds. I think this hardcoded 120s should also default to 5s and honour --timeout.

Truncated output of puppet infra status --debug

Debug: Caching connection for https://server:8081
Debug: Creating new connection for https://server:8140
Debug: Starting connection for https://server:8140
Debug: Exception raised while trying to fetch status for https://server:8140/status/v1/services
Debug: Puppet::HTTP::ConnectionError: Request to https://server:8140/status/v1/services?timeout=5 timed out connect operation after 120.051 seconds

Expected Behavior

puppet infra status should only wait 5s per node, or 5 s per API call per node, for a response.

Steps to Reproduce

  • Install primary
  • install a compiler
  • shutdown the compiler
  • run puppet infra status --debug

Environment

  • PE 2021.7.4

Additional Context

@bastelfreak bastelfreak added the bug Something isn't working label Apr 5, 2024
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