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

Remove eap74-tx-recovery-s2i.json

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.4.0.GA
    • 7.4.0.GA.CR1
    • OpenShift
    • None

    Description

      In [1] we have removed documentation about eap74-tx-recovery-s2i.json from 7.4 documentation.

      This issue is about removing also template eap74-tx-recovery-s2i.json for EAP 7.4.

      Do I understand correctly that is what is expected bozpeyni@redhat.comochaloup@redhat.comjmesnil1@redhat.com?

      [1] https://issues.redhat.com/browse/JBEAP-19128

      Attachments

        Issue Links

          causes

          Task - Represents a small unit of work that is not end-user facing. JBEAP-26528 EAP 74 quickstart uses links to nonexisting templates, should be migrated to Helm charts?

          • 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.
          • New
          is incorporated by

          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-3930 EAP 7.4.0.GA OpenShift Image Release

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19128 Remove OpenShift Legacy transaction Recovery approach from documentation

          • 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

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-3252 [Quickstart] jta-crash-rec-eap emit `Unable to acquire JDBC Connection` error

          • 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

          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

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              mchoma@redhat.com Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: