Bug 831369 - [as7] Warnings When Loading Resource Configuration
[as7] Warnings When Loading Resource Configuration
Product: RHQ Project
Classification: Other
Component: Plugins (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: RHQ 4.5.0
Assigned To: Stefan Negrea
Mike Foley
Depends On:
Blocks: as7-plugin 835699
  Show dependency treegraph
Reported: 2012-06-12 17:20 EDT by Stefan Negrea
Modified: 2013-09-01 06:18 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 835699 (view as bug list)
Last Closed: 2013-09-01 06:18:18 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stefan Negrea 2012-06-12 17:20:37 EDT
Description of problem:

Warnings are logged by the agent when loading resource configuration for all the AS7 plugin resources. Here is an example:

12:14:09,940 WARN  [ASConnection] Received 500 (Internal Server Error) response to Operation{operation='read-attribute', address=Address{path: subsystem=transactions,log-store=log-store}, additionalProperties={name=name}} - response body was [{"outcome" : "failed", "failure-description" : "JBAS014792: Unknown attribute name", "rolled-back" : true, "response-headers" : {"process-state" : "reload-required"}}].

The error is harmless. The error is due executing an extra operation to discover the server state (normal, reload required, restart required). The operation executed is :read-attribute with "name" as the name of the attribute. This operation will fail for any sub-resource that does not have "name" in the definition. While the operation fails, it still returns the correct server state. There are no side effects other than log entries.

How reproducible:
Every time

Steps to Reproduce:
1. Discover and import an AS7 server.
2. Select a resource that has configuration available and to the configuration tab.
3. Look in the agent logs and notice the above error.
Actual results:
Warning added to the agent log

Expected results:
No warnings in the agent log

Additional info:
The solution, instead of using :read-attribute operation to detect server state, use :whoami. This operation is present on all resources, does not require any attributes, and does return the server state.
Comment 1 Stefan Negrea 2012-06-12 17:24:48 EDT
Updated the plugin to use :whoami to retrieve server state.

master branch commit:
Comment 2 Heiko W. Rupp 2013-09-01 06:18:18 EDT
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.

Note You need to log in before you can comment on or make changes to this bug.