-
Notifications
You must be signed in to change notification settings - Fork 7
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
geonode django container dosn't get database connection #40
Comments
I'm running into a similar situation with
|
hi Brad, I generally fixed this issue for now by deleting and reinitializing the whole deployment. I think it's kind of a race condition while starting the pods. |
still can happen in 1.0.0 |
i think this is related to the database env variable loading in the geonode pod here: combined with the init container only checking if the database is accessable tcp layer. I guess sometimes the geonode pod gets created and load env vars from a secret which isn't final and therefore the geonode pod starts without or with wrong database credentials. I would suggest to edit the init container to actively interact with the postgres container using the postgresql-client |
after deploying the helm chart it sometimes randomly orrures that the geonode container can not find the database or does not have access to it. You see the issue in the geonode container logs like:
if the database is found once it will be found forever but sometimes within the initial deploy its not working
The text was updated successfully, but these errors were encountered: