Openshift Kogito Operator - default process-quarkus-example, crashLoopBackoff

6 views
Skip to first unread message

Graeme Colman

unread,
Apr 7, 2021, 7:24:58 AMApr 7
to Kogito development mailing list
Hi

Not sure if this is the place for user help but I am trying to get the process-quarkus-example working from the OpenShift operator. I'm using the steps in the latest docs and taking the defaults (the quarkus examples repo).  Build is fine, but the runtime does not start crash loop backoff due to the liveness probe failing.

I'm expecting this to work by following the docs, but stumped.

Should this just work? 

Kogito Operator 1.4.0
OpenShift 4.7.4

Thanks for any pointers you can give.
Graeme

2021-04-07 11:13:23,017 WARN [io.qua.config] (main) Unrecognized configuration key "quarkus.infinispan-client.server-list" was provided; it will be ignored 2021-04-07 11:13:23,952 INFO [io.quarkus] (main) process-quarkus-example 8.0.0-SNAPSHOT (powered by Quarkus 1.4.1.Final) started in 1.148s. Listening on: http://0.0.0.0:8080 2021-04-07 11:13:23,952 INFO [io.quarkus] (main) Profile prod activated. 2021-04-07 11:13:23,952 INFO [io.quarkus] (main) Installed features: [cdi, kogito, resteasy, resteasy-jackson, resteasy-jsonb, smallrye-openapi, swagger-ui] 2021-04-07 11:13:52,398 INFO [io.quarkus] (main) process-quarkus-example stopped in 0.029s

Tristan Radisson

unread,
Apr 7, 2021, 7:54:43 AMApr 7
to Kogito development mailing list
Hi Graeme,

You are in the right place to ask for help.

I can see `process-quarkus-example 8.0.0-SNAPSHOT (powered by Quarkus 1.4.1.Final)` into the logs. This seems to be an old version of Kogito (and not a stable one).
Which branch of kogito-examples are you using ? The default latest stable branch of kogito-examples is `stable`. Could you please retry with that branch ?

Regards,

Tristan Radisson

Senior Software Quality Engineer

Business Automation Cloud

Red Hat France

trad...@redhat.com   




--
You received this message because you are subscribed to the Google Groups "Kogito development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kogito-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kogito-development/b2ce1330-8b03-40db-9324-378642ec842dn%40googlegroups.com.

mma...@redhat.com

unread,
Apr 7, 2021, 8:07:16 AMApr 7
to kogito-de...@googlegroups.com
Hi Graeme,

Tristan is right. There was a change in the healthcheck subsystem on Quarkus some time ago and you are probably mixing old Kogito example with new Operator, so Operator configures liveness probe for endpoint which doesn't exist (yet in that old version) on the Kogito Quarkus example.

Marian

Graeme Colman

unread,
Apr 7, 2021, 9:13:07 AMApr 7
to kogito-de...@googlegroups.com
Thanks Tristan/Miriam

Just running with the stable branch, but the build is taking a very long time. As though it's doing a native build. Will update when it's finished!

Graeme


