Skip to content

fix: retry bootstrap check on on controllers when there are errors #41

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

Merged
merged 1 commit into from
Feb 24, 2025

Conversation

jnsgruk
Copy link
Owner

@jnsgruk jnsgruk commented Feb 24, 2025

At the moment, when concierge checks for a bootstrapped controller, if the command fails the check is considered a failure, and thus that the controller doesn't exist.

In some cases, that is correct, and we can tell that from the error message. In other cases, the check fails because the controller fails to respond.

This commit introduces a retry with backoff on that check.

At the moment, when concierge checks for a bootstrapped controller, if
the command fails the check is considered a failure, and thus that the
controller doesn't exist.

In some cases, that is correct, and we can tell that from the error
message. In other cases, the check fails because the controller fails
to respond.

This commit introduces a retry with backoff on that check.
carlcsaposs-canonical added a commit to canonical/postgresql-test-app that referenced this pull request Feb 24, 2025
@jnsgruk jnsgruk merged commit 1668e37 into main Feb 24, 2025
25 checks passed
@jnsgruk jnsgruk deleted the retry-bootstrap-check branch February 24, 2025 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant