-
Bug
-
Resolution: Done
-
Minor
-
7.3.0.GA
-
None
-
OpenShift 3.11
rhpam73-managed.yaml template
-
CR2
-
-
-
-
-
-
CR2
-
https://github.com/kiegroup/kie-cloud-operator/pull/185, https://github.com/jboss-container-images/rhpam-7-openshift-image/pull/307, https://github.com/jboss-container-images/jboss-kie-modules/pull/251, https://github.com/kiegroup/droolsjbpm-integration/pull/1827, https://github.com/kiegroup/droolsjbpm-integration/pull/1809, https://github.com/kiegroup/droolsjbpm-integration/pull/1807, https://github.com/jboss-container-images/jboss-kie-modules/pull/262, https://github.com/jboss-container-images/jboss-kie-modules/pull/267
-
-
2019 Week 20-22
Monitoring console shows HTTP 503 error message (see screenshot) when no Kie server pods are available.
The issue can be reproduced by deploying rhpam73-managed.yaml template, waiting for all the pods to start and then scaling Kie server pods to 0. Then if user opens Process instances view the error message is shown.
The expected behaviour is that no error is shown and process instance list is empty, or possibly an information with Kie server unavailability is shown.
- is incorporated by
-
JBPM-8150 Allow users to change Kie server id in Deployment config and templates
- Resolved
- is related to
-
KIECLOUD-172 Monitoring console problems in rhpam-production-immutable environment
- Closed
-
RHPAM-2634 Remote Server is lot from the controller after Kie Server scale down and scale up
- Closed
-
RHPAM-2657 KieServer Scale-Up-From-Zero lifecycle hooks logic broken at (7.7)
- Closed
-
RHPAM-2175 Adding a system account for connecting to Workbench internal REST/API
- Closed
- mentioned on