Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-2008

HTTP 503 error is shown in Monitoring console when Kie server is scaled to 0

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 7.4.0.GA
    • 7.3.0.GA
    • Business Central, Cloud
    • None

    • OpenShift 3.11
      rhpam73-managed.yaml template

    • 2019 Week 20-22

    Description

      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.

      Attachments

        Issue Links

          is incorporated by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBPM-8150 Allow users to change Kie server id in Deployment config and templates

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

          Bug - A problem that impairs or prevents the functions of the product. KIECLOUD-172 Monitoring console problems in rhpam-production-immutable environment

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-2634 Remote Server is lot from the controller after Kie Server scale down and scale up

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-2657 KieServer Scale-Up-From-Zero lifecycle hooks logic broken at (7.7)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) RHPAM-2175 Adding a system account for connecting to Workbench internal REST/API

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              evan.zhang@redhat.com Evan Zhang (Inactive)
              ksuta Karel Suta
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: