User is unable to click the configuration tab for a group of RHQ Agents. This seems to work with other groups for which "Configure" is a valid path, such as postgresql servers. Repro steps: 1. Create a compatible group of 3 or more RHQ Agents. I selected non-recursive, if that matters. 2. Resource > Compatible Groups > $group_name 3. Attempt to view the Configure page for the group (either by icons in the leftnav or via the "Configure" tab) 4. View results. Current results: Failed to load group Resource configuration. Cause: javax.ejb.EJBException:java.lang.RuntimeException: Failed to retrieve live Resource configurations. -> java.lang.RuntimeException:Failed to retrieve live Resource configurations. -> java.util.concurrent.ExecutionException:java.lang.Exception: Failed to obtain live Resource configuration for Resource[id=501051, type=RHQ Agent, key=jonqa.rdu.redhat.com RHQ Agent, name=jonqa.rdu.redhat.com RHQ Agent, parent=jonqa.rdu.redhat.com, version=1.2.0-SNAPSHOT]. -> java.lang.Exception:Failed to obtain live Resource configuration for Resource[id=501051, type=RHQ Agent, key=jonqa.rdu.redhat.com RHQ Agent, name=jonqa.rdu.redhat.com RHQ Agent, parent=jonqa.rdu.redhat.com, version=1.2.0-SNAPSHOT]. Expected results: Can view/edit configurations. Other notes: See attached traceback from serverlog..
Attaching screenshot, to note that all agents are up, and as far as I can tell had been and continued to be.
This occurs when agent is misconfigured and defaults with an endpoint of 127.0.0.1. Agent can communicate with server, but not vice-versa. Reducing priority for this, and certainly not a major 2.2 issue.
created RHQ-1911 in response to this issue.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1908 Imported an attachment (id=368688) Imported an attachment (id=368689) This bug relates to RHQ-1911
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
just tested this - the new gwt ui will still show something - it won't error out. The latest known config will be shown if some agents in the group are down or unreachable. If the agents are reachable, their live configs are used.
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.