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

Can't run multiple server during migration

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Blocker
    • None
    • 7.3.0.GA
    • OpenShift
    • None
    • CR2

    Description

      During migration the server running in the migration pod can be started multiple time. Each time it attempts to configure the server.
      It was not an issue when sed was used to configure the server, now that we are using CLI, CLI script can't be run multiple time.
      So the migration pod server must be configured once before entering the migration loop.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18533 Migration pod fails to start due to clustering.jgroups.channel.ee: java.lang.IllegalStateException

          • 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.
          • Verified
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18395 openshift-migrate.sh script fails on eap73-openjdk8-openshift-rhel7 due to missing /opt/eap/bin/launch/configure.sh

          • 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.
          • Verified
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-3471 Can't run multiple server during migration

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

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-3520 Can't configure multiple server during migration

          • 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

              jdenise@redhat.com Jean Francois Denise
              jdenise@redhat.com Jean Francois Denise
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: