wmedvede opened a new issue, #468:
URL: 
https://github.com/apache/incubator-kie-kogito-serverless-operator/issues/468

   ### Describe the bug
   
   1) We create a SPF with persistence configured, and DI and JS enabled that 
use that platform persistence.
   2) We deploy a workflow in that platform and let it use that platform 
persistence.
   3) DI, JS and the workflow starts well, etc.
   
   4) now we change the original SPF persistence configuration to point to 
another DB.
   
   5) DI is restarted and points to the new DB
   6) workflow is restarted and points to the new DB
   
   7) Jobs service is restarted but we have the following situation:
   
   7.1) The deployment has the  QUARKUS_DATASOURCE_JDBC_URL pointing to the new 
DB
   7.2) The sonataflow-platform-jobs-service-props ConfigMap, still has the 
quarkus.datasource.reactive.url pointing to the old DB.
   (It looks like the sonataflow-platform-jobs-service-props ConfigMap is not 
refreshed as part of the SPF change)
   
   So the restart don't well, since same instance points to two different 
databases.
   
   
   
   
   
   ### Expected behavior
   
   All jobs service connections must point to the new DB.
   
   ### Actual behavior
   
   _No response_
   
   ### How to Reproduce?
   
   _No response_
   
   ### Output of `uname -a` or `ver`
   
   _No response_
   
   ### Golang version
   
   _No response_
   
   ### Operator-sdk version
   
   _No response_
   
   ### SonataFlow Operator version or git rev
   
   _No response_
   
   ### Additional information
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to