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

EJB Transaction recovery tests failing with EAP Operator 2.1 for EAP 7.3 images only

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • OP-2.2.0.GA
    • OP-2.1.0.GA
    • OpenShift
    • None
    • False
    • False
    • Undefined
    • Hide
      1. I prepared easy to use branch + pre-provisioned clusters for testing this, please reach out if they stop working 
        git clone --single-branch --branch=testing-operator-ejb-txn-regression https://gitlab.hosts.mwqe.eng.bos.redhat.com/jbliznak/openshift-eap-tests.git
cd openshift-eap-tests
      2. execution against cluster with Operator 2.0 
        mvn clean test -Poperator -Dtest=EjbTxnRemotingScaleDownTest#testTxStatelessClientSecondCommitThrowRmErrBlockScaleDown -Dxtf.test_properties.path=test.properties_remote_op20 -P73
      3. execution against cluster with Operator 2.1 
        mvn clean test -Poperator -Dtest=EjbTxnRemotingScaleDownTest#testTxStatelessClientSecondCommitThrowRmErrBlockScaleDown -Dxtf.test_properties.path=test.properties_remote_op21 -P73
      Show
      I prepared easy to use branch + pre-provisioned clusters for testing this, please reach out if they stop working git clone --single-branch --branch=testing- operator -ejb-txn-regression https: //gitlab.hosts.mwqe.eng.bos.redhat.com/jbliznak/openshift-eap-tests.git cd openshift-eap-tests execution against cluster with Operator 2.0 mvn clean test -Poperator -Dtest=EjbTxnRemotingScaleDownTest#testTxStatelessClientSecondCommitThrowRmErrBlockScaleDown -Dxtf.test_properties.path=test.properties_remote_op20 -P73 execution against cluster with Operator 2.1 mvn clean test -Poperator -Dtest=EjbTxnRemotingScaleDownTest#testTxStatelessClientSecondCommitThrowRmErrBlockScaleDown -Dxtf.test_properties.path=test.properties_remote_op21 -P73

    Description

      After the recent update to EAP Operator 2.1, we discovered that tests for EAP7-1192 started to fail regularly. (https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-eap/openshift-eap-tests/-/blob/master/test-eap/src/test/java/com/redhat/xpaas/eap/xa/EjbTxnRemotingScaleDownTest.java)

      The strange thing is that it is failing only with EAP 7.3 images, eg.:

       registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-openjdk8-openshift-rhel7:7.3.4-7
 registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-openjdk8-openshift-rhel7:7.3.5-1

      It works fine with CD21 images.

      There are multiple test failures and quite frankly these are quite complex so it isn't easy to say what is wrong. For example, we have test that is doing transaction recovery on scaledown an it is now failing on checking presence of /opt/eap/standalone/data/MockXAResource after recovery (should not be there but it is)

      When trying to pinpoint when that happens I tried these images:

       registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-rhel8-operator:2.1-1 (based on 0.4.1 tag + only prometheus changes) - fail
 registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-rhel8-operator:2.1-2 (based on 0.4.1 tag + only bootable jar changes) - pass
 registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-rhel8-operator:2.1-3 (based on 0.4.1 tag + only bootable jar changes) - pass
 registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-rhel8-operator:2.1-4 (based on 0.4.1 tag + only bootable jar changes) - pass 
 registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-rhel8-operator:2.1-5 (based on 0.4.1 tag + only bootable jar changes) - pass 
 registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-rhel8-operator:2.1-6 (based on 0.4.1 tag + only bootable jar changes?) - fail 
 registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-rhel8-operator:2.1-7 (based on 0.5.0 tag + all changes) - fail
 ... and any version after that - fail

      So that led me to the idea that either EAP-1579 changes or one of the additional commits in https://github.com/wildfly/wildfly-operator/compare/0.4.0...0.5.0 led to this.

      Attachments

        1. operator-pod-op2.0-12.log
          281 kB
        2. operator-pod-op2.1-1.log
          118 kB
        3. operator-pod-op2.1-2.log
          98 kB
        4. operator-pod-op2.1-4.log
          95 kB
        5. operator-pod-op2.1-5.log
          91 kB
        6. operator-pod-op2.1-6.log
          91 kB
        7. operator-pod-op2.1-7.log
          116 kB

        Issue Links

          is related to

          Requirement - Used for conducting internal reviews of our products and process with 3rd party auditors JBEAP-20714 Transaction recovery can not work in the context of Bootable Jar

          • Critical - To be worked on immediately following BLOCKER issues.
          • New
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-17951 Operator error logs on scale down

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

          Bug - A problem that impairs or prevents the functions of the product. WFTC-90 WFTC should not throw NPE when transaction creation is disabled

          • 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.
          • Resolved

          Activity

            People

              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              jbliznak@redhat.com Jan Blizňák
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: