Details
-
Bug
-
Resolution: Done
-
Critical
-
fuse-7.6-ER1
-
None
Description
The operator periodically detects some change in broker-amq deployment config and it is bringing it up and terminating it right after (as the replicas is set to 0).
After few minutes of running, you can observe:
oc get pods NAME READY STATUS RESTARTS AGE broker-amq-27-deploy 0/1 ContainerCreating 0 2s i-db-to-db-smoke-rest-test-1-build 0/1 Completed 0 2m i-db-to-db-smoke-rest-test-2-lbkwb 1/1 Running 0 50s syndesis-db-1-6rmkr 2/2 Running 0 8m syndesis-meta-1-schbc 1/1 Running 0 8m syndesis-oauthproxy-1-vxxnw 1/1 Running 0 8m syndesis-operator-2-7278v 1/1 Running 0 9m syndesis-prometheus-1-rgdnh 1/1 Running 0 8m syndesis-server-1-8c5qr 1/1 Running 2 8m syndesis-ui-1-dbfkc 1/1 Running 0 8m todo-1-95ghx 1/1 Running 0 7m todo-1-build 0/1 Completed 0 8m
as you can see, in 8 minutes it tried to deploy it 27 times.
currently there is no possibility to scale the broker to 1 - ENTESB-12318
Attachments
Issue Links
- is related to
-
-
- Done
-
