The domain test suite for RBAC is consistently failing on SPARC Solaris, as can be seen at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-62-RBAC-QE-testsuite-Solaris-matrix/ Given that all the tests are running against the same domain, the first failure is the most significant and the others are just symptoms of inconsistent test environment. The first failure looks like this: Failed: { "address" => [ ("core-service" => "management"), ("access" => "authorization"), ("role-mapping" => "MainGroupDeployer"), ("include" => "user-MainGroupDeployer") ], "operation" => "remove" } Result: { "outcome" => "failed", "result" => undefined, "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.", "rolled-back" => true, "server-groups" => { "server-group-a" => {"host" => {"master" => {"master-a" => {"response" => { "outcome" => "failed", "rolled-back" => true, "response-headers" => {"process-state" => "restart-required"} }}}}}, "server-group-b" => {"host" => {"slave" => {"slave-b" => {"response" => { "outcome" => "failed", "failure-description" => "JBAS014807: Management resource '[ (\"host\" => \"slave\"), (\"server\" => \"slave-b\"), (\"core-service\" => \"management\"), (\"access\" => \"authorization\"), (\"role-mapping\" => \"MainGroupDeployer\"), (\"include\" => \"user-MainGroupDeployer\") ]' not found", "rolled-back" => true, "result" => undefined }}}}} } } and it happens when tearing down the test environment, as can be seen from the stacktrace: java.lang.AssertionError: JBAS010839: Operation failed or was rolled back on all servers. at org.junit.Assert.fail(Assert.java:88) at org.jboss.as.test.integration.management.rbac.RbacUtil.checkOperationResult(RbacUtil.java:94) at org.jboss.as.test.integration.management.rbac.RbacUtil.executeOperation(RbacUtil.java:79) at org.jboss.as.test.integration.management.rbac.RbacUtil.removeRoleUser(RbacUtil.java:152) at org.jboss.as.test.integration.management.rbac.UserRolesMappingServerSetupTask.tearDown(UserRolesMappingServerSetupTask.java:84) at org.jboss.as.test.integration.domain.rbac.RBACProviderServerGroupScopedRolesTestCase.tearDownDomain(RBACProviderServerGroupScopedRolesTestCase.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) ... The same can be seen at: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-62-RBAC-QE-testsuite-Solaris-matrix/jdk=java16_default,label=sol11_sparc/3/testReport/junit/org.jboss.as.test.integration.domain.rbac/RBACProviderServerGroupScopedRolesTestCase/org_jboss_as_test_integration_domain_rbac_RBACProviderServerGroupScopedRolesTestCase/ More details can be found in the job workspace, specifically in testsuite/domain/target: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-62-RBAC-QE-testsuite-Solaris-matrix/jdk=java16_default,label=sol11_sparc/ws/jboss-eap/testsuite/domain/target/ I'm assigning to myself, as this is most likely a test issue, though it might have something in common with https://issues.jboss.org/browse/WFLY-2270
Just noting that this also happens on Windows from time to time; e.g. at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-62-RBAC-QE-testsuite-Windows-matrix-5/jdk=java16_default,label=Win2k8_x86_64/5/testReport/junit/org.jboss.as.test.integration.domain.rbac/RBACProviderServerGroupScopedRolesTestCase/org_jboss_as_test_integration_domain_rbac_RBACProviderServerGroupScopedRolesTestCase/ Stil no idea what's the cause.
Renaming the issue to point out that: - this is not only failing on Solaris SPARC, but also on Windows - it's a single specific test that is failing I've created a Job to run just this single test: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-62-RBAC-testsuite-Solaris-investigation/ I can only guess that the test is failing in a very slow environment, which might mean that either there is a small timeout somewhere in the test, or that there is some concurrency issue in the code. I wasn't able to reproduce the failure manually yet.
Turns out this was caused by bug 1024072. I reran the test with EAP 6.2.0.ER6, which contains the fix, and it passed. Closing as dupe. *** This bug has been marked as a duplicate of bug 1024072 ***
(Bleh. That was of course ER7. Silly me.)