+++ This bug was initially created as a clone of Bug #859512 +++ Description of problem: :whoami operation not available for managed servers because the security context is not established by AS7. This operation is used by the plugin to detect the server state (need restart or reload). The error is harmless but the plugin should attempt a different operation if this operation fails. How reproducible: Everytime for AS7 managed servers in a domain configuration. Steps to Reproduce: 1. Start AS7 in domain mode. 2. Inventory a host controllers with managed servers active. 3. Execute an operation on one of the managed servers resources. Actual results: Operations succeeds but the the warning (shown below) is visible in the logs. Expected results: Operations succeeds, a warning is visible in the logs but plugin sends a second followup operation is sent to the AS7 server to check for the current status. Additional info: The operation to be executed in case :whoami fails is :read-resource. This operation is slower because the amount of data to be transferred from the server but it's safer since every single resource has it. This second operation is to be executed only if the first one fails. Here is the full text of the error printed in the logs: WARN 21-09 10:40:31,654 (ASConnection.java:executeRaw:229) -Received 500 (Internal Server Error) response to Operation{operation='whoami', address=Address{path: profile=full,subsystem=infinispan,cache-container=hibernate}, additionalProperties={}} - response body was [{"outcome" : "failed", "result" : {"identity" : {"username" : "admin", "realm" : "ManagementRealm"}}, "failure-description" : "JBAS010839: Operation failed or was rolled back on all servers.", "rolled-back" : true, "server-groups" : {"main-server-group" : {"host" : {"master" : {"server-one" : {"response" : {"outcome" : "failed", "failure-description" : "JBAS015249: No security context has been established.", "rolled-back" : true}}, "server-two" : {"response" : {"outcome" : "failed", "failure-description" : "JBAS015249: No security context has been established.", "rolled-back" : true}}}}}}}].
Per triage with loleary, crouch, mfoley: Move to JBoss ON product, set target release JON 3.2, clear priority (will be subject to further triage in JON 3.2 timeframe).
This appears to already be fixed upstream according to https://bugzilla.redhat.com/show_bug.cgi?id=859512#c1
Already fixed in master see upstream BZ859512#c1
As this is MODIFIED or ON_QA, setting milestone to ER1.
Tescase from Stefan: 1. do a config change that requires managed server reload or restart 2. verify UI reports managed server needs reload or restart Did it by changing datasource configuration in profile assigned with 1 or more running managed servers, then on managed server's datasource UI was signaling restart required verified on JON 3.2.0.ER5