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

Make retry_enablement as configurable parameter #190

Closed
abhijeetkaurav1st opened this issue Sep 24, 2021 · 1 comment · Fixed by #260
Closed

Make retry_enablement as configurable parameter #190

abhijeetkaurav1st opened this issue Sep 24, 2021 · 1 comment · Fixed by #260
Labels
enhancement New feature or request P1 Critical

Comments

@abhijeetkaurav1st
Copy link
Collaborator

Right now retries_enabled is set to True. It doesn't exactly get the correct message of api breakage.
Max retries exceeded with url: /api/nutanix/v3/services/nucalm/status (Caused by ResponseError('too many 503 error responses'))

Make it configurable
calm set config --retries enable/disable. By default it will be enable.

@abhijeetkaurav1st abhijeetkaurav1st added enhancement New feature or request P1 Critical labels Sep 24, 2021
@abhijeetkaurav1st
Copy link
Collaborator Author

Add retry_timeout, connection_timeout also

abhijeetkaurav1st pushed a commit that referenced this issue Aug 22, 2023
(cherry picked from commit a854fd61677d729d51f85504233f31157fc2c71c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P1 Critical
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant