You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you so much John for this configuration for k8s deployment, It makes everyone job easy who wants to use k8s for chirpstack :)
I have been using your configuration for chirpstack deployment and now I am trying to use this to deploy the latest version of images like for app server 3.15 to deploy fresh on a new cluster.(not upgrade for old)
I am using external Postgres DB not the container-based and created a different user(not chirspstack_as) so my DSN in configmap is something like this
But now the application pod is failing with the following error
time="2021-06-25T08:49:01.84746091Z" level=fatal msg="setup storage error: storage: migrate up error: Dirty database version 27. Fix and force version."
I see there is a table called schema_migrations in application_server DB which have created the one record
Not sure if I am doing anything wrong here or we need any changes in our config to support the 3.15 version of the app server.
Can you please point me if I am doing anything wrong here?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Thank you so much John for this configuration for k8s deployment, It makes everyone job easy who wants to use k8s for chirpstack :)
I have been using your configuration for chirpstack deployment and now I am trying to use this to deploy the latest version of images like for app server 3.15 to deploy fresh on a new cluster.(not upgrade for old)
I am using external Postgres DB not the container-based and created a different user(not chirspstack_as) so my DSN in configmap is something like this
dsn="postgres:https://my_user:[email protected]:5432/devnsdatabse?sslmode=disable&search_path=devnsschema"
But now the application pod is failing with the following error
time="2021-06-25T08:49:01.84746091Z" level=fatal msg="setup storage error: storage: migrate up error: Dirty database version 27. Fix and force version."
I see there is a table called schema_migrations in application_server DB which have created the one record
Not sure if I am doing anything wrong here or we need any changes in our config to support the 3.15 version of the app server.
Can you please point me if I am doing anything wrong here?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions