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

[EAP][XA] jta-crash-rec-eap7 quickstart doesn't work with sprint-21 img

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • None
    • None
    • EAP7
    • CLOUD Maintenance Sprint 22

    Description

      jta-crash-rec-eap7 doesn't work correctly with jboss-eap-7/eap71-openshift:1.4-5 image.
      Steps to work with QS are described in doc .

      Doing scale down after starting second transaction leads to recovery in migration pod (which looks ok) but bringing back the app with scale up leads to empty table (looks like even the first record didn't survive the scale down) .

      It works OK for me with previous jboss-eap-7/eap71-openshift:1.3. Maybe I am missing something....

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-2761 [EAP][Recovery] Migration pod starts with permission errors in log

          • 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

          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) CLOUD-2795 [EAP][XA] jta-crash-rec-eap quickstarts needs to use proper messaging and database datasource

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-2766 [EAP][Templates] eap71-tx-recovery-s2i template params don't make sense

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

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-2261 [EAP][XA][Recovery][NFS] split lock is broken after a minute of network partition

          • 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

          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) CLOUD-2768 [EAP][XA] merge jta-crash-rec-eap quickstarts and update README

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

          Activity

            People

              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              tremes1@redhat.com Tomas Remes
              Tomas Remes Tomas Remes
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: