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

[GSS](7.3.z) WFCORE-5121 - Unable to add a new server in a server-group of older EAP 7 host controller that is managed by a newer EAP 7 Domain Controller

    XMLWordPrintable

Details

    • +
    • Hide

      a workaround right now is to add the server manually by editing the host*.xml file and adding the server under the servers section, then start the host as usual:

      <host name="SlaveEAP71" xmlns="urn:jboss:domain:5.0">
...
    <servers>
        <server name="SlaveJvm-EAP71" group="ServerGroup-eap71"/>
    </servers>
...
</host>

      After adding at least one server manually in your host*.xml, then you will be able to use the CLI (or Admin GUI Console) operation to add more servers:

      [domain@xx.xx.xx.xx:9990 /] /host=SlaveEAP71/server-config=SlaveJvm-EAP72:add(group=ServerGroup-eap71)
{
    "outcome" => "success",
    "result" => undefined,
    "server-groups" => undefined
}
      Show
      a workaround right now is to add the server manually by editing the host*.xml file and adding the server under the servers section, then start the host as usual: <host name= "SlaveEAP71" xmlns= "urn:jboss:domain:5.0" > ... <servers> <server name= "SlaveJvm-EAP71" group= "ServerGroup-eap71" /> </servers> ... </host> After adding at least one server manually in your host*.xml, then you will be able to use the CLI (or Admin GUI Console) operation to add more servers: [domain@xx.xx.xx.xx:9990 /] /host=SlaveEAP71/server-config=SlaveJvm-EAP72:add(group=ServerGroup-eap71) { "outcome" => "success" , "result" => undefined, "server-groups" => undefined }
    • Hide
      • Follow EAP 7.3 documentation and configure a JBoss EAP 7.3.1 Domain Controller to Administer a JBoss EAP 7.1.6 Host Controller.

      An example profile="full-ha-eap71" (as renamed from the "full-ha" profile) can be copied from the EAP 7.1.6 domain.xml and added into EAP 7.3.1 domain.xml, as well as a "full-ha-eap71-sockets" socket-binding-group, and a defined custom server group ("ServerGroup-eap71" with empty assigned servers)

      • Have the EAP 7.3 master host DC and EAP 7.1.6 host slave started
      • Try to add a new server in the server-group with profile copied from the older EAP 7.1.6 host. This will not work and the following error always comes up on CLI started on the EAP 7.3.1 Domain Controller
      [domain@xx.xx.xx.xx:9990 /] /host=SlaveEAP71/server-config=SlaveJvm-EAP71:add(group=ServerGroup-eap71)
{
 "outcome" => "failed",
 "result" => {},
 "failure-description" => {"host-failure-descriptions" => {"SlaveEAP71" => "WFLYHC0201: Error synchronizing the host model with the domain controller model with failure : WFLYDC0075: Cannot synchronize the model due to missing extensions: [org.wildfly.extension.microprofile.opentracing-smallrye, org.wildfly.extension.microprofile.config-smallrye, org.wildfly.extension.ee-security]."}},
 "rolled-back" => true
}

[domain@xx.xx.xx.xx:9990 /]
      Show
      Follow EAP 7.3 documentation and configure a JBoss EAP 7.3.1 Domain Controller to Administer a JBoss EAP 7.1.6 Host Controller. An example profile="full-ha-eap71" (as renamed from the "full-ha" profile) can be copied from the EAP 7.1.6 domain.xml and added into EAP 7.3.1 domain.xml, as well as a "full-ha-eap71-sockets" socket-binding-group, and a defined custom server group ("ServerGroup-eap71" with empty assigned servers) Have the EAP 7.3 master host DC and EAP 7.1.6 host slave started Try to add a new server in the server-group with profile copied from the older EAP 7.1.6 host. This will not work and the following error always comes up on CLI started on the EAP 7.3.1 Domain Controller [domain@xx.xx.xx.xx:9990 /] /host=SlaveEAP71/server-config=SlaveJvm-EAP71:add(group=ServerGroup-eap71) { "outcome" => "failed" , "result" => {}, "failure-description" => { "host-failure-descriptions" => { "SlaveEAP71" => "WFLYHC0201: Error synchronizing the host model with the domain controller model with failure : WFLYDC0075: Cannot synchronize the model due to missing extensions: [org.wildfly.extension.microprofile.opentracing-smallrye, org.wildfly.extension.microprofile.config-smallrye, org.wildfly.extension.ee-security]." }}, "rolled-back" => true } [domain@xx.xx.xx.xx:9990 /]

    Description

      I followed EAP 7.2 documentation [1]  and have successfully configured a JBoss EAP 7.2.8 Domain Controller to Administer a JBoss EAP 7.1.6 Host Controller.

      I have followed all the steps listed in there and believe the configuration is OK. Both the master DC and host slave hosts started fine.

      The remote slave host "SlaveEAP71" registered successfully into the EAP 7.2.8 DC

      Cf.>>>

      ...

[Host Controller] 20:34:54,387 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.2.8.GA (WildFly Core 6.0.27.Final-redhat-00001) (Host Controller) started in 6162ms - Started 81 of 83 services (23 services are lazy, passive or on-demand)

... 
[Host Controller] 20:35:12,457 INFO [org.jboss.as.domain.controller] (Host Controller Service Threads - 9) WFLYHC0019: Registered remote slave host "SlaveEAP71", JBoss JBoss EAP 7.1.6.GA (WildFly 3.0.21.Final-redhat-00001)

 ...

       

      However, when trying to add a new server in a server-group with profile copied from the older EAP 7.1.6 host , I'm not able to have this working. The following error always comes up on CLI started on EAP 7.2.8 Domain Controller

      [domain@10.44.130.73:9990 /] /host=SlaveEAP71/server-config=SlaveJvm-EAP71:add(group=ServerGroup-eap71)
{
 "outcome" => "failed",
 "result" => {},
 "failure-description" => {"host-failure-descriptions" => {"SlaveEAP71" => "WFLYHC0201: Error synchronizing the host model with the domain controller model with failure : WFLYDC0075: Cannot synchronize the model due to missing extensions: [org.wildfly.extension.microprofile.opentracing-smallrye, org.wildfly.extension.microprofile.config-smallrye, org.wildfly.extension.ee-security]."}},
 "rolled-back" => true
}

[domain@10.44.130.73:9990 /]

       

      This is a the server group defined in the Host master domain.xml :

      <server-groups>
    <server-group name="ServerGroup-eap71" profile="full-ha-eap71">
        <socket-binding-group ref="full-ha-eap71-sockets"/>
     </server-group>
 </server-groups>

       

      The profile="full-ha-eap71" is copied from the EAP 7.1.6 domain.xml and added into EAP 7.2.8 domain.xml, as well as the "full-ha-eap71-sockets" socket-binding-group.

       

      NOTE: The same issue does also happen with EAP 7.3.1 running as master host DC and EAP 7.1.6 as host slave.

       

      [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.2/html-single/configuration_guide/index#configure_eap71_administer_eap70

       

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-5121 Unable to add a new server in a server-group of older EAP 7 host controller that is managed by a newer EAP 7 Domain Controller

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

          Web Link KB Solution

          Activity

            People

              spyrkob Bartosz Spyrko-Smietanko
              rhn-support-igueye Issa Gueye
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: