[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ] Richard Achmatowicz commented on WFLY-13433: -------------------------------------------- I'm running into a problem with the LegacyConfigXTestSuite tests, where X=640, 700, 710,  720 and 730. All tests pass, except for X=640 which fails, complaining about missing capabilities. These tests do the following: * start a master HC and slave HC using a given domain.xml file * for each profile p in \{default, ha, full, full-ha} from the domain.xml file: ** start a server using profile p and wait for it to start ** check it has the correct profile name ** check we can connect via HTTP ** clean up the server   An example output from a successful test can be seen in the attachment succssfulLegacyConfigTest for X=700. An example output from the unsuccessful test can be seen in the attachment unSuccssfulLegacyConfigTest for X=640. The strange thing is that for X=640, capabilities are checked when the master and slave start up (and problems with missing capabilities there ultimately cause them to fail to boot); however, capabilities are not checked in the other versions when the master and slave start up. I know this because I added a line in CapabilityRegistry.validateCapabilities() to dump out the registered capabilities. This method is being called in the failing test, but not in the passing tests. This is a mystery to me. [~yersan], [~brian.stansberry] any ideas?   -- This message was sent by Atlassian Jira (v7.13.8#713008)