Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-869

[EAP6] liveness probe unnecessarily repeats 30 iterations even when the deployment is already failed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP64 1.5.0.GA
    • None
    • EAP6
    • None
    • Hide

      set failureThreshold: 1 on the liveness probe to at least not repeat all the liveness probe iterations 3 times (which is the default openshift value for failureThreshold)

      Show
      set failureThreshold: 1 on the liveness probe to at least not repeat all the liveness probe iterations 3 times (which is the default openshift value for failureThreshold)
    • CLOUD Maintenance Sprint 6

      The liveness probe repeats its check so that it doesn't kill pod when EAP management port is not yet active...

      However it also repeats this cycle when it already knows that the "deployments_failed", which doesn't make sense as the deployment can never fix itself.

      Liveness probe should fail immediately if it already knows that "deployments_failed".

              rcernich1 Rob Cernich
              maschmid@redhat.com Marek Schmidt
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: