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

Liveness probe is unable to detect that business central pod is broken

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.0.0.GA
    • 7.0.0.GA
    • None

    • Openshift, Business Central

    • ER5
    • Hide
      1. Run business central in Openshift
      2. Open shell in business central pod (oc rsh business-central-pod-name)
      3. Undeploy business central war using CLI (/opt/eap/bin/jboss-cli.sh -c --command='undeploy ROOT.war')
      4. Pod should be replace by new one but it is not
      Show
      Run business central in Openshift Open shell in business central pod (oc rsh business-central-pod-name) Undeploy business central war using CLI (/opt/eap/bin/jboss-cli.sh -c --command='undeploy ROOT.war') Pod should be replace by new one but it is not

      Liveness probe in business central image is unable to detect crashed business central. It checks only that EAP is working but it is unable to detect that business central application is broken.

      To reproduce this bug run business central in Openshift and manually undeploy war with business central. Then Openshift should replace the pod with business central with new one. However, it does not happen because liveness probe is unable to detect that business central is not running.

              czhu_jira calvin zhu (Inactive)
              jpetrlik@redhat.com Jiri Petrlik
              Jiri Petrlik Jiri Petrlik
              Jiri Petrlik Jiri Petrlik
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: