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

Fix service checks #78

Merged
merged 1 commit into from
Sep 10, 2024
Merged

Fix service checks #78

merged 1 commit into from
Sep 10, 2024

Conversation

jdrew82
Copy link
Contributor

@jdrew82 jdrew82 commented Jul 8, 2024

This PR closes the issue in #66.

@jdrew82 jdrew82 requested a review from jvanderaa as a code owner July 8, 2024 17:24
@ryaelo
Copy link

ryaelo commented Jul 17, 2024

I tried using this branch, but the service seems to be declared healthy prematurely and thus the failure described still exists. If invoke start is run again after the nautobot service is fully up and running (can log in, etc.), the issue is resolved.

@glennmatthews
Copy link

@ryaelo Can you confirm what Nautobot version you're running? There were changes made to the default health-check in Nautobot v2.2.0 that should mitigate that, but older versions might still show issues.

@ryaelo
Copy link

ryaelo commented Jul 17, 2024

@glennmatthews currently running 2.1.1 - will try deploying with v2.2.0 - thanks for the tip.

@jvanderaa jvanderaa merged commit aa06e64 into main Sep 10, 2024
2 checks passed
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.

4 participants