Closed jdrew82 closed 2 months ago
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.
@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.
@glennmatthews currently running 2.1.1 - will try deploying with v2.2.0 - thanks for the tip.
This PR closes the issue in #66.