Generating dockerfile with builder image image-registry.openshift-image-registry.svc:5000/gctemp/kogito-builder@sha256:b14c090ad0d6d43e6eef609ee8a7f5b95262c97db0d2e91afbd30be7f2401476
Adding transient rw bind mount for /run/secrets/rhsm
STEP 1: FROM image-registry.openshift-image-registry.svc:5000/gctemp/kogito-builder@sha256:b14c090ad0d6d43e6eef609ee8a7f5b95262c97db0d2e91afbd30be7f2401476
STEP 2: LABEL "io.openshift.build.commit.id"="b4c398cf8130c1f899a7e7103a2e5c477dca5bd0"       "io.openshift.build.commit.message"="Merge pull request #621 from bsig-gh-bot/1.4.1.Final-nkfihfbeo1"       "io.openshift.s2i.destination"="/tmp"       "io.openshift.build.image"="image-registry.openshift-image-registry.svc:5000/gctemp/kogito-builder@sha256:b14c090ad0d6d43e6eef609ee8a7f5b95262c97db0d2e91afbd30be7f2401476"       "io.openshift.build.commit.author"="Jenkins CI <jen...@rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com>"       "io.openshift.build.commit.date"="Mon Mar 22 05:05:36 2021 -0400"       "io.openshift.build.commit.ref"="stable"       "io.openshift.build.source-location"="https://github.com/kiegroup/kogito-examples"       "io.openshift.build.source-context-dir"="process-quarkus-example"
STEP 3: ENV OPENSHIFT_BUILD_NAME="example-quarkus-builder-1"     OPENSHIFT_BUILD_NAMESPACE="gctemp"     OPENSHIFT_BUILD_SOURCE="https://github.com/kiegroup/kogito-examples"     OPENSHIFT_BUILD_REFERENCE="stable"     OPENSHIFT_BUILD_COMMIT="b4c398cf8130c1f899a7e7103a2e5c477dca5bd0"     RUNTIME_TYPE="quarkus"     NATIVE="false"     LIMIT_CPU=""     LIMIT_MEMORY=""
STEP 4: USER root
STEP 5: COPY upload/src /tmp/src
STEP 6: RUN chown -R 1001:0 /tmp/src
STEP 7: USER 1001
STEP 8: RUN /usr/local/s2i/assemble
INFO ---> Setting RUNTIME_TYPE to quarkus
INFO ----> RUNTIME_TYPE has been set to quarkus
 [0;33mWARN Provided memory () limit is not valid, native build will use all available memory [0m
INFO ---> Building application from source...
[INFO] Scanning for projects...
[INFO] 
[INFO] ----------< org.kie.kogito.examples:process-quarkus-example >-----------
[INFO] Building Kogito Example :: Process and Quarkus 1.4.1.Final
[INFO] --------------------------------[ jar ]---------------------------------


Graeme Colman
UKI Domain Solution Architect & Developer Advocacy Lead
Red Hat UK Ltd, 200 Fowler Avenue, Farnborough, Hampshire, GU14 7JP



You received this message because you are subscribed to a topic in the Google Groups "Kogito development mailing list" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kogito-development/c0bN5I7FqsE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kogito-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kogito-development/d9015d326e1859ff73bdbed18398c20b023c8ea0.camel%40redhat.com.

Graeme Colman

unread,
Apr 7, 2021, 5:53:13 PMApr 7
to kogito-de...@googlegroups.com
Trying again, the default branch on the example repo (https://github.com/kiegroup/kogito-examples) is the stable branch. I have tried setting the branch to stable with the same results. 

The log is the same version:
2021-04-07 21:19:29,158 INFO  [io.quarkus] (main) process-quarkus-example 8.0.0-SNAPSHOT (powered by Quarkus 1.4.1.Final) started in 1.355s. Listening on: http://0.0.0.0:8080

The setting for the repo is as default:
image.png

The Kogito Operator runtime probe fails with:

image.png

I am just trying to get the absolute minimum running on OpenShift using the default settings throughout.

Really appreciate your help!
Graeme



Graeme Colman
UKI Domain Solution Architect & Developer Advocacy Lead
Red Hat UK Ltd, 200 Fowler Avenue, Farnborough, Hampshire, GU14 7JP


Tristan Radisson

unread,
Apr 8, 2021, 6:30:15 AMApr 8
to Kogito development mailing list
Hi Graeme,

I think the problem is with the KogitoRuntime creation in the web console.
The problem when using the OCP console and creating a KogitoRuntime is that the `image` field has a default value to `quay.io/kiegroup/process-quarkus-example`, which is a very old image ...
We need to correct that and remove the default value (I created https://issues.redhat.com/browse/KOGITO-4894 to correct that).

If you want to reuse the KogitoBuild you created, the KogitoRuntime CR should have the exact same name as the KogitoBuild (default is `example-quarkus` if you did not change it) and the `image` field should be empty (remove the default value). It will then take directly the image built in the KogitoBuild.
The logs should then be something like:

2021-04-08 10:21:18,198 INFO [io.quarkus] (main) process-quarkus-example 1.4.1.Final on JVM (powered by Quarkus 1.11.5.Final) started in 10.232s. Listening on: http://0.0.0.0:8080

Tristan Radisson

Senior Software Quality Engineer

Business Automation Cloud

Red Hat France

trad...@redhat.com   



Graeme Colman

unread,
Apr 8, 2021, 6:39:56 AMApr 8
to kogito-de...@googlegroups.com
Awesome, thank you Tristan!

That worked, thanks.

Graeme.



Graeme Colman
UKI Domain Solution Architect & Developer Advocacy Lead
Red Hat UK Ltd, 200 Fowler Avenue, Farnborough, Hampshire, GU14 7JP


Reply all
Reply to author
Forward
0 new messages