wmedvede commented on PR #467: URL: https://github.com/apache/incubator-kie-kogito-serverless-operator/pull/467#issuecomment-2332103563
> Guys, @jianrongzhang89 @ricardozanini > > I have executed most of the use cases in https://github.com/flows-examples/techpreview2/tree/0ac3f5285fac169bafa0ae84661e6c608e88283c/platforms/data_index_and_jobservice_as_platform_service_postgresql_persistence_knative_eventing > > and in general I'd say that most of issues are fixed and working. Great job @jianrongzhang89! > > However, I have identified the following situation that looks not good, specially considering that this is probably one of the most frequent setups to use by Parodos. > > **Full executable usecase here**: > > https://github.com/flows-examples/techpreview2/tree/main/platforms/data_index_and_jobservice_as_platform_service_postgresql_persistence_knative_eventing/case5 > > **Summarized usecase**: > > 1. Broker is configured in SPF and deployed in namespace `case5-kn-eventing` > 2. We configure also a SFCP that points to the SPF in 1 > 3. We deploy WF `callbackstatetimeouts` in a different namespace `case5-kn-eventing-workflows`. The WF takes the Broker config from the SFCP as expected > 4. We deploy WF `callbackstatetimeouts2`in namespace `case5-kn-eventing`. The WF takes the Broker config from the SFP as expected > 5. DI, JS, and both workflows works fine, all Triggers, SBs, etc are created. Events are produced well. > > After some time, we try to delete the WFs created before. > > 1. We execute `kubectl delete workflow callbackstatetimeouts2 -n case5-kn-eventing` > Deletion is produced as expected, associated Triggers and SBs are also deleted as expected. > 2. We execute `kubectl delete workflow callbackstatetimeouts -n case5-kn-eventing-workflows` > This time the deletion never finishes. > Basically looks to get stuck. > > We can query the current workflows and see it all the time. > > kubectl get workflows -n case5-kn-eventing-workflows > > NAME PROFILE VERSION URL READY REASON callbackstatetimeouts preview 0.0.1 True > > 3. The controller log attached here: > https://gist.github.com/wmedvede/6da7d3fb3fb9f213ed62c9dbe2609a28 > > @jianrongzhang89 Would you mind try to reproduce? @jakubschwan @domhanak Would you mind guys double check this execution so see if you get same results. Thanks! -- 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]
