wmedvede opened a new issue, #561: URL: https://github.com/apache/incubator-kie-kogito-serverless-operator/issues/561
### Describe the bug Given an installation, for example when the operator 1.33.0 is upgraded to 1.34.0, the following situation is produced: If we have deployed workflow with the preview profile, that was built, in 1.33.0, when the operator is upgraded too 1.34.0, we have that the workflow will continue running as is. In a later point in time, if a re-build of the workflow is produced, for whatever reason, we have that the new build is started, this time with the builder image 1.34.0, but, preserving the initial build generated in 1.33.0. We must analyse if this is bug, or if we need adjustments. Possible alternatives. 1) since the workflow was generated with 1.33.0, unless the user voluntary deletes, and re-deploy the workflow, potential new re-builds must be produced with the sonataflowbuild produced in 1.33.0 and the builder image for 1.33.0. 2) when a new re-build of the workflow is produced in 1.34.0, the operator must not only use the builder image 1.34.0 but also re-generate the sonataflowbuild in 1.34.0 before executing the build. 3) any other alternative. (maybe the sonataflowbuild shouldn't save the added QUARKUS_EXTENSIONS as part of it.) Alternatives above must consider that the sonataflowbuid is keeping the information of the QUARKUS_EXTENSIONS potentially added for a particular build, and here is one point of discussion and where a problem might be introduced. Specially for the automatically added persistence related extensions. ### Expected behavior _No response_ ### 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]
