Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-18066

DNS_PING rolling update: Client gets "HTTP 500 error: Internal Server Error"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • 7.3.0.CD18
    • Clustering, OpenShift
    • None

      After enabling tests with fixed JBEAP-17170 (KUBE_PING) test failure popped up in case of DNS_PING. Current ratio is 1:2 in lab.

      Thats the first time I see it failing. DNS_PING variant was created during investigation of JBEAP-17170 and was ignored with KUBE_PING variant because of JBEAP-17170. So it wasn't run many times so far in lab. This one failure occured on OCP3.

      I am attaching test log, matching events and log of pods which are available at the end of test. I dont have available logs of pods with old version of application before rolling update. Could you spot from these resources what the problem could be?

      As far as I can tell, I don't see split brain occurred as in case of JBEAP-17170. And I don't see any exception in pods. That makes me think 500 error occurred on "old" pods.

      I will continue with investigation, but I would be glad for any hints.

        1. com.redhat.xpaas.eap.rolling.RollingUpdatesDnsPingTest
          73 kB
          Martin Choma
        2. DNS_PING.events
          138 kB
          Martin Choma
        3. test.log
          20 kB
          Martin Choma

              rhn-engineering-rhusar Radoslav Husar
              mchoma@redhat.com Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: