-
Bug
-
Resolution: Done
-
Major
-
0.9.0
-
None
When deploy a new Kogito App, for example:
apiVersion: app.kiegroup.org/v1alpha1
kind: KogitoApp
metadata:
name: payroll
spec:
build:
gitSource:
contextDir: onboarding-example/payroll
uri: 'https://github.com/kiegroup/kogito-examples'
imageVersion: 0.9.0-rc2
native: true
resources:
requests:
memory: 4Gi
replicas: 1
runtime: quarkus
service:
labels:
payments/date: process
taxes/rate: process
vacations/days: process
Randomly, two Builder are triggered at almost the same time, see status of the KogitoApp with the following information:
apiVersion: app.kiegroup.org/v1alpha1
kind: KogitoApp
metadata:
generation: 4
name: payroll
status:
builds:
new:
- payroll-builder-2
running:
- payroll-builder-1
conditions:
- lastTransitionTime: '2020-04-08T10:41:05Z'
status: 'True'
type: Provisioning
deployments: {}
Looking into each Builder, the first is triggered by:
triggeredBy:
- message: Image change
imageChangeBuild:
imageID: >-
image-registry.openshift-image-registry.svc:5000/cucumber-tezz/kogito-quarkus-ubi8-s2i@sha256:729e158710dedba50a49943ba188d8f31d09568634896de9b903838fc4e34e94
fromRef:
kind: ImageStreamTag
namespace: cucumber-tezz
name: 'kogito-quarkus-ubi8-s2i:0.9.0-rc2'
And the second only says:
triggeredBy:
- message: Triggered by payroll operator
- is related to
-
KOGITO-1999 Separate build tasks on Kogito Operator to a new CR
-
- Resolved
-
-
KOGITO-2019 When a build is running and the configuration has changed, we should start a new build any way
-
- Resolved
-