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

Legacy slaves can't understand new enum version values

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.1.0.CR2
    • 7.1.0.CR1
    • Management
    • None
    • Not Required
    • Hide

      See attached configs. Mgmt user is eap70-host password: password
      1. Start EAP7.1 DC with attached domain.xml (download it to jboss-eap-7.1/domain/configuration).

      ./jboss-eap-7.1/bin/domain.sh -b 127.0.0.1 -bmanagement 127.0.0.1

      2. Start EAP7.0 HC with attached host-slave.xml (download it to jboss-eap-7.0/domain/configuration and fix server group name, it should be eap70-main-server-group instead of eap-70-main-server-group"), pointing it to discover the already started up DC bound to loopback.

      ./jboss-eap-7.0/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -b <NON_LOOPBACK_IP_ADDR> -bmanagement <NON_LOOPBACK_IP_ADDR>
      Show
      See attached configs. Mgmt user is eap70-host password: password 1. Start EAP7.1 DC with attached domain.xml (download it to jboss-eap-7.1/domain/configuration ). ./jboss-eap-7.1/bin/domain.sh -b 127.0.0.1 -bmanagement 127.0.0.1 2. Start EAP7.0 HC with attached host-slave.xml (download it to jboss-eap-7.0/domain/configuration and fix server group name, it should be eap70-main-server-group instead of eap-70-main-server-group" ), pointing it to discover the already started up DC bound to loopback. ./jboss-eap-7.0/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -b <NON_LOOPBACK_IP_ADDR> -bmanagement <NON_LOOPBACK_IP_ADDR>

    Description

      [Host Controller] 10:53:50,342 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 2) WFLYCTL0013: Operation ("add") failed - address: ([("host-exclude" => "EAP70")]) - failure description: "WFLYCTL0248: Invalid value EAP7.0 for host-release; legal values are [EAP6.3, EAP6.2, WildFly10.0, EAP6.4]"
      [Host Controller] 10:53:50,366 ERROR [org.jboss.as.host.controller] (Host Controller Service Threads - 2) WFLYHC0143: Failed to apply domain-wide configuration from master host controller. Operation outcome: failed. Failure description {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0248: Invalid value EAP7.0 for host-release; legal values are [EAP6.3, EAP6.2, WildFly10.0, EAP6.4]"}}
      [Host Controller] 10:53:50,448 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0001: Could not connect to remote domain controller remote://192.168.122.71:9999 – 1-$-
      [Host Controller] 10:53:50,449 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0147: No domain controller discovery options remain.
      [Host Controller] 10:53:50,451 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0002: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: WFLYHC0120: Tried all domain controller discovery option(s) but unable to connect

      Attachments

        1. domain.xml
          130 kB
        2. host-slave.xml
          4 kB

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-3226 Legacy slaves can't understand new enum version values

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

          Bug - A problem that impairs or prevents the functions of the product. WFLY-9307 Update testsuite to use EAP70 enum values and not just api versions

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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-12949 (7.1.0) Upgrade to WildFly Core to 3.0.3.Final-redhat

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-13392 Update testsuite to use EAP70 enum values and not just api versions

          • 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

          Activity

            People

              kwills@redhat.com Ken Wills
              kwills@redhat.com Ken Wills
              Martin Simka Martin Simka
              Martin Simka Martin Simka
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: