pgr-services goes into a crashloop due to improper db migration scripts, not able to create businessService configuration for PGR #819
Unanswered
shashwat-egov
asked this question in
Q&A
Replies: 2 comments 1 reply
-
@shashwat-egov This is expected behaviour, we have already mentioned this in the document that initially the PGR-service will be in crash loop, you should run the post deployment scripts. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Update: This issue has been escalated to the urban team and will be fixed soon. Also, we should have a separate configs branch for quickstart too so that the queries that are getting executed and db tables do not go out of sync. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Upon checking pgr-services logs,
The pod is not able to find businessService config of PGR which is causing it to go into a crashloop.
Upon checking the persister service ( asynchronously inserts data into the database ) logs,
Seems like the db migration scripts are not in sync with the INSERT query that is getting executed to persist data onto the db. Adding this missing migration script ought to solve the issue - https://github.com/egovernments/DIGIT-Dev/blob/develop/core-services/egov-workflow-v2/src/main/resources/db/migration/main/V20210423102936__wf_alter_table_active_ddl.sql
Beta Was this translation helpful? Give feedback.
All reactions