Slaves should report the master's version in the domain model ------------------------------------------------------------- Key: WFCORE-1552 URL: https://issues.jboss.org/browse/WFCORE-1552 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 2.2.0.CR2 Reporter: Kabir Khan Assignee: ehsavoie Hugonnet Setting up the mixed domain tests for an EAP7 slave, I get the following error : {code} SimpleMixedDomain700TestCase>SimpleMixedDomainTest.test00002_Versioning:139 expected:<{ "management-major-version" => 4, "management-micro-version" => 0, "management-minor-version" => 1, "name" => "Unnamed Domain", "namespaces" => [], "product-name" => "WildFly Full", "product-version" => "10.1.0.Final-SNAPSHOT", "release-codename" => "Kenny", "release-version" => "2.2.0.CR2", "schema-locations" => [] }> but was:<{ "management-major-version" => 4, "management-micro-version" => 0, "management-minor-version" => 1, "name" => "Unnamed Domain", "namespaces" => [], "product-name" => "JBoss EAP", "product-version" => "7.0.0.GA", "release-codename" => "Kenny", "release-version" => "2.1.2.Final-redhat-1", "schema-locations" => [] }> {code} The 'expected' is the WildFly master values, while the 'actual' are the slave values. product-name, product-version, release-codename and release-version on the slave should be the same as the master values. Once we upgrade to Wildfly Core 3.0.0 we should also check that the management-[major/minor/micro]-version attributes on the slave are the same as the DC's values as well (i.e 5.0.0 rather than 4.0.1) This is similar to WFLY-3228 back in the day. This is probably caused by the SyncXXX handlers for pushing the domain config as operations (WFCORE-401)