Details
-
Bug
-
Resolution: Done
-
Minor
-
7.3.0.GA
-
None
-
OpenShift 3.11
template rhpam73-managed.yaml
template runs with 3 Kie server pods and 3 Monitoring console pods
-
CR1
-
https://github.com/jboss-container-images/rhpam-7-openshift-image/pull/266, https://github.com/jboss-container-images/rhpam-7-openshift-image/pull/267, https://github.com/kiegroup/kie-cloud-operator/pull/112, https://github.com/ansibleplaybookbundle/rhpam-apb/pull/55, https://github.com/ansibleplaybookbundle/rhpam-apb/pull/56
-
-
2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19
Description
When new container is created in Business central and user selects newly created container in Deployment units column then exception is thrown, see attachment.
The exception is not thrown every time the container is selected, its intensity decreases over time until it completely disappears.
From this behaviour it seems that requests from Monitoring console reach all 3 Kie server pods. Kie server pods which weren't restarted yet return outdated informations (without newly created container), causing errors in Monitoring console.
