Closed itheodoridis closed 2 months ago
This is a known issue with Celery or Beats starting before the database schema has been fully created. You can safely ignore it and fix it by allowing the nautobot container to finish the migrations and then restart all the containers. This should hopefully be less of an issue with some of the healthchecks that are in the compose files now.
Postgress and Celery beat service produce errors in log during the first deployment (when no db exists already). Postgress complains for some relations that don't exist at specific character locations, e.g. :
Celery beat is producing python errors in the log, its quite possible that the two issues are connected.
None of those are repeated if the db exists already when creating the containers again (e.g. if we don't delete volumes between tests).