]
Bartosz Spyrko-Smietanko moved JBEAP-20160 to WFCORE-5121:
----------------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-5121 (was: JBEAP-20160)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Server
(was: Server)
Affects Version/s: (was: 7.3.1.GA)
(was: 7.2.8.GA)
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
------------------------------------------------------------------------------------------------------------------------------
Key: WFCORE-5121
URL:
https://issues.redhat.com/browse/WFCORE-5121
Project: WildFly Core
Issue Type: Bug
Components: Server
Reporter: Bartosz Spyrko-Smietanko
Assignee: Bartosz Spyrko-Smietanko
Priority: Major
Labels: customer, support-case-open
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.>>>
{code:java}
...
[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)
...
{code}
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
{code:java}
[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 /]
{code}
This is a the server group defined in the Host master domain.xml :
{code:java}
<server-groups>
<server-group name="ServerGroup-eap71"
profile="full-ha-eap71">
<socket-binding-group ref="full-ha-eap71-sockets"/>
</server-group>
</server-groups>
{code}
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_ap...]