[sonataflow-operator] SonataFlow Operator goes into CrashLoopBackOff when workflow is deployed with cluster platform referenced platform

[jianrongzhang89]

Description of the problem:
The SonataFlow Operator goes into CrashLoopBackOff when workflow is deployed with cluster platform referenced platform.

How reproducible: 100%

Steps to reproduce:

1. Deploy Sonataflow Operator on OCP v4.14.0 using image from local build on the main branch and check that the operator is running.
2. Create two namespaces sonataflow-infra and test.
3. Deploy a sonatafowplatform using the attached yaml file.
   sonataflowplatform.txt
4. Deploy a sonatafowclusterplatform using the attached yaml file.
   sonataflowclusterplatform.txt
5. Deploy the greeting workflow using the attached yaml file in the test namespace.
   greeting.txt
6. Wait until the workflow build is completed.

Actual results: the operator loop goes into CrashLoopBackOff after a few minutes:
oc get pods -n openshift-serverless-logic
NAME READY STATUS RESTARTS AGE
logic-operator-rhel8-controller-manager-64d748755f-792s8 1/2 CrashLoopBackOff 380 (84s ago) 43h

Expected results: The greeting workflow should get deployed normally and the operator pod should continute to run.

It appears to have a stackoverflow, see logs attached. Note that the log level was set to debug

errror.log

[thiagoelg]

Hello @jianrongzhang89!

As @tiagobento mentioned here, the Apache KIE community doesn't have a 1.35 RC release, and the registry-proxy.engineering.redhat.com/rh-osbs/iib:878712 image is not part of our release and is not publicly accessible.

Please ensure this issue is reproducible with the officially released Apache KIE community versions and update this description accordingly.

[jianrongzhang89]

Hello @jianrongzhang89!

As @tiagobento mentioned here, the Apache KIE community doesn't have a 1.35 RC release, and the registry-proxy.engineering.redhat.com/rh-osbs/iib:878712 image is not part of our release and is not publicly accessible.

Please ensure this issue is reproducible with the officially released Apache KIE community versions and update this description accordingly.

@thiagoelg I updated the issue description. Let me know if there is any issue.